Re: [Flightgear-devel] Re: contacting tower
Melchior FRANZ wrote: >* Frank Olaf -- Thursday 20 October 2005 13:03: > >>[...] I am using the versions of SDL, pthread and such from the tarball >>on plausible.org/andy. >> >>Anyway, I applied your patch to today's CVS, and besides the problem >>with HUGE when compiling, all keys are now operating as expected, > > >I don't know what "Andy's SDL" does differently from the official SDL, >but the latter works for me (CVS/HEAD, at least :-). The patch reverts >a bugfix, so it's rather unlikely to get into CVS. > I am still unable to find the appropriate glut libraries to compile with msys. I have however done a clean check out and downloaded the latest SDL libraries from their web page and recompiled. The error is still there, so I don't think SDL is the problem, at least not my versions of it. -- Frank Olaf Sem-Jacobsen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: contacting tower
Melchior FRANZ wrote: >* Frank Olaf -- Wednesday 19 October 2005 10:55: > >>I don't think that is the problem. Pressing 'v' works several times, >>but 'V' works only once. The entries in keyboard.xml are similar.. > > >Which interface have you compiled fgfs with? (non-free) glut, freeglut, >or SDL (./configure --enable-sdl)? > >Which version thereof? > >Whatever interface, I'd try a newer version, maybe even CVS/HEAD. > >Also, if you are using glut, try SDL instead, or the other way around. > >Is the fgfs source really CVS/HEAD (as after doing a $ cvs up -AC)? > > >This looks too strange to suspect a FlightGear bug, but you can also >try to apply the attached patch to src/Input/input.cxx. It reverses >the only relevant change in keyboard handling since a while. It's not >acceptable for cvs, but it would help to falsify it as possible cause. > >m. I have been compiling with SDL, and I do not seem to have the necessary glut libraries to try to make the switch. I am definitely compiling with the latest CVS of flightgear and simgear, and I am using the versions of SDL, pthread and such from the tarball on plausible.org/andy. Anyway, I applied your patch to today's CVS, and besides the problem with HUGE when compiling, all keys are now operating as expected, I was able to press all keys multiple times such as v/V cycled back and forth in the view is as much as I wanted :). --- Frank Olaf Sem-Jacobsen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS compiling error
The same problem is present using MSYS/Mingw with 5min old cvs.. Georg Vollnhals wrote: David Luff schrieb: Cygwin doesn't have HUGE, so change HUGE to HUGE_VAL and -HUGE to -HUGE_VAL and I suspect this should compile. Changing HUGE to HUGE_VAL in simple.cxx solved the problem! Thank you, thank you :-) Have just made a testflight with the new FG version! I guess that we could do something in compiler.h along the lines of #ifdef __CYGWIN__ #define HUGE HUGE_VAL #define -HUGE -HUGE_VAL #endif I tried this *before* I did the "huge-change". I put it between two other #ifdef .. (Microsoft and Borland, as far as I remember) but it caused some other strange errors. May be it was my fault to put it the wrong place or the wrong file (there are two compiler.h files in my Cygwin folder, I changed the one in the SimGear-0.3 .. folder. BTW, Georg, CVS SimGear should compile on Cygwin 3.4.4 now, and CVS FlightGear will probably compile on it if you add #ifdef HAVE_CONFIG_H # include #endif as the first include for every source (cxx or cpp) file where you get the strange error message you reported a while ago. Then send the output of "cvs diff -u" from the FlightGear directory to Erik, and the 3.4.4 problem should be sorted :-) Ok, this has to be done when I have a little more time than this evening, but I will go for it within the next days and report so that you have some feedback. Thank you once again, David, your help saved the day for me! Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d -- Frank Olaf Sem-Jacobsen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] contacting tower
Frederic Bouvier wrote: Quoting Frank Olaf : I just tried the latest compiled snapshot at ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/ and everything work normally, so its only my own compilation that suffers from the problem :( They seemd to rely on different pthreadVC-nd.dlls. It has allways work for me with pthreadVC-nd.dll, but the snapshot required pthreadVC2-nd.dll, could this be the problem? I doubt it is related. I just migrate my own projects to a more recent pthread snapshot that induced the change in library name. The problem with non-repeating keys is certainly a problem with not current keyboard.xml. There was a change by Melchior after I reported a bug and the repeat behavior must be explicit now. Perhaps Melchior can comment as my memory is a bit short on this topic. -Fred I don't think that is the problem. Pressing 'v' works several times, but 'V' works only once. The entries in keyboard.xml are similar.. -- Frank Olaf Sem-Jacobsen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] contacting tower
I just tried the latest compiled snapshot at ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/ and everything work normally, so its only my own compilation that suffers from the problem :( They seemd to rely on different pthreadVC-nd.dlls. It has allways work for me with pthreadVC-nd.dll, but the snapshot required pthreadVC2-nd.dll, could this be the problem? Frank Olaf wrote: Ampere K. Hardraade wrote: On October 18, 2005 05:51 am, Frank Olaf wrote: > >>Another point is that I am not always able to contact the tower when > >>pressing the ' key, even though I am on the correct radiofrequency. > > Er... try flying out of the ATC's control area before you attempt to contact the tower. Ampere It's not the tower that is the problem, it is that the key-press is not recognised more than once, several keys and key combinations are recognised only once in CVS versions I compile. -- Frank Olaf Sem-Jacobsen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] contacting tower
Ampere K. Hardraade wrote: On October 18, 2005 05:51 am, Frank Olaf wrote: > >>Another point is that I am not always able to contact the tower when > >>pressing the ' key, even though I am on the correct radiofrequency. > > Er... try flying out of the ATC's control area before you attempt to contact the tower. Ampere It's not the tower that is the problem, it is that the key-press is not recognised more than once, several keys and key combinations are recognised only once in CVS versions I compile. -- Frank Olaf Sem-Jacobsen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] contacting tower
Buchanan, Stuart wrote: >>Has anyone had the time to look at this problem yet? >>it is a bit >>annoying when flying having a large number of key >>presses available only >>once. Since I don't have any insight into the >>source code I think I >>will do more harm than good if I should try to >>correct it myself (and it >>would take a very long time ;) ) > > >Hi Frank, > >Like you, I don't have enough experience of the code >to be able to delve in and pinpoint your problem, but >I do have a suggestion or two. Suggestions are always welcome :) >- Firstly, do you see this on a 0.9.8 FG install ? If >so, it would suggest that something has changed on >your box, rather than a straightforward FG bug. The problems I described are only present in the CVS version of flightgear. The 0.9.8 release works normally, i.e. I may press every key multiple times and have flightgear respond every time. >- Secondly, could you have triggered anything in the >Accessibility Options on XP like StickyKeys, >ToggleKeys or FilterKeys. They hay be named something >different on XP (I'm looking at a 2k box right now). I >don't really know much about them, but they get >triggered somewhat easily (pressing shift 5 times for >example) and might mess up some key codes. I have checked my settings in control panel and found that sticky keys is turned off. Additionally, the problems with the CVS version are present on both my Windows XP PCs. >- Thirdly, and very speculatively, is there some way >within the properties tree to detect what keys are >currently pressed? Poissibly under the input branch? You might want to see if the key-presses are reaching >FG. I've checked the property browser, but I can't seem to find any property that displays raw keypresses :( >Sorry I can't be of more help. > >-Stuart > -- Frank Olaf Sem-Jacobsen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] contacting tower
Hi, Has anyone had the time to look at this problem yet? it is a bit annoying when flying having a large number of key presses available only once. Since I don't have any insight into the source code I think I will do more harm than good if I should try to correct it myself (and it would take a very long time ;) ) > >>Another point is that I am not always able to contact the tower when > >>pressing the ' key, even though I am on the correct radiofrequency. > > > Since this appears to be a bug I'll continue this discussion on the > developer list.(I assume I shouldn't post this message on both lists?) > Further investigation into the tower communication problem shows that > several of my key presses are available only once. I may lower the > flaps to one notch once, and raise them again once. v cycles the view > multiple times, but shift+v only cycles the view backwards once. I may > only contact the tower once with the ' key, h cycles the HUD, but shift > + h only works once. > This is present both in a two weeks old CVS checkout, and in one from > yesterday. The problem only seems to affect keyboard commands, this is > the commands that are mapped to the joystick like flaps and view cycling > work well multiple times in both directions. > My system is a Windows XP box with service Pack 2, compiled using MSYS. > Please let me know if additional information is required. -- Frank Olaf Sem-Jacobsen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: contacting tower
> >>Another point is that I am not always able to contact the tower when > >>pressing the ' key, even though I am on the correct radiofrequency. > > Since this appears to be a bug I'll continue this discussion on the developer list.(I assume I shouldn't post this message on both lists?) Further investigation into the tower communication problem shows that several of my key presses are available only once. I may lower the flaps to one notch once, and raise them again once. v cycles the view multiple times, but shift+v only cycles the view backwards once. I may only contact the tower once with the ' key, h cycles the HUD, but shift + h only works once. This is present both in a two weeks old CVS checkout, and in one from yesterday. The problem only seems to affect keyboard commands, this is the commands that are mapped to the joystick like flaps and view cycling work well multiple times in both directions. My system is a Windows XP box with service Pack 2, compiled using MSYS. Please let me know if additional information is required. -- -- Frank Olaf Sem-Jacobsen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
