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

List:       kde-core-devel
Subject:    Re: Screenshot [Was [PATCH] Distinguish Read-Only KLineEdit from Read-Write one...]
From:       Dawit Alemayehu <adawit () kde ! org>
Date:       2002-03-21 21:25:39
[Download RAW message or body]

On Thursday 21 March 2002 15:50, Martijn Klingens wrote:
> On Thursday 21 March 2002 21:17, Dawit Alemayehu wrote:
> > There are very valid reason why it needs to be a lineedit.  People might
> > want to copy one or more of the cookie text for whatever reason and worst
> > of all the cookie value text can be very very large.  A QLabel is not
> > well suited for show a really really long text IMHO.  I only point to the
> > many discussions about this very issue on many dialogs one of which was
> > even designed by me (the authentication dialog).
>
> Like I said , and like other people also mentioned, that can be done with a
> QLabel derived class. KMessageBox already does that. (Also as a reply to
> David's post :)

I did not check, but I think KMessageBox uses a KActiveLabel which is not a 
QLabel but rather a QTextBrowser.   I agree with this being an appropriate 
thing for KMessageBox to use.  However this is an even more overkill for the 
circumstances I am using these read-only lineedits.  Secondly, you can and 
should be able to set the focus on this readonly lineedits to select the text 
using the keyboard only.  This is not and IMHO should never be the case ? for 
"message" in a mesage box.  IMHO there are places where lineedit should and  
should not be used and I do not think I am abusing it, but of course I would 
say that :)

BTW using KActiveLabel in the progress dialogs to show really long paths does 
not make sense for example.  However, a readonly lineedit would work and IMHO 
it will be a much better solution than squeezing a QLabel and forcing the 
user to expand the dialog to see the whole path.

Regards,
Dawit A.

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