On Wed, Jan 30, 2002 at 02:09:08PM +0000, Mikhael Goikhman wrote: > On 30 Jan 2002 13:56:24 +0100, Dominik Vogt wrote: > > > > On Wed, Jan 30, 2002 at 11:59:11AM +0000, Mikhael Goikhman wrote: > > > I want to add an option to interactive Move, so snap is ignored. > > > > > > What do you think is a preferable syntax approach? > > > I may think about 2 possible solutions. > > > > > > 1) New command UnconstrainedMove with the same arguments as Move. > > > 2) An option to Move and AnimatedMove (other *Move* commands are not > > > interactive) called NoSnap. > > > > Why? What is the advantage to turning SnapAttraction off before > > moving and enabling it afterwards? > > This is not only SnapAttraction, but SnapGrid and EdgeResistance too. > There is no way to restore their previous state. > > Thinking about this, it may be done by adding a new command Snap: > > Snap Disable > Snap Enable > > This would affect snap in interactive Move and interactive placement. > > Still having an option to do an unconstrained Move would be ok.
An option for the move command should be good enough, I guess. > I myself would bind it to decoration dragging when shift is pressed. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- 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]
