Page 1 of 1
Menu builder outside the stack
Posted: Fri Dec 04, 2009 3:58 pm
by massung
I'm sure this (or similar) has been brought up before, but my biggest frustration with Rev to-date is - hands down - the menu builder. The builder is fine, but I hate having to see the menu in the stack and (because of that) having to work around a lot of annoyances when building an app that will run on both OS X and Windows.
On Windows, the menu is in the stack, and so controls being shifted down is fine. On OS X shifting the controls "breaks" the app and I have to manually fix it on stack startup... very frustrating.
Would it be possible to just have the menu live outside the stack during development (ala Interface Builder in XCode?), and then have Rev just "do the right thing" for each platform on a built application?
Jeff M.
Re: Menu builder outside the stack
Posted: Sat Dec 05, 2009 12:34 am
by Mark
Hi Jeff,
First of all, I think it would be a great idea to make the menubar a completely separate element, which can be added to or removed from the stack window.
Having said that, I'm not completely sure which problem you describe. What I see myself is that all is fine inside the IDE, but when I build a standalone, the window size is often too large or too small, either cutton off some controls or adding white space. Some time ago, I noticed that toggling either the destroyStack or the destroyWindow window property, or both, solves the problem.
Is this the problem you refer to?
Best,
Mark
Re: Menu builder outside the stack
Posted: Sat Dec 05, 2009 12:37 pm
by malte
Hiding the menubar group on the mac also appears to fix things. But I agree. building menus is nasty
cheers,
Malte
Re: Menu builder outside the stack
Posted: Tue Dec 08, 2009 5:41 pm
by massung
Mark wrote:...What I see myself is that all is fine inside the IDE, but when I build a standalone, the window size is often too large or too small, either cutton off some controls or adding white space. Some time ago, I noticed that toggling either the destroyStack or the destroyWindow window property, or both, solves the problem.
Is this the problem you refer to?
Yep, this is it exactly. I usually have to end up putting an
on openStack event that fixes everything up based on what platform is running... but I also have to comment it out during development (I'm unaware of a way to query whether or not the stack running is in development mode or a standalone).
Anyway, yes, building a menu outside of the stack and then just saying
set the menu of stack "MyApp" to ... and having Rev do the right thing based on platform (shift controls + increase stack size on Win32 and nothing on OS X) would be very ideal.
It would also allow me to swap out menus at runtime very easily should I need to given the context, active card, or whatever reason I can think of.
Jeff M.