Re: dragging 2 windows in synch
Thank you for that excellent suggestion! I may have been missing the forest for the drawer in this case as this seems such an obvious solution... now that you point it out. I do like that drawers can open from different edges depending what the user might find most convenient. In this case, where I'm doing something that might ordinarily be done with a popup menu - if the list of items weren't so big - having it scroll up without taking the window's handle with it is the detractor from simply resizing the stack to show the list. -Scott Morrow Elementary Software (Now with 20% less chalk dust !) web http://elementarysoftware.com/ email [EMAIL PROTECTED] - Richard Gaskin wrote: It may be simpler and more consistent with the UI expectations for your users to just use a collapsable panel with a disclosure triangle instead. In most cases where an OS X drawer would work a collapsable panel will work just as well, and the convention is universally accepted on all modern platforms (even OS X). -- Richard Gaskin On 8/31/04 9:34 PM, Scott Morrow [EMAIL PROTECTED] wrote: Hello, Is there a technique to maintain the relative location of a secondary stack while dragging the primary stack. I'm not looking to just update the window location after the move has completed but to visually drag it along with the window that the user is moving. I'm building routines for simulating drawer behaviors outside of OSX. Well, if it's for OS 9, you're probably out of luck unless you make your own custom windows and your own drag regions. The reason is that the moveStack message isn't sent until *after* you release the mouse on the Mac. Now if this is for Windows, moveStack and resizeStack are sent continually so you could probably get away with something like: on moveWindow set the topLeft of stack Secondary to the topRight of this stack end moveWindow ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: dragging 2 windows in synch
Mr. Rossi, I thank you for that demo. What an elegant script. I'm not ready to fake the title bar yet but if I come to it your script will surely be the ticket. Ken, I was under the impression that dragging the title bar was a kind of blocking action and wasn't sure ANY messages were sent in Revolution / OS 9 then. (I could of course fire up an OS9 machine and discover this for myself rather than rambling on...) Certainly I would love to see a script. -Scott Morrow Elementary Software (Now with 20% less chalk dust !) web http://elementarysoftware.com/ email [EMAIL PROTECTED] - On Sep 1, 2004, at 10:42 AM, Scott Rossi wrote: Recently, Scott Morrow wrote: Is there a technique to maintain the relative location of a secondary stack while dragging the primary stack. I'm not looking to just update the window location after the move has completed but to visually drag it along with the window that the user is moving. I'm building routines for simulating drawer behaviors outside of OSX. If you create your own drag mechanism, it's possible. See this demo -- run the following in your message box: go url http://www.tactilemedia.com/download/slider.rev; Relies on a palette stack being the main stack but might give you some useful info. Regards, Scott Rossi Creative Director Tactile Media, Multimedia Design - E: [EMAIL PROTECTED] W: http://www.tactilemedia.com ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: dragging 2 windows in synch
Hi Scott, I've a very easy to implement library for doing just about what you want. It's called 'altBuddyStack' and available at the bottom of page: http://www.altuit.com/webs/altuit2/RunRev/Downloads.htm or just put in the msg: go URL http://www.altuit.com/webs/altuit2/RunRev/altbuddystack.rev; and you can see it work. It has the advantage of being VERY EASY TO IMPLEMENT with existing stacks/windows. The disadvantage of only moving the stacks together after the mouse is up (something you don't want to do). best, Chipp Scott Morrow wrote: Recently, Scott Morrow wrote: Is there a technique to maintain the relative location of a secondary stack while dragging the primary stack. I'm not looking to just update the window location after the move has completed but to visually drag it along with the window that the user is moving. I'm building routines for simulating drawer behaviors outside of OSX. ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: dragging 2 windows in synch
Chipp Walters wrote: I've a very easy to implement library for doing just about what you want. It's called 'altBuddyStack' and available at the bottom of page: http://www.altuit.com/webs/altuit2/RunRev/Downloads.htm or just put in the msg: go URL http://www.altuit.com/webs/altuit2/RunRev/altbuddystack.rev; and you can see it work. It has the advantage of being VERY EASY TO IMPLEMENT with existing stacks/windows. The disadvantage of only moving the stacks together after the mouse is up (something you don't want to do). Works in MetaCard too. :) FWIW, it may be useful to just use a disclosure pane for things you might otherwise use a drawer for. A lot of OS X apps use expanding panels with a disclosure triangle, and the convention is popular on most other modern GUIs as well. Drawers are great for making a Mac-only app, but they're foreign to other OSes and the tradeoffs with using a disclosure pane are few if any at all. -- Richard Gaskin Fourth World Media Corporation ___ [EMAIL PROTECTED] http://www.FourthWorld.com ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: dragging 2 windows in synch
Recently, Scott Morrow wrote: Is there a technique to maintain the relative location of a secondary stack while dragging the primary stack. I'm not looking to just update the window location after the move has completed but to visually drag it along with the window that the user is moving. I'm building routines for simulating drawer behaviors outside of OSX. If you create your own drag mechanism, it's possible. See this demo -- run the following in your message box: go url http://www.tactilemedia.com/download/slider.rev; Relies on a palette stack being the main stack but might give you some useful info. Regards, Scott Rossi Creative Director Tactile Media, Multimedia Design - E: [EMAIL PROTECTED] W: http://www.tactilemedia.com ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: dragging 2 windows in synch
Hi Ken and Scott, Date: Tue, 31 Aug 2004 21:56:03 -0500 From: Ken Ray [EMAIL PROTECTED] Subject: Re: dragging 2 windows in synch On 8/31/04 9:34 PM, Scott Morrow [EMAIL PROTECTED] wrote: Hello, Is there a technique to maintain the relative location of a secondary stack while dragging the primary stack. I'm not looking to just update the window location after the move has completed but to visually drag it along with the window that the user is moving. I'm building routines for simulating drawer behaviors outside of OSX. Well, if it's for OS 9, you're probably out of luck unless you make your own custom windows and your own drag regions. The reason is that the moveStack message isn't sent until *after* you release the mouse on the Mac. Well, actually it should work under OS 9 because the windows ghost when you move them, i.e., you aren't moving the real window, like you are with OSX and Windows XP. That means both should reappear together. AFAIK, it's Mac OSX that simply won't work with the moveStack message because of the reasons you site. The only other way to make it work is via continuous window relocation script that uses globalized mouseMove coordinate offsets. It won't be as smooth, but on todays fast Macs and fast video, it ought to be somewhat acceptable. I have a routine that does that, but not on this machine. I have to get to the studio to look it up. Or, since it's not rocket science, you can probably figure it out reasonably quickly. I'd suggest doing all the maths you can up front, i.e., establish the window offsets at mouseDown, and use small 1 or 2 letter variable names. Everything counts when you need your routine to run fast, but most of it depends on screen redraws as you 'drag'. If someone else doesn't come up with it beforehand, I'll find the example and post it, but I gotta go. owever, I also wish for a way to move multiple stack windows simultaneously without running a script routine. And real Drawers, too, for that matter. HTH, Ken N. ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: dragging 2 windows in synch
On 8/31/04 9:34 PM, Scott Morrow [EMAIL PROTECTED] wrote: Hello, Is there a technique to maintain the relative location of a secondary stack while dragging the primary stack. I'm not looking to just update the window location after the move has completed but to visually drag it along with the window that the user is moving. I'm building routines for simulating drawer behaviors outside of OSX. Well, if it's for OS 9, you're probably out of luck unless you make your own custom windows and your own drag regions. The reason is that the moveStack message isn't sent until *after* you release the mouse on the Mac. Now if this is for Windows, moveStack and resizeStack are sent continually so you could probably get away with something like: on moveWindow set the topLeft of stack Secondary to the topRight of this stack end moveWindow Ken Ray Sons of Thunder Software Web site: http://www.sonsothunder.com/ Email: [EMAIL PROTECTED] ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: dragging 2 windows in synch
Thanks Ken, I'm working in MacOS and didn't realize that the moveStack and resizeStack message were sent continually under Windows. While good news it surprised me as the documentation is pretty specific. The moveStack message is sent after the movement is finished. This means that you cannot prevent a stack window from being moved by trapping this message. I'm using Rev version 2.1.2 so hopefully this isn't a new feature! ... Custom windows will probably have to wait : ) -Scott On Aug 31, 2004, at 7:56 PM, Ken Ray wrote: On 8/31/04 9:34 PM, Scott Morrow [EMAIL PROTECTED] wrote: Hello, Is there a technique to maintain the relative location of a secondary stack while dragging the primary stack. I'm not looking to just update the window location after the move has completed but to visually drag it along with the window that the user is moving. I'm building routines for simulating drawer behaviors outside of OSX. Well, if it's for OS 9, you're probably out of luck unless you make your own custom windows and your own drag regions. The reason is that the moveStack message isn't sent until *after* you release the mouse on the Mac. Now if this is for Windows, moveStack and resizeStack are sent continually so you could probably get away with something like: on moveWindow set the topLeft of stack Secondary to the topRight of this stack end moveWindow Ken Ray Sons of Thunder Software Web site: http://www.sonsothunder.com/ Email: [EMAIL PROTECTED] ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: dragging 2 windows in synch
Ken Ray wrote: On 8/31/04 9:34 PM, Scott Morrow [EMAIL PROTECTED] wrote: Hello, Is there a technique to maintain the relative location of a secondary stack while dragging the primary stack. I'm not looking to just update the window location after the move has completed but to visually drag it along with the window that the user is moving. I'm building routines for simulating drawer behaviors outside of OSX. Well, if it's for OS 9, you're probably out of luck unless you make your own custom windows and your own drag regions. The reason is that the moveStack message isn't sent until *after* you release the mouse on the Mac. Now if this is for Windows, moveStack and resizeStack are sent continually so you could probably get away with something like: on moveWindow set the topLeft of stack Secondary to the topRight of this stack end moveWindow It may be simpler and more consistent with the UI expectations for your users to just use a collapsable panel with a disclosure triangle instead. In most cases where an OS X drawer would work a collapsable panel will work just as well, and the convention is universally accepted on all modern platforms (even OS X). -- Richard Gaskin Fourth World Media Corporation ___ [EMAIL PROTECTED] http://www.FourthWorld.com ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
