Event loop bug?

Event loop bug?

Post by Christian » Thu, 11 Sep 2008 16:53:21


Hi all,

I've found a possible bug in Tk on Windows, shown by the following script:

================
package require Tk

# update
tk_getOpenFile
entry .e
pack .e
===============

Run it under ActiveTcl 8.4.19 on Windows, select some arbitrary file,
and then it is not possible to enter anything into the entry widget. The
cursor does not appear, it doesn't react on mouseclicks. However, after
uncommenting the "update", it works. The bug is not reproducible on
Linux. I haven't tried 8.5 yet.

Since tk_getOpenFile uses the native dialog on Windows, I suspect some
problem when the main event loop isn't running yet.

Christian
 
 
 

Event loop bug?

Post by Ron Fo » Thu, 11 Sep 2008 20:36:10


Can't reproduce this on ActiveTcl 8.4.14 on Windows Xp-Pro if it's a
defect it is a regression.


--
Ron Fox
NSCL
Michigan State University
East Lansing, MI 48824-1321

 
 
 

Event loop bug?

Post by me » Thu, 11 Sep 2008 21:19:28

In article <ga7udf$b15$ XXXX@XXXXX.COM >,



For what it's worth, both update and non update version seems
fine on 8.5.0 on XP Pro SP3.


I've had odd experiences with native dialogue on Windows,
and it always came down to some random shell extension that
is magically invoked in the background. Usually adobe acrobat
reader, it seems.

--
WL
real mail: wliao at sdf loSnPesAtarM org
(remove the uppercase letters...)
 
 
 

Event loop bug?

Post by Christian » Thu, 11 Sep 2008 23:06:38

WL schrieb:


I see it on 8.4.19 and 8.4.16 on two different machines. Nobody else who
can reproduce it? It took me a while to figure out the update trick. If
one enters the code line-by-line into tkcon, it works, which supposed me
to try "update".
Maybe I should try 8.5... I didn't want to try it until now, 'cause I
have some home-brewn extensions that need to work.


Uh, uninstalling adobe reader is not an option.

Christian
 
 
 

Event loop bug?

Post by Bruc » Thu, 11 Sep 2008 23:24:55


I see same behavior with 8.5.3 on Win XP (service Pack 2)

Bruce
 
 
 

Event loop bug?

Post by MartinLemb » Fri, 12 Sep 2008 02:03:17

Hello Christian,

sorry, but I can not reproduce this behaviour - not with 8.4.16 nor
with 8.5.0.

Sometimes I wonder why an application suddenly does not react anymore
and looking for reasons I often find this little, anoying Adobe
Acrobat Reader window asking me for the preferred language.
It comes up if I hover over or select a PDF file.

Until now I never had such described effect in my applications and I
think the reason will be outside of tcl/tk's scope.
Just because I believe, that such basic scripts won't only run on my
computer that stable - like expected.

Belonging to effects of the tk_getOpenFile dialog or a file selection
box on tcl ...
.... one of our customers used NFS services for Windows (a MS product)
and the namespace provider for the working place in the explorer
loaded a DLL changing the locale that way, that suddenly tcl
recognized "8,1" as floating point instead of "8.1".
So we had to control the locale after each file system related dialog
or to switch the locale brutally back to the one we needed to let tcl
go on in its calculations. (Nowadays in 8.5 times this is not needed
anymore!)

So - I don't expect tcl/tk to be blamed for your described behaviour.

Best regards,

Martin Lemburg

On Sep 10, 4:06m, Christian Gollwitzer <Christian.Gollwit...@uni-

>>>> For what it's worth, both update and non update version seems >>>> fine on 8.5.0 on XP Pro SP3. >> >> I see it on 8.4.19 and 8.4.16 on two different machines. Nobody else who >> can reproduce it? It took me a while to figure out the update trick. If >> one enters the code line-by-line into tkcon, it works, which supposed me >> to try "update". >> Maybe I should try 8.5... I didn't want to try it until now, 'cause I >> have some home-brewn extensions that need to work. >> >>>>> Since tk_getOpenFile uses the native dialog on Windows, I suspect some >>>>> problem when the main event loop isn't running yet. >> >>>> I've had odd experiences with native dialogue on Windows, >>>> and it always came down to some random shell extension that >>>> is magically invoked in the background. Usually adobe acrobat >>>> reader, it seems. >> >> Uh, uninstalling adobe reader is not an option. >> >> Christian
 
 
 

Event loop bug?

Post by Neil Madde » Fri, 12 Sep 2008 02:04:45


[...]

The problem with adobe reader came up not too long ago, in almost
identical circumstances. Check:

http://www.yqcomputer.com/ #

-- Neil