The Unofficial XCSoar Manual
Advanced:Development/FAQ
From XCSoar
Contents |
Advanced:Development and Code FAQ
Map Window Button Creation
Q: could anyone please tell me where the map window buttons ("nav", "config" ...) are created? Maybee i'm too stupid but I can't find them...
A: In InfoBoxLayout.cpp - InputEvents.cpp constructs them when loading the xci file or initialising the compiled-in version.
Default Input Configuration
Q: I want to change the content of Common/Header/InputEvents_defaults.cpp entries
A: Don't. They are created automatically from Common/Data/Input/default.xci. Once you make the changes in default.xci then you can type "make" in that directory, or run the Perl create script by hand. e.g. "perl xci2cpp.pl default.xci > ../../Header/InputEvents_defaults.cpp". The compile version (Common/Header/InputEvents_defaults.cpp) is only in the repository for convenience.
Q: I want to test my new XCI without recompiling
A: You can load XCI (input) and most other configuration - even the Dialogue XML files - without recompiling.
vibrate.h
Q: I've now installed EVC 4.0 with SP4 and the PocketPC 2003 SDK and successfully build "Win32 (WCE ARMV4) Release", despite errors about not finding file "vibrate.h".
A: The vibrate.h file is due to weirdness with how EVC does precompiled headers --- even if a file include is #ifdef'ed out, EVC still complains if it can't find it.
