On 05/19/2012 10:54 PM, Scott Kostyshak wrote:
When you reconfigure by going to Tools > Reconfigure, if the python
script returns a non-zero exit status, a useful GUI error is
displayed. However, when configure is run from LyX.cpp on the first
run, you can only see if there is an error in the terminal and this
will pass unnoticed by most. To test this case, in configure.py put a
system.exit(1) just before sys.exit(ret is not None) at the end and
force a startup configure (for example by renaming your .lyx folder).
Is this a problem that should be fixed?
I think we've had complaints that this would resolve, yes.
If so, what is the best design? Should a bool be passed to the
Application constructor?
I think the GUI is accessible at this point---if use_gui is true. So you
might just try something like:
if (use_gui)
frontend::Alert(...);
else
LYXERR0(...);
at the relevant point. If not, then we need more complex return values
from init().
Richard
