On Sun, 22 Mar 2009 19:07:12 -0500 "Edward K. Ream" <[email protected]> wrote:
> On Sun, Mar 22, 2009 at 10:41 AM, Ville M. Vainio > <[email protected]>wrote: > > > > > > Indeed there is such an event: QWidget.destroyed. Connecting this > > > event seems to work. > > > > It's actually QObject.destroyed. > > > > It does seem rather hackish (read: error-prone) to rely on that. > > > WARNING: Rev 1666 can totally mess up headlines. Rev 1668 backed out > of the change within 10 minutes of the commit, so hopefully this will > not bite anyone. > > > > > Following Terrys suggestion, why not just rely on: > > > > http://doc.trolltech.com/4.5/qlineedit.html#textEdited > > > Because it doesn't work completely. In fact, the code that we have > been living with for the last several months uses the textEdited > signal. The problem is that textEdited doesn't get generated when > focus leaves the outline. I think I meant: http://doc.trolltech.com/4.5/qlineedit.html#textChanged which catches programatic changes as well, but the real point of my idea was to record the new text as each character is typed, so that they're are not lost. More CPU cycles, but it may make other feedback more dynamic too. I don't care, as long as I can type headline notes on a conference call without losing them. Cheers -Terry > I do hope that Vincent's suggestion to use editingFinished will > work. I'll be testing this tonight. > > For reference, the event handlers should be bound in the > createTreeEditorForItem and editLabelHelper methods. These probably > should be refactored to eliminate the duplicate code... > > Edward > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
