Tk Library Source Code

View Ticket
Login
2026-11-16
00:07 • Ticket [79747a0cb5] notifywindow error in successive calls status still Open with 3 other changes artifact: f5f03a0801 user: serhiy.storchaka
00:01
Follow-up to [db81761a73] for [79747a0cb5]: when a notification replaced one which was still shown, the pending fade_in and fade_out events of the old window still ran, and faded out and destroyed the new window early. Cancel them. Add notifywindow.test. leaf check-in: e6328aa17c user: serhiy.storchaka tags: notifywindow-cancel-timers
2026-09-10
19:21
Fix for bug [79747a0cb518] leaf check-in: db81761a73 user: emiliano tags: bug-79747a0cb518
19:16 • New ticket [79747a0cb5] notifywindow error in successive calls. artifact: eef6e3153a user: emiliano

Ticket UUID: 79747a0cb518c6d3ef5ff5a41333838b1bcd2a70
Title: notifywindow error in successive calls
Type: Bug Version: 1.0.2
Submitter: emiliano Created on: 2026-09-10 19:16:56
Subsystem: (unused) Assigned To: nobody
Priority: 5 Medium Severity: Minor
Status: Open Last Modified: 2026-11-16 00:07:23
Resolution: None Closed By: nobody
    Closed on:
Description:
calling notifywindow::notifywindow while the notify window already exists raises an error

% package require notifywindow
1.0.2
% foreach msg {hello world} {
    notifywindow::notifywindow $msg ::tk::icons::information
}
window name "_notify" already exists in parent
User Comments: serhiy.storchaka added on 2026-11-16 00:07:23:

Branch bug-79747a0cb518 destroys the old window, but its pending fade_in and fade_out events still run, so the new notification is faded out and destroyed before its time. Proposed fix on top of it in branch notifywindow-cancel-timers: these events are cancelled.