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

List:       kde-devel
Subject:    AW: visibility?
From:       "Ferdinand Gassauer" <f.gassauer () aon ! at>
Date:       2000-03-08 8:11:02
[Download RAW message or body]

I think it's very important - specialy NEW KDE users - who are not used the
fact that KDE application will not crash but load ;-) should NOT be left
uncertain what happens, when loading takes a bit longer (for some good or
even bad reasons).
cu
fedinand


> -----Ursprüngliche Nachricht-----
> Von: Hummel, Timo [mailto:timo.hummel@sap.com]
> Gesendet am: Mittwoch, 08. März 2000 08:58
> An: 'kde-devel@kde.org'
> Betreff: RE: visibility?
>
> this is maybe a funny thought, but how about this:
>
> AFAIK, it is possible to catch a segmentation fault.
> AFAIK, every KDE application is based on C++ and you can put some
> extra code
> into the init code of a class.
>
> This gives me 2 ways to solve both problems:
>
> 1.) Whenever a segmentation fault is catched (I guess this could also be
> implemented in the KApplication base class),
>     the application shows some error message. Additionally, an application
> programmer could overload the
>     crash method (name it whatever you like) to save important data, or to
> save debug informations.
>
> 2.) Whenever KApplication initializes, the user gets some visual feedback
> (like a progress bar or a simple message
>     box that the application is loading right now).
>
> I don't think this is very hard to realize, and would only require that
> current applications re-compile. If there are
> enough requests to show this on existing applications, I would
> start to make
> a patch for the current KDE 2 snapshot
> and try this on some applications. If it works well, why don't we use it?
>
> Laters
> Timo
>
>

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