Boris Koenig
Frederic Bouvier wrote:
Combo arrows are 16 pixels wide, so the input is -6 pixels . ( The width
is not in
characters but in pixels )
thanks for the explanation, but I was aware of that.
And NO, this problem did not only occur with a width
specification of = 16, but rather =
Boris Koenig wrote:
There seem to be some issues regarding the XML file processing
and FlightGear's stability:
#Nasal parse error: empty subexpression in command, line 3
#Failed to execute command nasal
#Segmentation fault
The XML you posted contains no Nasal script, so I'm at a
Andy Ross wrote:
Boris Koenig wrote:
There seem to be some issues regarding the XML file processing
and FlightGear's stability:
#Nasal parse error: empty subexpression in command, line 3
#Failed to execute command nasal
#Segmentation fault
The XML you posted contains no Nasal script,
Boris Koenig wrote:
Frederic Bouvier wrote:
In fact, the combo's arrow is 16 pixels wide and an input must be at
least 15 pixels.
That means that every combo that are 31 pixels or less
are causing a segfault in a function named chop_to_width
in puInput.cxx.
okay, makes sense - even
There seem to be some issues regarding the XML file processing
and FlightGear's stability:
# Nasal parse error: empty subexpression in command, line 3
# Failed to execute command nasal
# Segmentation fault
One problem seems to be related to using combo boxes with insufficient
