On Friday, December 3, 2010, David Faure wrote:
> I guess your point is "KDialog should remember and make the button default
> once it exists". Hmm. It can be done indeed. I don't know if it's worth the
> additional complexity, but if you feel this should work, please review the
> attached patch. U
[ksnapshot was indeed fixed rather long ago for this, but let's discuss the
kdialog behavior]
On Thursday 02 December 2010, Aaron J. Seigo wrote:
> it's KDialog that making the assertion; and the assertion looks bogus since
> it's absolutely plausible that the app requests the default to be a but
Em Quinta-feira, 2 de Dezembro de 2010, às 19:23:54, Aaron J. Seigo escreveu:
> On Thursday, December 2, 2010, Chani wrote:
> > #13 0xb67f1444 in qt_assert (assertion=0xb71f93c8 "defaultButton() ==
> > newDefaultButton", file=0xb71f91f0
> > "/home/chani/src/kde/kdelibs/kdeui/dialogs/kdialog.cpp", l
On Thursday, December 2, 2010, Chani wrote:
> #13 0xb67f1444 in qt_assert (assertion=0xb71f93c8 "defaultButton() ==
> newDefaultButton", file=0xb71f91f0
> "/home/chani/src/kde/kdelibs/kdeui/dialogs/kdialog.cpp", line=311)
>
> was this ksnapshot's fault for asserting such a thing, or kdelibs' fault
