Re: [Flightgear-devel] Important: input properties

2004-06-25 Thread Innis Cunningham
Christian Brunschen writes I think you misunderstand the scenario I'm sketching at. You seem to be suggesting a scenario with one 'main' configuration, and the ability to focus briefly by selecting a certain part of the panel, with the default panel resuming operation after the user 'deselects

Re: [Flightgear-devel] Some general questions

2004-06-25 Thread Ampere K. Hardraade
I have found another thing that is quite interesting. May be this have something to do with the fact that the opacity of my objects is 98%, but FlightGear seem to have trouble displaying multiple partially transparent objects that are overlapping one another. For example, if I have a plane wit

[Flightgear-devel] f16 model broken?

2004-06-25 Thread Istvan Marko
Since the JSBSIM update some days ago the f16 model stopped working properly for me. The elevator appears to be oscillating randomly, it's seemingly in a different position for each frame update. This is visible in the model animation and the aircraft is uncontrollable. Does anyone else see this?

Re: [Flightgear-devel] Important: input properties

2004-06-25 Thread Ampere K. Hardraade
I suppose I did. I'm sorry about it. =) Regards, Ampere On June 25, 2004 04:16 pm, Christian Brunschen wrote: > > I think you misunderstand the scenario I'm sketching at. > ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org

Re: [Flightgear-devel] Important: input properties

2004-06-25 Thread Christian Brunschen
On 25 Jun 2004, at 20:41, Ampere K. Hardraade wrote: Sorry, I should have quote this instead: Christian Brunschen worte: Consider an aircraft with *lots* of different things that can be changed; including things like autopilot, radios, and so on. Rather than having to have all possible things acce

Re: [Flightgear-devel] help groking the code

2004-06-25 Thread Jim Wilson
Josh Babcock said: > I want to write a program that, given a lat/lon, will return the ground altitude > ASL and the slope (strike and dip). I have poked around in the simgear and > flightgear code a bit, and am having trouble finding where the tiles get loaded > to use as an example. Can some

Re: [Flightgear-devel] Important: input properties

2004-06-25 Thread Ampere K. Hardraade
Sorry, I should have quote this instead: Christian Brunschen worte: > Consider an aircraft with *lots* of different things that can be > changed; including things like autopilot, radios, and so on. Rather > than having to have all possible things accessible from the keyboard - > likely leading

[Flightgear-devel] help groking the code

2004-06-25 Thread Josh Babcock
I want to write a program that, given a lat/lon, will return the ground altitude ASL and the slope (strike and dip). I have poked around in the simgear and flightgear code a bit, and am having trouble finding where the tiles get loaded to use as an example. Can someone point me in the right di

Re: [Flightgear-devel] problem with SGLookupFunction (patch included)

2004-06-25 Thread Andy Ross
Erik Hofman wrote: > Unfortunately RTLD_DEFAULT isn't supported on all platforms (it isn't > supported in IRIX anyhow). I think that if what you describe is the > problem this really is a bug at your side. What happens is that the > function pointer is copied to ftpr. So dlcose() should never be ab

Re: [Flightgear-devel] Important: input properties

2004-06-25 Thread Josh Babcock
Ampere K. Hardraade wrote: I came up with a similar idea a few weeks ago. The panel will have to lost focus automatically when no input is given within a certain time. Regards, Ampere On June 25, 2004 11:17 am, Josh Babcock wrote: Whatever we do, it should be self documenting. There should be a

[Flightgear-devel] Re: problem with SGLookupFunction (patch included)

2004-06-25 Thread Alex Romosan
Erik Hofman <[EMAIL PROTECTED]> writes: > I think that if what you describe is the problem this really is a > bug at your side. What happens is that the function pointer is > copied to ftpr. So dlcose() should never be able to have any effects > on this copy ?? erik, maybe this test program will

[Flightgear-devel] Re: problem with SGLookupFunction (patch included)

2004-06-25 Thread Alex Romosan
Frederic Bouvier <[EMAIL PROTECTED]> writes: > There is probably no problem of not doing dlclose at all. Standard > process exit routine should do it for us. So we could write : > > static void *handle = 0; > if ( !handle ) > handle = dlopen(); > fct = dlsym(); > return fct; or we can call dlo

Re: [Flightgear-devel] Important: input properties

2004-06-25 Thread Jim Wilson
Josh Babcock said: > Jim Wilson wrote: > > > Modelers could perhaps build at the "aircraft specific" versions, so > > that they are there, and the program would default to ignoring these. Users > > who wanted the alternate versions could then deliberately enable them. > > > > Best, > > > > Ji

[Flightgear-devel] Re: problem with SGLookupFunction (patch included)

2004-06-25 Thread Frederic Bouvier
Alex Romosan wrote: > Frederic Bouvier writes: > > > So, if the library is really unloaded, the pointer access should be > > really undefined and could lead to a segfault. Anyway, is it really > > mandatory to do dlclose after getting the pointer ? It is if we do > > dlopen every time we get a po

Re: [Flightgear-devel] Important: input properties

2004-06-25 Thread Ampere K. Hardraade
I came up with a similar idea a few weeks ago. The panel will have to lost focus automatically when no input is given within a certain time. Regards, Ampere On June 25, 2004 11:17 am, Josh Babcock wrote: > Whatever we do, it should be self documenting.  There should be a way to > turn on someth

[Flightgear-devel] Re: problem with SGLookupFunction (patch included)

2004-06-25 Thread Alex Romosan
Frederic Bouvier <[EMAIL PROTECTED]> writes: > So, if the library is really unloaded, the pointer access should be > really undefined and could lead to a segfault. Anyway, is it really > mandatory to do dlclose after getting the pointer ? It is if we do > dlopen every time we get a pointer, but th

[Flightgear-devel] Re: problem with SGLookupFunction (patch included)

2004-06-25 Thread Alex Romosan
Erik Hofman <[EMAIL PROTECTED]> writes: > Unfortunately RTLD_DEFAULT isn't supported on all platforms (it isn't > supported in IRIX anyhow). I think that if what you describe is the > problem this really is a bug at your side. What happens is that the > function pointer is copied to ftpr. So dlcos

Re: [Flightgear-devel] Important: input properties

2004-06-25 Thread Josh Babcock
Jim Wilson wrote: Modelers could perhaps build at the "aircraft specific" versions, so that they are there, and the program would default to ignoring these. Users who wanted the alternate versions could then deliberately enable them. Best, Jim ___ Flig

Re: [Flightgear-devel] Important: input properties

2004-06-25 Thread Josh Babcock
Christian Brunschen wrote: By allowing aircraft to provide hints, we could actually include a few different keyboard & joystick configurations to match different broad types of aircraft, or different broad capabilities (ie, sets of instruments and controls), which could allow those keyboard con

Re: [Flightgear-devel] Important: input properties

2004-06-25 Thread Andy Ross
David Megginson wrote: > Some of these are using the bindings solely to set flap detents > we should find a better system than that. We already do, actually. Take a look at the 747 configuration, you basically just drop in a /sim/flaps section that looks like: 0.000 0.000 0.167

Re: [Flightgear-devel] Important: input properties

2004-06-25 Thread Christian Brunschen
On 25 Jun 2004, at 14:16, David Megginson wrote: Christian Brunschen wrote: What would be really good is if it were possible for the *user* to define an arbitrary number of keyboard / joystick configurations. These could also be named and grouped together; and there should be an easy way to swit

Re: [Flightgear-devel] Important: input properties

2004-06-25 Thread Jim Wilson
Christian Brunschen said: > > Just one personal opinion ... > > What would be really good is if it were possible for the *user* to > define an arbitrary number of keyboard / joystick configurations. These > could also be named and grouped together; and there should be an easy > way to switch

Re: [Flightgear-devel] Important: input properties

2004-06-25 Thread Jim Wilson
David Megginson said: > Jim Wilson wrote: > > > Sorry for the dumb question: why are they offending? I'm in favor of limiting > > aircraft specific key bindings to a very small number of keys (like 1 or 2), > > but I'm also not clear why the input binding configuration needs to be handled > > d

Re: [Flightgear-devel] Important: input properties

2004-06-25 Thread David Megginson
Christian Brunschen wrote: What would be really good is if it were possible for the *user* to define an arbitrary number of keyboard / joystick configurations. These could also be named and grouped together; and there should be an easy way to switch between these configurations, from the keyboar

Re: [Flightgear-devel] Wind direction inconsistency

2004-06-25 Thread Frederic Bouvier
Roy Vegard Ovesen wrote: > I was looking at the clouds at KSFO today and noticed that the clouds were > moving towards the wind as indicated by the windsock. Windsock pointed > towards 80 deg and clouds were moving towards 260 deg. > > I checked the "environment" subtree in the property browser, a

Re: [Flightgear-devel] Important: input properties

2004-06-25 Thread Christian Brunschen
On 25 Jun 2004, at 12:36, David Megginson wrote: Jim Wilson wrote: Sorry for the dumb question: why are they offending? I'm in favor of limiting aircraft specific key bindings to a very small number of keys (like 1 or 2), but I'm also not clear why the input binding configuration needs to be ha

Re: [Flightgear-devel] problem with SGLookupFunction (patch included)

2004-06-25 Thread Frederic Bouvier
Erik Hofman wrote: > Alex Romosan wrote: > > trying to debug why i wasn't able to run flightgear on my laptop, i > > think i found a problem with SGLookupFunction. the problem is that we > > call dlclose() before we return the pointer to the GL function, and, > > if i understand things correctly,

Re: [Flightgear-devel] Important: input properties

2004-06-25 Thread David Megginson
Jim Wilson wrote: Sorry for the dumb question: why are they offending? I'm in favor of limiting aircraft specific key bindings to a very small number of keys (like 1 or 2), but I'm also not clear why the input binding configuration needs to be handled differently than it is now. It's a layering v

Re: [Flightgear-devel] problem with SGLookupFunction (patch included)

2004-06-25 Thread Erik Hofman
Alex Romosan wrote: trying to debug why i wasn't able to run flightgear on my laptop, i think i found a problem with SGLookupFunction. the problem is that we call dlclose() before we return the pointer to the GL function, and, if i understand things correctly, this invalidates the handle and the ad