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

List:       kde-core-devel
Subject:    Re: kdesktop wait cursor
From:       mosfet <mosfet () mandrakesoft ! com>
Date:       2001-05-10 5:55:19
[Download RAW message or body]

You didn't even know what the image viewer window was, and were
complaining that it was a splashscreen :P Was that your joke? If so then
why did you include it in a serious discussion against splashscreens as
one of two examples? Use the app, then complain.

The GUI window shouldn't be shown at startup unless you select it,
because if your quickly viewing images why would you want two toplevel
windows? Again, this is why almost all the traditional Unix image
viewers don't do things the way you want it.

If you don't like it, select KView UI mode, but that will never be the
default behavior. 

Carsten Pfeiffer wrote:
> 
> On Donnerstag, 10. Mai 2001 01:12 mosfet wrote:
> 
> > The comparison to Konq isn't accurate at all. It is very useful to have
> > the image show up in it's own toplevel window (ie: so you can have large
> > images scaled to the entire size of the desktop instead of having
> > toolbars and menus taking up space). There are many reasons virtually
> > all Linux image viewers do things the way I do it.
> 
> that's ok, but then it should show the GUI first, instead of a dummy image,
> which forces you to do right-click on it before you can use it.
> 
> > Since you've never even opened up an image in Pixie tho, I guess you
> > don't know this :P I'd actually use the app before telling me what type
> > of UI is more useful...
> 
> That was a joke.
> 
> Cheers,
> Carsten Pfeiffer

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