[Pharo-project] Annoying bug: UndefinedObject(Object)>>doesNotUnderstand: #mimeTypes
Hi Mariano, I dont have this problem. But I think I had this problem with an old VM. Can you try the new Win32 setup that is based on 10371: see http://lists.gforge.inria.fr/pipermail/pharo-project/2009-July/010469.html to make sure you have the correct VM and image? Which Win version do you use? Thanks Torsten -- Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate für nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02
On Wed, Jul 8, 2009 at 2:15 PM, Torsten Bergmann <astares@gmx.de> wrote:
Hi Mariano,
I dont have this problem. But I think I had this problem with an old VM.
Can you try the new Win32 setup that is based on 10371:
see http://lists.gforge.inria.fr/pipermail/pharo-project/2009-July/010469.html
I test it and I got the same results. In addition, is a bit random. Sometimes it happens and sometimes it doesn't :(
to make sure you have the correct VM and image?
I was using latest windows VM from here: http://squeakvm.org/win32/release/SqueakVM-Win32-3.11.2-bin.zip and latest image from here: http://gforge.inria.fr/frs/download.php/22610/pharo0.1-10371dev09.07.1.zip
Which Win version do you use?
XP none of you has the same problem? best, Mariano
Thanks Torsten -- Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate für nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
This is strange because it is interpreted as if it were a DropFilesEvent! But this is just a alt + tab. I don't see the relation between and alt + tab and a DropFilesEvent Mariano On Wed, Jul 8, 2009 at 2:47 PM, Mariano Martinez Peck <marianopeck@gmail.com
wrote:
On Wed, Jul 8, 2009 at 2:15 PM, Torsten Bergmann <astares@gmx.de> wrote:
Hi Mariano,
I dont have this problem. But I think I had this problem with an old VM.
Can you try the new Win32 setup that is based on 10371:
see http://lists.gforge.inria.fr/pipermail/pharo-project/2009-July/010469.html
I test it and I got the same results. In addition, is a bit random. Sometimes it happens and sometimes it doesn't :(
to make sure you have the correct VM and image?
I was using latest windows VM from here: http://squeakvm.org/win32/release/SqueakVM-Win32-3.11.2-bin.zip and latest image from here: http://gforge.inria.fr/frs/download.php/22610/pharo0.1-10371dev09.07.1.zip
Which Win version do you use?
XP
none of you has the same problem?
best,
Mariano
Thanks Torsten -- Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate für nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Mariano Martinez Peck wrote:
This is strange because it is interpreted as if it were a DropFilesEvent!
But this is just a alt + tab. I don't see the relation between and alt + tab and a DropFilesEvent
could be some oddness in the Windows event generation/handling. A fix would be to check for a nil file entry in the drop event in ExternalDropHandler class>>lookupExternalDropHandler: Michael
On Wed, Jul 8, 2009 at 3:04 PM, Michael Rueger <m.rueger@acm.org> wrote:
Mariano Martinez Peck wrote:
This is strange because it is interpreted as if it were a DropFilesEvent!
But this is just a alt + tab. I don't see the relation between and alt + tab and a DropFilesEvent
could be some oddness in the Windows event generation/handling. A fix would be to check for a nil file entry in the drop event in ExternalDropHandler class>>lookupExternalDropHandler:
But I think that's not the real problem, just a fix. I am right? What I can see debugging is that HandMorph>>processEvents when it does: Sensor nextEvent that returns: #(3 11623748 4 0 0 0 1 1) which 3 means type EventTypeDragDropFiles... but I wonder why Sensor nextEvent is returning me that in and "alt + tab". best, Mariano
Michael
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Mariano Martinez Peck wrote:
But I think that's not the real problem, just a fix. I am right?
Right.
but I wonder why Sensor nextEvent is returning me that in and "alt + tab".
Somehow that event gets either received from Windows or is generated by the VM for some reason. I'd rather suspect Windows, knowing some of the fun stuff it is doing with events... Michael
On Wed, Jul 8, 2009 at 5:51 PM, Michael Rueger <m.rueger@acm.org> wrote:
Mariano Martinez Peck wrote:
But I think that's not the real problem, just a fix. I am right?
Right.
but I wonder why Sensor nextEvent is returning me that in and "alt + tab".
Somehow that event gets either received from Windows or is generated by the VM for some reason. I'd rather suspect Windows, knowing some of the fun stuff it is doing with events...
mmmm I tried this VM with squeak 3.10.2 and couldn't reproduce it. I guess it is because Sensor refactor. I am not saying InputSensor has the problem, just that perhaps because of this, I cannot reproduce it in Squeak. The strange thing is that this doesn't happend to me in older Pharo versions. What we should do in this case? ask squeak-dev? vm-dev ? thanks! Mariano
Michael
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Mariano Martinez Peck wrote:
mmmm I tried this VM with squeak 3.10.2 and couldn't reproduce it. I guess it is because Sensor refactor. I am not saying InputSensor has the problem, just that perhaps because of this, I cannot reproduce it in Squeak.
The strange thing is that this doesn't happend to me in older Pharo versions.
Is the image side code in 3.10 the same as in Pharo? I mean the drop event handling. Michael
On Wed, Jul 8, 2009 at 6:13 PM, Michael Rueger <m.rueger@acm.org> wrote:
Mariano Martinez Peck wrote:
mmmm I tried this VM with squeak 3.10.2 and couldn't reproduce it. I guess it is because Sensor refactor. I am not saying InputSensor has the problem, just that perhaps because of this, I cannot reproduce it in Squeak.
The strange thing is that this doesn't happend to me in older Pharo versions.
Is the image side code in 3.10 the same as in Pharo? I mean the drop event handling.
weird...Now I can also reproduce it in sq3.10.2-7179dev09.03.1 hahaha The same behaviour
Michael
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (3)
-
Mariano Martinez Peck -
Michael Rueger -
Torsten Bergmann