On 03 Sep 2004 10:03:19 +0200, Dominik Vogt wrote: > > On Fri, Sep 03, 2004 at 07:20:59AM +0200, Olivier Chapuis wrote: > > * New command SaveWindowPointerPosition: this command save the pointer > > position relatively to the "current" window. You can restore this > > position with a new option to the WarpToWindow cmd: "UseSavedPosition". > > WarpToWindow UseSavedPosition 50 50 will either restore the pointer > > position if saved or put the pointer in the middle of the window. > > My vote: I do not care. > > > > * New command ShowCursor: draw a flashing circle around the cursor > > during a fraction of time. I use this with some new options to > > WarpToWindow: ShowCursor and ShowCursorOnSavedPosition. > > My vote: I do not care. > > > > Example of use of these two cmd and these options to WarpToWindow: > > > > DestroyFunc FuncFvwmSaveWindowPointerPosition > > AddToFunc FuncFvwmSaveWindowPointerPosition > > + I Silent All (HasPointer Focused) SaveWindowPointerPosition On > > + I TestRc (Match) Break 1 > > + I Silent All (HasPointer) SaveWindowPointerPosition On > > + I TestRc (Match) Break 1 > > + I Silent Current SaveWindowPointerPosition On > > > > DestroyFunc WindowListFunc > > AddToFunc WindowListFunc > > + I Iconify false > > + I FlipFocus > > + I Raise > > + I WarpToWindow UseSavedPosition ShowCursorOnSavedPosition 10p 10p > > > > DestroyFunc MyAltTabFunc > > AddToFunc MyAltTabFunc > > + I FuncFvwmSaveWindowPointerPosition > > + I WindowList Root c c NoDeskSort, SelectOnRelease Meta_L > > > > Key Tab A M MyAltTabFunc
I don't very care too, but these seem to be isolated and easy changes, so if you think these are tested well, my vote is more "Yes" than "No". It is probably better to use "short" for new window fields. There is one more unapplied patch that should use "short" not "int" as well. It is good to keep fvwm smaller even if it is just a matter of several KB (this is also potentially passed to all modules, so it should better be short). > > * Support for _NET_SHOW_DESKTOP via a new command ShowDesktop bool: this > > command, if bool is on, iconify all window not in the window skip list. > > If bool is off the command uniconify all window iconified by a > > "ShowDesktop On". This can be simulated by a fvwm function (by using > > State) modulo stacking order problems. FVWM GNOME/KDE users will be > > happy with the support of _NET_SHOW_DESKTOP. My vote: yes. > > _NET_SHOW_DESKTOP support: yes; implementation with icons: no. I > am almost sure using icons for this purpose will make more trouble > than it saves. Instead, all windows should just be unmapped like > when they are on a different desk. The checks for the current > desk are strewn all over the place, so this is no simple patch. Yes, if FvwmAnimate is on, mass-iconify may be problematic. This is why I added "pause", "push" and "pop" messages to FvwmAnimate some time ago. I can't say yet whether iconifying without iconified windows is good. > > * A library "FTips" for implementing tips in modules. I used this > > library to add tips to IconMan with a lot of options (I've even write > > down the man page I can poste it). I used this library in the Pager > > and I plan to use it to implement (multiline) tips in FvwmButtons. > > My vote: yes (a step toward removing the FvwmTaskBar). > > Yes. Yes! > > * New option MaxButtonWidth to FvwmIconman. My vote: yes > > (an other step toward removing the FvwmTaskBar). > > Yes, that's an important patch. Indeed. > > * New option -transient-window to the FvwmPager which causes FvwmPager > > to be transient and to execute "Silent Current MoveToPage x y" or > > "Silent Current MoveToDesk d" or "Silent Current MoveToDeskAndPage d x > > y" in the place of the GotoPage, GotoDesk and GotoDeskAndPage usual > > cmd. Optionally the usual GotoPage, GotoDesk and GotoDeskAndPage are > > also executed. My vote: yes. > > What is that good for? I suggest to rename the option to -transient-move, or -transient -move, where -move is only relevant with -transient. FvwmPager -transient-move is supposed to be bound to a window operation menu, it nicely shows all pages and moves the window to the chosen page. > > * The "execute totally immediate complex function even if we > > cannot grab the pointer" patch. Should not be disputed here :o) > > No. As asked, no comments here. > > * There are others stuffs which are not stable enough. Some new complex > > stacking/focus policy related to text selection and dnd (these use > > XRecord). TaskBar Launch buttons used all the rows. My vote: no. > > Not without knowing more details. > > > * Some metisse specific stuff. New module msg MX_STARTSTOP_OPERATION, > > MX_MODULE_INTERACTIVE_MOVE and MX_CLICK_MOTION mainly for non standard > > operation and interactive move in FvwmAmetista. New msg for syncing > > desk switching are incoming. A new BugOpts option "MetisseWorkaround" > > for small things. My vote: obviously no. Regards, Mikhael. -- 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]
