I think this is one of those bugs really easy to debug if you build your
kde+qt in debug mode.
Just debug it until you get the behavior, add a break point at the doc
input or even the undo point, and follow from there...
Of course compiling kde + qt in debug just for this is quite allot of
time investment for me right now.
Maybe in a little while, like at the end of next month.
That's why I was hoping that the dev responsible for this widget would
pick it up.
:p
Thomas Olsen wrote:
> On Friday 19 February 2010 22:04:24 Trent Shea wrote:
>> On Friday 19 February 2010 13:58:59 Trent Shea wrote:
>>> You should get 'foowobarrd'
>> Which looks a bit different than the OP... either way, not the expected
>> output
>
> And definitely worthy of an entry in bugs.kde.org even tho it's hard to
> trigger?
>
___________________________________________________
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
