Re: [Flightgear-devel] Translucent Dialogs
David Luff writes: >> > A couple of points I noticed are that when sliding the mouse sideways > across the menubar at the top, the original submenu is not replaced by the > next ones, I believe that this is a dsign decision in PLIB It is related to being able to keep focus on a slider or a dial widget when outside of the widgets bounding box if the mouse button remains depressed > and pressing escape when a dialog with a cancel box is displayed > still brings up the exit sim dialog instead of clearing the current one. This requires a more sophisticated key mapping system then what we currently have. PLIB purposefully leaves almost all keyhandling to the application using it. It could be that the easiest way to remap the 'esc key' when a dialog is active is to have the fgDialog class explicitly check for an 'esc' key < abory event > before passing the key onto the properties key resolution mechanism. Another way is to derive a new base dialog class from puDialog that handles the esc key and use it as the base of all our dialogs Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Translucent Dialogs
David Megginson writes: > > David Luff writes: > > > A couple of points I noticed are that when sliding the mouse sideways > > across the menubar at the top, the original submenu is not replaced by the > > next ones, and pressing escape when a dialog with a cancel box is displayed > > still brings up the exit sim dialog instead of clearing the current one. > > The first issue is almost certainly Plib related I should think, but could > > we be at fault for the second one? > > It may have to do with whether or not the dialog is modal. I'll have > to experiment a bit. > > Did the old dialogs close when you pressed ESC? No We discussed this several years ago Now as then I advocate having a stack of 'keybinding sets' where you associate a set of bindings for a 'mode'. On entering a 'mode' its' set bindings is pushed onto the stack on leaving the mode the stack is popped. A key press is resolved by walking the sets on the stack returning the first binding found This is quite easy to do in 'C' where the stack is actually an array of stacks, one for each possible key combination, and a 'mode set' is a just a list of the key bindings for that mode I think that a variation of a C++ MultiMap could probably be used for this as well Regards Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Translucent Dialogs
On 1/19/03 at 7:51 PM David Megginson wrote: >It may have to do with whether or not the dialog is modal. I'll have >to experiment a bit. > >Did the old dialogs close when you pressed ESC? No, the old behaviour was just the same, it was something I never got round to mentioning... Cheers - Dave ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Translucent Dialogs
David Luff writes: > A couple of points I noticed are that when sliding the mouse sideways > across the menubar at the top, the original submenu is not replaced by the > next ones, and pressing escape when a dialog with a cancel box is displayed > still brings up the exit sim dialog instead of clearing the current one. > The first issue is almost certainly Plib related I should think, but could > we be at fault for the second one? It may have to do with whether or not the dialog is modal. I'll have to experiment a bit. Did the old dialogs close when you pressed ESC? All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Translucent Dialogs
On 1/19/03 at 7:01 PM David Megginson wrote: >Michael Basler writes: > > > Could we draw the menu line over the full width, independent of > > resolution? This is common for nearly all programs on all > > platforms I know. > >Right now we're using the higher-level PUI menubar widget, so we have >to take what we get. To change its appearance, we'd have to implement >our own menubar from low-level widgets. > >In fact, we probably will have to do that sooner or later, since the >PUI menubar is not all that feature-rich, but I don't want to dive >into it right now. A couple of points I noticed are that when sliding the mouse sideways across the menubar at the top, the original submenu is not replaced by the next ones, and pressing escape when a dialog with a cancel box is displayed still brings up the exit sim dialog instead of clearing the current one. The first issue is almost certainly Plib related I should think, but could we be at fault for the second one? Cheers - Dave ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Translucent Dialogs
Michael Basler writes: > Could we draw the menu line over the full width, independent of > resolution? This is common for nearly all programs on all > platforms I know. Right now we're using the higher-level PUI menubar widget, so we have to take what we get. To change its appearance, we'd have to implement our own menubar from low-level widgets. In fact, we probably will have to do that sooner or later, since the PUI menubar is not all that feature-rich, but I don't want to dive into it right now. > PS: Are the recent CVS submits supposed to solve the OK/Cancel memory leak > issue? It should be fixed now. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Translucent Dialogs
Curtis L. Olson writes: > > How would people feel about going opaque? > > What about 90% opaque? Just enough to say, "yeah, we're cool" but for > all practical purposes, they are opaque ... (?) Sounds like a good compromise. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Translucent Dialogs
David, After getting recent CVS updates the menu crash is gone for me too. Great Work you guys! Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Translucent Dialogs
David, > The translucent dialogs we've been using look very spiffy, but it > turns out that they're not all that practical once you start using > things like pop-up menus in combo boxes. Take a look at the clouds > dialog in the latest CVS (FlightGear and base package) to see why. > > How would people feel about going opaque? I am not that definit on this one, maybe personally would leave it as is, but as we are on this: Could we draw the menu line over the full width, independent of resolution? This is common for nearly all programs on all platforms I know. We just would fill it with the main menu entries as far as they go. Perhaps the Help menu (maybe including an "About" button with a link the Home page and GPL) might be on the very right, but this is not mandatory. PS: Are the recent CVS submits supposed to solve the OK/Cancel memory leak issue? Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Translucent Dialogs
David Megginson writes: > The translucent dialogs we've been using look very spiffy, but it > turns out that they're not all that practical once you start using > things like pop-up menus in combo boxes. Take a look at the clouds > dialog in the latest CVS (FlightGear and base package) to see why. > > How would people feel about going opaque? Ok, your latest changes eliminate my crash. Thanks! I now see what you mean about the translucency. The popup menus at least need to be opaque. But since we probably can't control this at that fine of detail we do probably need to go opaque ... I'm not all that attached to the translucency other than it was a bit of eye candy, I'm willing to give it up if everyone else is. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Translucent Dialogs
On 1/19/03 at 6:06 PM David Megginson wrote: >The translucent dialogs we've been using look very spiffy, but it >turns out that they're not all that practical once you start using >things like pop-up menus in combo boxes. Take a look at the clouds >dialog in the latest CVS (FlightGear and base package) to see why. > >How would people feel about going opaque? Opaque is good for dialogs where the sim is paused, but translucent is better for non-paused dialogs, such as selecting an ATC communication from a list whilst flying, IMHO. Could this not be made user definable though? Cheers - Dave ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Translucent Dialogs
David Megginson writes: > The translucent dialogs we've been using look very spiffy, but it > turns out that they're not all that practical once you start using > things like pop-up menus in combo boxes. Take a look at the clouds > dialog in the latest CVS (FlightGear and base package) to see why. > > How would people feel about going opaque? What about 90% opaque? Just enough to say, "yeah, we're cool" but for all practical purposes, they are opaque ... (?) Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Translucent Dialogs
The translucent dialogs we've been using look very spiffy, but it turns out that they're not all that practical once you start using things like pop-up menus in combo boxes. Take a look at the clouds dialog in the latest CVS (FlightGear and base package) to see why. How would people feel about going opaque? All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
