From: Mike F. <va...@ge...> - 2003-11-24 15:52:16
|
so i load up xine and set the display window to act the way i want it to (borderless, always on top, sticky). i save the settings, quit the app, and relaunch it ... bam, it knows how i like it ... however, if i'm watchin a movie and i load up another movie in a diff xine, the new xine's dont use my custom settings ... they use the default border, sticky settings, etc... and when i look at the remember window, nothing is checked ... the weird thing is that if i look at the remember settings for both windows (the one that knows how i like it and the one that doesnt), they have the same Title, Name, and Class ... so what gives ? :/ -mike |
From: Mandrake (G. H. <man...@ma...> - 2003-11-24 16:53:18
|
On Mon, Nov 24, 2003 at 10:52:28AM -0500, Mike Frysinger wrote: > so i load up xine and set the display window to act the way i want it to > (borderless, always on top, sticky). i save the settings, quit the app, and > relaunch it ... bam, it knows how i like it ... > however, if i'm watchin a movie and i load up another movie in a diff xine, > the new xine's dont use my custom settings ... they use the default border, > sticky settings, etc... and when i look at the remember window, nothing is > checked ... > the weird thing is that if i look at the remember settings for both windows > (the one that knows how i like it and the one that doesnt), they have the > same Title, Name, and Class ... so what gives ? :/ > -mike it always has had per-instance settings. that way you could have different settings for any number of different terminal windows you open, etc. first one, second one, third one, can all be different. -- Mandrake Some Random Guy |
From: Jason V. C. <ja...@va...> - 2003-11-24 22:13:21
|
Quoth Mandrake (Geoff Harrison), on Mon, 24 Nov 2003 11:53:14 -0500: > it always has had per-instance settings. that way you could have > different settings for any number of different terminal windows you > open, etc. first one, second one, third one, can all be different. Yeah, except it doesn't work that way. The first Eterm instance I open takes my remembered settings. If I open a second and set ITS position or whatever, then close both, the first instance I open thereafter remembers the new settings, and the second one doesn't remember a damn thing. As far as I know, this has always been the case. --Jason Van Cleve -- I'm out of my mind, but feel free to leave a message... |
From: Massimo M. <mai...@in...> - 2003-11-24 22:33:03
|
Il giorno Mon, 24 Nov 2003 15:13:02 -0700 Jason scrisse: > Quoth Mandrake (Geoff Harrison), on Mon, 24 Nov 2003 11:53:14 -0500: >=20 > > it always has had per-instance settings. that way you could have > > different settings for any number of different terminal windows you > > open, etc. first one, second one, third one, can all be different. >=20 > Yeah, except it doesn't work that way. The first Eterm instance I > open takes my remembered settings. If I open a second and set ITS > position or whatever, then close both, the first instance I open > thereafter remembers the new settings, and the second one doesn't > remember a damn thing. As far as I know, this has always been the > case. look for a file called "windowmatches.cfg" in your theme's dir and edit it to have a window with specific attributes always with the same settings. --=20 Massimo Maiurana mailto:ma...@ra... Linux RU #245612 RM #127258 keyID #7044D601 Articolo 11 - L'Italia ripudia la guerra come strumento di offesa alla libert=E0 degli altri popoli e come mezzo di risoluzione delle controversie internazionali; consente, in condizioni di parit=E0 con gli altri Stati, alle limitazioni di sovranit=E0 necessarie ad un ordinamento che assicuri la pace e la giustizia fra le Nazioni; promuove e favorisce le organizzazioni internazionali rivolte a tale scopo.=20 |
From: Kim W. <ki...@wo...> - 2003-11-24 22:50:04
|
Massimo Maiurana wrote: > look for a file called "windowmatches.cfg" in your theme's dir and edit > it to have a window with specific attributes always with the same > settings. > windowmatches.cfg can take care of border and stickyness, but not the layer (yet): __MATCH_WINDOW __BGN __NAME xine __HAS_CLASS xine __USE_BORDER BORDERLESS __MAKE_WINDOW_STICKY __ON __END /Kim |
From: Carsten H. (T. R. <ra...@ra...> - 2003-11-24 23:46:38
|
On Mon, 24 Nov 2003 15:13:02 -0700 Jason Van Cleve <ja...@va...> babbled: > Quoth Mandrake (Geoff Harrison), on Mon, 24 Nov 2003 11:53:14 -0500: > > > it always has had per-instance settings. that way you could have > > different settings for any number of different terminal windows you > > open, etc. first one, second one, third one, can all be different. > > Yeah, except it doesn't work that way. The first Eterm instance I open takes > my remembered settings. If I open a second and set ITS position or whatever, > then close both, the first instance I open thereafter remembers the new > settings, and the second one doesn't remember a damn thing. As far as I know, > this has always been the case. this is not how it orignally was. it originally worked by: u remember a window and e stores, name, class, etc. etc. for each rememebr you do it has a list of these. when a window starts e runs through the list form start to end the first match it has is used. THEN this entry is marked as "used" and wont match anything until this window closes. then this slow can be re-used. thats the original algorithm. it DID work just fine whne it was written and in 0.16.0 and onwards. it may have been broken now. i have noticded that stacking of windows is quite broken now... in 0.16.6 :( i dont have time to look into it atm. -- --------------- Codito, ergo sum - "I code, therefore I am" -------------------- The Rasterman (Carsten Haitzler) ra...@ra... 熊耳 - 車君 ra...@de... Mobile Phone: +61 (0)413 451 899 Home Phone: 02 9698 8615 |
From: Kim W. <ki...@wo...> - 2003-11-25 20:05:28
|
Carsten Haitzler (The Rasterman) wrote: > this is not how it orignally was. it originally worked by: u remember > a window and e stores, name, class, etc. etc. for each rememebr you > do it has a list of these. when a window starts e runs through the > list form start to end the first match it has is used. THEN this > entry is marked as "used" and wont match anything until this window > closes. then this slow can be re-used. > > thats the original algorithm. it DID work just fine whne it was > written and in 0.16.0 and onwards. it may have been broken now. OK, I did another check-up on this. In 0.16.6 the remembered settings feature works for one instance of the key (WM_CLASS or WM_NAME). As reported, settings for multiple windows with same key are not handled properly. However, it works just like in 0.16.5. Someone must have broke it before that :) > i have noticded that stacking of windows is quite broken now... in > 0.16.6 :( i dont have time to look into it atm. > Could you be just a trifle more specific about what is broken? /Kim |
From: Carsten H. (T. R. <ra...@ra...> - 2003-11-25 21:29:49
|
On Tue, 25 Nov 2003 21:05:24 +0100 Kim Woelders <ki...@wo...> babbled: > Carsten Haitzler (The Rasterman) wrote: > > this is not how it orignally was. it originally worked by: u remember > > a window and e stores, name, class, etc. etc. for each rememebr you > > do it has a list of these. when a window starts e runs through the > > list form start to end the first match it has is used. THEN this > > entry is marked as "used" and wont match anything until this window > > closes. then this slow can be re-used. > > > > thats the original algorithm. it DID work just fine whne it was > > written and in 0.16.0 and onwards. it may have been broken now. > > OK, I did another check-up on this. > In 0.16.6 the remembered settings feature works for one instance of the > key (WM_CLASS or WM_NAME). As reported, settings for multiple windows > with same key are not handled properly. > However, it works just like in 0.16.5. > Someone must have broke it before that :) hmmm it should have worked by then. this is explicitly the way i wrote it! :) i cant imagine i'd let 0.16.0 out the door without this working! :) > > i have noticded that stacking of windows is quite broken now... in > > 0.16.6 :( i dont have time to look into it atm. > > > Could you be just a trifle more specific about what is broken? window stacking. ie. i take a window and say "stack below" but it sometimes is able to permenantly stack itself above windows tacked on the "normal" (4) layer. this actually happens often when starting xine - since it requests specific stacking. i also have several epplets that insist on stacking below too :) > /Kim > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- --------------- Codito, ergo sum - "I code, therefore I am" -------------------- The Rasterman (Carsten Haitzler) ra...@ra... 熊耳 - 車君 ra...@de... Mobile Phone: +61 (0)413 451 899 Home Phone: 02 9698 8615 |
From: Kim W. <ki...@wo...> - 2003-11-25 23:07:19
|
Carsten Haitzler (The Rasterman) wrote: >>> i have noticded that stacking of windows is quite broken now... >>> in 0.16.6 :( i dont have time to look into it atm. >> >> Could you be just a trifle more specific about what is broken? > > window stacking. ie. i take a window and say "stack below" but it > sometimes is able to permenantly stack itself above windows tacked on > the "normal" (4) layer. this actually happens often when starting > xine - since it requests specific stacking. i also have several > epplets that insist on stacking below too :) > xine changes the stacking of the calling terminal window to 6 (above). Until somebody tells me why I'm wrong, I think that the problem is with xine. There are similar issues with gmplayer. AFAIK epplets are supposed to stack at layer 2 (below). /Kim |