Tk Source Code

View Ticket
Login
Ticket UUID: 1567354
Title: [tk scaling] changes
Type: Bug Version: None
Submitter: nobody Created on: 2006-09-28 22:27:06
Subsystem: 99. Other Assigned To: das
Priority: 5 Medium Severity:
Status: Open Last Modified: 2008-05-06 23:06:29
Resolution: None Closed By:
    Closed on:
Description:
Mac OSX 10.4.7 dual 2.2GHz G5

tk scaling 2.0
puts [tk scaling]
update
puts [tk scaling]
after 1000 {puts [tk scaling]}

The first puts shows the correct scaling factor (1.99 etc).

The second puts sometimes shows that the scaling factor
changed back to 1.

Usually, but not always, it has changed to 1 by the time
the "after" fires.  Once it changes back to 1, if you reset
it to something else, it won't change on its own again.

Changing it to a delay of 100, it usually doesn't change
if it didn't change after the update.

As best I can tell, it didn't do this in 8.4.7, and it does
do it in 8.4.13 and the current cvs head.  I have no idea
if it does this on any other platform.

I thought at first that it had something to do with the
console window, but that was just affecting the timing
and confusing me.

[email protected]
User Comments: jaspert added on 2008-05-06 23:06:29:
Logged In: YES 
user_id=456242
Originator: NO

Under Windows, the scaling value gets reset to its default if a second monitor is connected or removed, or if the machine hibernates and reawakens while a second monitor is connected. 
This is bad, because according to the documentation, the behaviour of existing widgets after a change in scaling is 'undefined'. 
For a canvas, this means that the coordinates from a mouse click or move event no longer correspond to the position of the mouse.