Re: Rev Menus [was Re: Location of stack]

2010-05-17 Thread Richard Gaskin
Jeff Massung wrote: On Mon, May 17, 2010 at 2:28 PM, Richard Gaskin wrote: I can think of no solution for adding something to a window in a way that doesn't add it to the window. I can't think of way to eat a burger without eating a burger. Richard, I usually love your insightful posts...

Re: Rev Menus [was Re: Location of stack]

2010-05-17 Thread Jeff Massung
On Mon, May 17, 2010 at 2:28 PM, Richard Gaskin wrote: > > I can think of no solution for adding something to a window in a way that > doesn't add it to the window. > > I can't think of way to eat a burger without eating a burger. Richard, I usually love your insightful posts... but that statemen

Re: Rev Menus [was Re: Location of stack]

2010-05-17 Thread Richard Gaskin
Mark Wieder wrote: Point taken. The fact that there needs to be an explanation at all, though, and that it's something that comes up frequently on the list, is an indicator that something needs work. Perhaps what it's telling us is that we should take Steve Jobs' advice and stop making cross-

Re: Rev Menus [was Re: Location of stack]

2010-05-17 Thread Mark Wieder
Jacque- Monday, May 17, 2010, 9:54:58 AM, you wrote: > I'm not disagreeing, I'm just wondering what better way would be > available. I don't personally have any trouble with menu builder, I've > found it to be solid and reliable, but I won't argue if others do. I use > menu builder in virtually e

Re: Location of stack

2010-05-17 Thread J. Landman Gay
Jeff Massung wrote: In Win32 (and Linux), you can make a window and put any controls in there you want. 0,0 is always the upper-left corner of the _usable_ client area in the window. If you were - at runtime - to attach a menu to the window, what would happen is that the usable client area would

Re: Location of stack

2010-05-17 Thread J. Landman Gay
Jeff Massung wrote: On Mon, May 17, 2010 at 10:59 AM, J. Landman Gay wrote: Perhaps menus should be independent objects? Then the engine could manage them. There would still be issues with the space at the top of the stack, where menus show on two platforms but not on the other. How would you h

Rev Menus [was Re: Location of stack]

2010-05-17 Thread J. Landman Gay
Mark Wieder wrote: Jacque- Monday, May 17, 2010, 8:59:41 AM, you wrote: As far as I can see, the confusion comes from those who don't understand the scrolling behavior. Once they get that, it falls into place. Sorry, I'm with Jeff on this. There are (at least) three things I never use in the

Re: Location of stack

2010-05-17 Thread Jeff Massung
On Mon, May 17, 2010 at 11:40 AM, Jeff Massung wrote: > > In Win32 (and Linux), you can make a window and put any controls in there > you want. 0,0 is always the upper-left corner of the _usable_ client area in > the window. If you were - at runtime - to attach a menu to the window, what > would

Re: Location of stack

2010-05-17 Thread Jeff Massung
On Mon, May 17, 2010 at 10:59 AM, J. Landman Gay wrote: > > Perhaps menus should be independent objects? Then the engine could manage > them. There would still be issues with the space at the top of the stack, > where menus show on two platforms but not on the other. How would you handle > that? >

Re: Location of stack

2010-05-17 Thread Mark Wieder
Jacque- Monday, May 17, 2010, 8:59:41 AM, you wrote: > As far as I can see, the confusion comes from those who don't understand > the scrolling behavior. Once they get that, it falls into place. Sorry, I'm with Jeff on this. There are (at least) three things I never use in the rev IDE: the menu

Re: Location of stack

2010-05-17 Thread J. Landman Gay
Jeff Massung wrote: Summary: menus are a "feature" in Rev that needs completely revamped and fixed. I wouldn't mind that, of course, since it does come up often, but I'm not sure what the answer would be. Menus work as expected on Windows and Linux; we'd need a cross-platform way to implemen

Re: Location of stack

2010-05-17 Thread Jeff Massung
On Sun, May 16, 2010 at 2:42 PM, J. Landman Gay wrote: > Jeff Massung wrote: > >> Oh, please, RunRev gods working on the roadmap... can we *please* get this >> fixed finally? Menus - like unicode - should "just work" out of the box. >> > > I've never had much trouble with it, aside from the known

Re: Location of stack

2010-05-17 Thread Mark Schonewille
Hi Paul, I just saw your question on the forum. I'll post the same answer there and on this list. The engine knows the actual height of the card only after loading all windows, objects, libraries etc. This is easy to solve, by first running all default startup messages (preOpenStack, open

Re: Location of stack

2010-05-16 Thread J. Landman Gay
Jeff Massung wrote: Oh, please, RunRev gods working on the roadmap... can we *please* get this fixed finally? Menus - like unicode - should "just work" out of the box. I've never had much trouble with it, aside from the known bug where stacks with destroystack set don't always scroll correctly

Re: Location of stack

2010-05-16 Thread Jeff Massung
Oh, please, RunRev gods working on the roadmap... can we *please* get this fixed finally? Menus - like unicode - should "just work" out of the box. Jeff M. ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe

Re: Location of stack

2010-05-16 Thread J. Landman Gay
Paul D. DeRocco wrote: Alternatively, is there a way to know in advance how much to twiddle the vertical location by? It's 12 in my system, and I assume that's half the height of the non-existent menu bar, but I expect that varies depending upon the screen resolution or something-or-other, just

Re: Location of stack

2010-05-16 Thread Sarah Reichelt
> Alternatively, is there a way to know in advance how much to twiddle the > vertical location by? It's 12 in my system, and I assume that's half the > height of the non-existent menu bar, but I expect that varies depending upon > the screen resolution or something-or-other, just as it would under

Re: Location of stack

2010-05-16 Thread Jerry Daniels
I'm not positive it will work...maybe openStack won't get sent if the stack isn't visible. You could send your own custom message, tho, on preOpenStack. I do stuff like that on startUp to give libURL time to load. Best, Jerry Daniels Create iPad web apps with Rodeo: http://rodeoapps.com On Ma

RE: Location of stack

2010-05-16 Thread Paul D. DeRocco
> From: Jerry Daniels > > You could also hide the stack on preOpenStack then do your > business and show the stack on openStack. That sounds like it's worth a try. Thanks. -- Ciao, Paul D. DeRocco Paulmailto:pdero...@ix.netcom.com __

RE: Location of stack

2010-05-16 Thread Paul D. DeRocco
> From: Sarah Reichelt > > No, in that case, it should work fine, except that your users > will see the window flash up and then move. > > A compromise might be to set the loc in both handlers. Then it > will appear almost in the right place and then shuffle a little bit. Alternatively, is there a

Re: Location of stack

2010-05-16 Thread Jerry Daniels
You could also hide the stack on preOpenStack then do your business and show the stack on openStack. Best, Jerry Daniels Create iPad web apps with Rodeo: http://rodeoapps.com On May 16, 2010, at 3:22 AM, Sarah Reichelt wrote: > On 16/05/2010, at 4:34 PM, "Paul D. DeRocco" wrote: > >>> From

Re: Location of stack

2010-05-16 Thread Sarah Reichelt
On 16/05/2010, at 4:34 PM, "Paul D. DeRocco" wrote: >> From: Sarah Reichelt >> >> I'm guessing your stack has a menu. On Mac stacks, Rev does some funny >> business to hide the menu buttons off the top of the stacks window and >> create a real Mac menu. But this doesn't happen immediately. >> >

RE: Location of stack

2010-05-15 Thread Paul D. DeRocco
> From: Sarah Reichelt > > I'm guessing your stack has a menu. On Mac stacks, Rev does some funny > business to hide the menu buttons off the top of the stacks window and > create a real Mac menu. But this doesn't happen immediately. > > If you set the loc in a preOpenStack or startup handler, the

Re: Location of stack

2010-05-15 Thread Sarah Reichelt
I'm guessing your stack has a menu. On Mac stacks, Rev does some funny business to hide the menu buttons off the top of the stacks window and create a real Mac menu. But this doesn't happen immediately. If you set the loc in a preOpenStack or startup handler, the menu bar will not have been hidden