Re: Hi!
On Tue, Feb 16, 2010 at 12:24:53PM -0500, MK wrote: > I could see it being useful internally; but as for "specific windows" in > the config how can you know in advance what windowID to use? Oh right -- in that case it's probably not useful, not when most things tend to run in window context anyway. It used to be useful for use with FvwmEvent, when the windowid was passed into a calling function for the event, so you could do something like: *FvwmEvent: passid *FvwmEvent: configure_window FooFunc DestroyFunc FooFunc AddToFunc FooFunc + I WindowId $0 (Optional_name) DoSomething ... but these days, because the calling function operates within the context of a known window, such checks degrade to: + I ThisWindow (Optional_name) DoSomething So, standalone it's usecase is somewhat limited. Why do you even ask, out of interest? -- Thomas Adam -- "It was the cruelest game I've ever played and it's played inside my head." -- "Hush The Warmth", Gorky's Zygotic Mynci.
Re: Hi!
2010/2/16 MK : >> > Tangential question: am I missing something or is WindowId bordeline >> > useless? >> Oh, it has a lot of uses in passing around specific window IDs to >> functions to refer to specific windows -- and is used a lot >> internally by FVWM as well. > > I could see it being useful internally; but as for "specific windows" in > the config how can you know in advance what windowID to use? It's mostly useful for dynamic configuration. For instance it could be used together with PipeRead to do something with a window selected by other means earlier. Or you could be interested in saving a window id in an environmental variable and use it later. (The $[w.id] window variable is the key to successful use of the WindowId command in most cases.) Of course it should not be abused either, if for instance window states can be used instead on environment variables that is preferred. /Viktor
Re: Hi!
On Tue, 16 Feb 2010 16:44:58 + Thomas Adam wrote: > > However, I now notice that FvwmPager has a zero length title in the > > window list. Does anyone know of a way to give it a name, or do I > > have to patch the FvwmPager source? > > Eh? Are you sure you haven't set the style WindowListSkip on it or > something? By default, the name of the FvwmPager is the name of the > current desk you're on, as referenced through either the deprecated > option "*FvwmPager: Label", or more preferrably: DesktopName. Ah, I had set Label invalid when trying to lose it; took that out and added a DesktopName, thanks. > > Tangential question: am I missing something or is WindowId bordeline > > useless? > Oh, it has a lot of uses in passing around specific window IDs to > functions to refer to specific windows -- and is used a lot > internally by FVWM as well. I could see it being useful internally; but as for "specific windows" in the config how can you know in advance what windowID to use? -- MK
Re: Hi!
On Tue, Feb 16, 2010 at 10:25:44AM -0500, MK wrote: > On Mon, 15 Feb 2010 20:12:08 -0600 > Jonathan Kotta wrote: > > On Mon, Feb 15, 2010 at 7:56 PM, MK > > wrote: > > > But I don't see a way to call a function on a window by name? ?Am I > > > wrong? > > > > Have look at "List of Conditional Commands" in the manpage. Look at > > All, Next, and Prev in particular. You can also use WindowId if you > > know the window's ID. > > Thanks, that will probably work, at least for the first part. > > However, I now notice that FvwmPager has a zero length title in the > window list. Does anyone know of a way to give it a name, or do I have > to patch the FvwmPager source? Eh? Are you sure you haven't set the style WindowListSkip on it or something? By default, the name of the FvwmPager is the name of the current desk you're on, as referenced through either the deprecated option "*FvwmPager: Label", or more preferrably: DesktopName. But patch the source? No. > Tangential question: am I missing something or is WindowId bordeline > useless? Isn't this like saying "You can use the exact address of the > variable if you know it"? Sure, but it is unlikely to remain the same > between invocations and AFAICT must be hardcoded in .fvwm2rc... Oh, it has a lot of uses in passing around specific window IDs to functions to refer to specific windows -- and is used a lot internally by FVWM as well. -- Thomas Adam -- "It was the cruelest game I've ever played and it's played inside my head." -- "Hush The Warmth", Gorky's Zygotic Mynci.
Re: Hi!
On Mon, 15 Feb 2010 20:12:08 -0600 Jonathan Kotta wrote: > On Mon, Feb 15, 2010 at 7:56 PM, MK > wrote: > > But I don't see a way to call a function on a window by name? Am I > > wrong? > > Have look at "List of Conditional Commands" in the manpage. Look at > All, Next, and Prev in particular. You can also use WindowId if you > know the window's ID. Thanks, that will probably work, at least for the first part. However, I now notice that FvwmPager has a zero length title in the window list. Does anyone know of a way to give it a name, or do I have to patch the FvwmPager source? Tangential question: am I missing something or is WindowId bordeline useless? Isn't this like saying "You can use the exact address of the variable if you know it"? Sure, but it is unlikely to remain the same between invocations and AFAICT must be hardcoded in .fvwm2rc... --MK
Re: Hi!
On Mon, Feb 15, 2010 at 08:56:03PM -0500, MK wrote: > The style settings already depend upon regexing or globbing with the > window names (hey -- which is it?) . Those are hardcoded in the Look at the implementation of matchWildcards() in libs/wild.c -- Thomas Adam -- "It was the cruelest game I've ever played and it's played inside my head." -- "Hush The Warmth", Gorky's Zygotic Mynci.
Re: Hi!
On Mon, Feb 15, 2010 at 7:56 PM, MK wrote: > But I don't see a way to call a function on a window by name? Am I > wrong? > Have look at "List of Conditional Commands" in the manpage. Look at All, Next, and Prev in particular. You can also use WindowId if you know the window's ID. -- Thanks, Jonathan Kotta Hofstadter's Law: It always takes longer than you expect, even when you take into account Hofstadter's Law.
Hi!
I'm taking a sudden interest in the fvwm code because Thomas Adam posted on the user list looking for GSOC cantidates, but I've loved fvwm for a long time, started C programming a few years ago, perl a few years before that, to a small degree understand and have used xlib. Not totally sure that I am the appropriate person for GSOC, but I do think Thomas should follow up with the mentoring application this year as you are sure to get *someone* who can do good things for you. Also I think I'd like to take an interest anyway, I have never taken part in a large collaborative project like this. Poking around in the source made me realize how out of touch I actually am just with the interface -- eg, the first two things I wanted to do were 1) make the "windows start" key work as a modifier, which eventually I realized this is <<6, aka Mod4Mask, and already available :D Second example was the desk label in fvwm pager: I use one desk and don't want it. Eventually noticed this is flagged with "uselabel" in the FvwmPager source and eliminating the label is in the man page :D :D So this may well be a question more appropriate to the user list but I thought I'd ask here as you are sure to know and what follows from that is thinking about the possibility of implementing it. Using the "start" key is like adding a fourth bit -- when really the first three are already taken except in combination. I keep the pager staysonbottom, but I'd like to couple a universal root window key combo to RaiseLower the pager and probably also change it's geometry -- like double the size and center it, then maybe even on click lower and put it back in the corner. I'd love to do that with the iconbox too. The style settings already depend upon regexing or globbing with the window names (hey -- which is it?) . Those are hardcoded in the config: Style "someapp" Property... But I don't see a way to call a function on a window by name? Am I wrong? -- MK
hi
Thank you for contacting [EMAIL PROTECTED] We appreciate you taking the time to report a problem with the site. Due to the large amount of spam we receive we have changed a few of our email addresses in the attempt to eliminate some of the spam. Please feel free to contact us regarding any feedback you wish to provide regarding Epinions.com. http://www.epinions.com/feedback Thank you, Epinions Community Care Team -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
hi
is that your name? <>
Auto Reply(From: w...@onlysw.com, Subject: hi)
ÖйúÉÌ»§ÍøÃâ·ÑΪ»áÔ±ÆóÒµ½¨Á¢µç×ÓÉÌÎñÐÍÍøÕ¾ »¶ÓÀ´µç×Éѯ£º0551-4248558 ÍøÖ·£ºwww.onlysw.com ÍøÂçʵÃû£ºÖйúÉÌ»§Íø -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
