https://bugs.kde.org/show_bug.cgi?id=427141
Tristan Miller <psychon...@nothingisreal.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO |---
--- Comment #2 from Tristan Miller <psychon...@nothingisreal.com> ---
Well, let me explain how this report arose.
KDialog is more or less a wrapper for the dialog APIs of
frameworks-kwidgetsaddons. With the current Git master of KDialog, invoking
kdialog --newpassword foo\\nbar
results in a new password dialog that says
foo
bar
but invoking it as
kdialog --password foo\\nbar
results in a password dialog that says
foo bar
That is, in one case the newline is being converted to a space and in the other
it is not. The desired behaviour (at least from KDialog's point of view) is to
preserve the newline.
Since the KDialog code for handling the --password and --newpassword options is
pretty much the same, except that one invokes a KPasswordDialog and the other
invokes a KNewPasswordDialog, I assume that the discrepancy in behaviour lies
in frameworks-kdewidgetsaddons. From reading its source, I see that the
setPrompt() function on line 291 of kpassworddialog.cpp invokes
d->ui.prompt->setWordWrap(true), whereas the setPrompt() function on line 264
of knewpassworddialog.cpp does not. I had assumed that this was the cause of
the problem, but did not test this by changing and building the code myself.
If this isn't the cause of the problem, then the cause must lie elsewhere,
though I'm still pretty sure it's in frameworks-kdewidgetsaddons and not
KDialog.
--
You are receiving this mail because:
You are watching all bug changes.
