How to solve XWin error?

[Alexander Gottwald]

Jack Tanner wrote:

> Alexander Gottwald wrote:
> > I've though about this today too. I don't like the idea but i don't like
> > answering the same question over and over.
>
> What's not to like? A small bit of code makes a usability problem
> disappear. (Not that I'm offering to write the code.)


On small bit of code creates yet another exception to the general behaviour.

By default XWin prints the dialog box when there is a fatal error. This way
the user is informed there is something wrong. With the change there is one
situation where the dialog box does not appear but the logfile for example
is overwritten with new content which only states there was an attempt to
start a second instance of xwin. Not too easy to debug errors from the first
instance beyond this point.

> Consider how many
> people might be having the same issue but not writing to the list!

Consider how many people are not writing to the list because they search
for "duplicate invokation" and found the answer to their question.

I'm about to add such a workaround, but I have a bad feeling about this "hack"

bye
    ago
-- 
 Alexander.Gottwald@informatik.tu-chemnitz.de
 http://www.gotti.org           ICQ: 126018723