Rob,

I'd suggest adding this to the bug database as a feature request so it doesn't get lost on the list. I know the bug database is getting bigger all the time, but some of the bugs are actually getting fixed and Martin is doing a great job implementing some of the feature requests for the UI.

Feedback can be added to the bug database as well and if you implement some code for it, you can then refer to the bug # when you post any code.

David


Ok, saw that now. I usually do not start DX from a terminal, but with a
preset-command in my window manager (Xfce in my case) and stdout is rather
hidden that way. Also, what about following:

start vpe in terminal window (dx -edit), make a new network without saving it
and then press ctrl-C (SIGINT) in the terminal. Boom, vpe gone. No message and
nothing saved. Everthing gone!

Since SIGINT is not a fatal interrupt, this is not an emergency. The vpe, or dx in general, should pop up a window whether the user indeed wants to quit without
saving the data. If the anwswer is "no", vpe and dx should continue without
quiting. This holds not only for SIGINT, but for several other non-fatal interrupts.

I haven't looked into detail, but briefly noticed that signal catching is scattered over a whole bunch of files in src/exec/dpexec src/exec/hwrender src/exec/libdx etc. It uses "signal(SIGno, handler)" style, but according to the GNU glibc library this
is not an optimum way of platform independent signal catching:

http://www.gnu.org/manual/glibc-2.2.5/html_node/Basic-Signal-Handling.html


--
.............................................................................
David L. Thompson                   Visualization and Imagery Solutions, Inc.
mailto:[EMAIL PROTECTED]    5515 Skyway Drive, Missoula, MT 59804
                                    Phone : (406)257-8530

Reply via email to