On Mon, Feb 24 at 00:37, [EMAIL PROTECTED] wrote: > On Sun, Feb 23, 2003 at 04:48:44AM +0100, Marcin Pawlik wrote: >> In the descriptions of Current, None, Any, Pick, PointerWindow, and >> ThisWindow commands there is a part saying "The command (...) implies >> the conditions CirculateHit, CirculateHitIcon and >> CirculateHitShaded". >> >> It looks strange in this context. I don't understand what's the point >> in putting this conditions on commands like Pick. > > Current, Pick and Pointerwindow imply said conditions because they > have a unique target window, so 'skipping' the window would be > inappropriate. For example, the user is asked for a window with Pick > and clicks on a shaded xterm. The expected behaviour is that Pick > takes this window, regardless of any window styles.
So when I say "Pick (cond) foo" it usualy means "do foo on chosen window if it satisfies cond" but if cond is for example "!CirculateHit" the meaning is "do foo on chosen window not assuming that CirculateHit is true"? If so, is there any way to check if window has "!CirculateHit"? I checked if it works this way, but it is probably even more complicated. "Pick (!CirculateHit) Iconify" command iconifies "CirculateHit" windows and ignores "!CirculateHit" windows. I still don't understand reasons for this reversed behaviour. I also tried "Pick (Maximized !Maximized) Iconify" and it iconifies windows. Is the "p and not p" true here?. But "Pick (!Maximized Maximized) Iconify" does nothing. Is the order significant, why? I'm afraid I completely don't understand how it works. > No, the man page is correct. It works fine with 2.5.5. What > version did you try? Current (Feb 24) CVS. Regards -- Marcin Pawlik -- Visit the official FVWM web page at <URL: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]
