* James Turner -- 6/12/2009 11:05 AM:
I guess there is no chance of switching to osgWidgets in the near
future? I've not looked at how mature that code is or isn't yet.
No. This may take another year, or two. AFAIK, osgWidgets is still
nothing more than colored, clickable rectangles with
* James Turner -- 6/8/2009 10:52 AM:
On 6 Jun 2009, at 08:46, Melchior FRANZ wrote:
I'll [...] try to keep PLIB'isms away as far as possible.
Actually, I'll reorganize the code a bit so that possible later
transitions to osgWidgets or other toolkits are even easier. And
I intend to make all
* James Turner -- 6/8/2009 10:56 AM:
Another, related question: is it possible to hide and show UI
element / groups dynamically?
You can manipulate (add/remove/change) anything in a dialog before
it's opened by embedded Nasal. You could have an XML dialog file
with only a nasalopen block, and
On 12 Jun 2009, at 09:54, Melchior FRANZ wrote:
And
I intend to make all widget properties live, so that one can,
for instance, change the x component (and optionally re-layout
the dialog), and see the widget move. It'll be nice to have live
color changes and to see the total weight text in
On 12 Jun 2009, at 10:04, Melchior FRANZ wrote:
I checked over the dialog code, and I don't see a standard 'visible'
or 'hidden' property (looking at FGDialog::makeObject), but perhaps
there is some other way to achieve this?
There's a visible property per widget group, which defaults to
On 5 Jun 2009, at 19:52, James Turner wrote:
I want this for the route-manager dialog, but I can imagine similar
concepts being useful in the other places in the GUI - for example
the 'position on ground' dialog could have the runway and parking
position fields replaced with menus,
* Melchior FRANZ -- Friday 05 June 2009:
With some code in dialog.cxx live updates of lists could be implemented,
too. Recent changes made that easier than before.
This would really be the best approach. It could then also be used to
live-enable/disable (grey out) widgets, or to change their
I've started something similar, (I think) , with help from others, with the
ATC2.
I use the nasal airportinfo(id) to get airport and runway info.The ATC2
uses 2d panel text , but should be able to do the same in a dialog .
A listener would be able to run a routine whenever the ICAO code changed
* James Turner -- Friday 05 June 2009:
Can anyone (with more experience of the GUI code and Nasal) suggest
how close I can get to a GUI like the one I've mocked-up below:
There are currently two ways:
- make the popup an extra dialog; See the dialog that's shown in Model
View in the lower
9 matches
Mail list logo
