[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: feedback
From:       zander () microweb ! nl
Date:       1999-11-02 11:56:53
[Download RAW message or body]

> Rik Hemsley wrote:
> > 
> > #if Stephan Kulow
> > > Hmm, that would only help if the application isn't installed. If it for
> > > examples fails to open because of missing library is not clear. The
> > > feedback is needed since KDE 1.0 - it's just that noone implemented
> > > it :)
> > 
> > I've done it here, using some DCOP stuff with kapp, KRun and kicker.
> > 
> > It's not perfect, but it works...
> > 
> > As soon as any app is started via KRun you get a taskbar entry. As soon
> > as the app gets to KApplication::parseCommandLine() the taskbar entry
> > is removed. When the window maps, the 'proper' taskbar entry appears.
> > 
> > The problem is that there's a delay between KApplication::parseCommandLine()
> > and the first window mapping.
> > 
> > Suggestions welcome. If we could find out when an app's first QWidget hits
> > the screen it'd work... but it'd be better in KTMainWindow.. but not every
> > app uses that :) I don't know a proper solution.
> > 
> eventFilters I say - eventFilters! :)
> 
> But this will only work in the working situation. What if it doesn't
> work
> and the process dies before main?
> 

I think we could presume sh does work, and the error message from sh could be 
properly displayed in a window (stderr -> window) in this case.


--
Thomas Zander                                                zander@microweb.nl
Today, it's understood that of course you'll use a computer,
because it makes other people's lives easier -- or, more         icq: 970 00 05
accurately, it enables them to maintain their manic pace.      gpg-key:  0588D5

[prev in list] [next in list] [prev in thread] [next in thread]