[Pharo-dev] XMLParser does not close input stream
hi, after parsing the input stream is left open, so Dia can't save the next version of my toy-designs. added streamReader stream close. at the end of XMLParserTokenizernextEndDocument this made Dia (and me) happy. cheers
[Pharo-dev] unloading a module used by NativeBoost
hi all, I need to find out a way for unloading a module previously loaded by NativeBoost. Smalltalk vm unload:'mylib.dll' works perfectly, but NB does not like it, How to ask NB to unload a module, or: how to tell NB that one module has been unloaded? thanks
[Pharo-dev] mouse-wheel (on Windows)
hi all, there are some differences between how vm handles Windows messages of type mouse-wheel and all the other ones? It seems to me that primitiveEventProcessingControl suspends vm's message handling, but does not suspend mouse-wheel ones. thanks
Re: [Pharo-dev] how to debug NB?
Il 15/01/2014 19.43, Igor Stasenko ha scritto: On 15 January 2014 17:58, paolo.bernardi...@gmail.com mailto:paolo.bernardi...@gmail.com paolo.bernardi...@gmail.com mailto:paolo.bernardi...@gmail.com wrote: Il 13/01/2014 2.25, Igor Stasenko ha scritto: On 13 January 2014 00:08, paolo.bernardi...@gmail.com mailto:paolo.bernardi...@gmail.com mailto:paolo.bernardi...@gmail.com mailto:paolo.bernardi...@gmail.com paolo.bernardi...@gmail.com mailto:paolo.bernardi...@gmail.com mailto:paolo.bernardi...@gmail.com mailto:paolo.bernardi...@gmail.com wrote: Il 12/01/2014 19.41, Igor Stasenko ha scritto: All i can say that callbacks for handling window events need special handling: - you basically should prevent VM to do event handling during handling of event by callback. Do I achieve that when starting in headless mode? (no ui, no messages...) nope. VM will still run event loop (in ioProcessEvents) and do more or less the same things. that is another reason, btw to bring event loop handling to image level. -- Best regards, Igor Stasenko. Could I prevent VM (as you say, Igor) do process events using primitiveEventProcessingControl? I tried hacking NBFFICallback pvtEnter:stackPointer:primitiveMethod: by disabling events before block execution and enabling them after callback termination. Pharo still works for a while, then crashes. nice try.. now i am out of ideas why else it would be crashing :) -- Best regards, Igor Stasenko. maybe primitiveEventProcessingControl still could be the solution, vm should be already blinded (event processing disabled) when the cb is fired. My nice :) try, instead, just tried to blind vm when cb was already fired. Now I should try to blind vm _before_ any cb is fired. But I'm not sure wxWidgets has chances to ear (and processing) incoming OS events when the vm's thread is freezed.
Re: [Pharo-dev] how to debug NB?
Il 13/01/2014 2.25, Igor Stasenko ha scritto: On 13 January 2014 00:08, paolo.bernardi...@gmail.com mailto:paolo.bernardi...@gmail.com paolo.bernardi...@gmail.com mailto:paolo.bernardi...@gmail.com wrote: Il 12/01/2014 19.41, Igor Stasenko ha scritto: All i can say that callbacks for handling window events need special handling: - you basically should prevent VM to do event handling during handling of event by callback. Do I achieve that when starting in headless mode? (no ui, no messages...) nope. VM will still run event loop (in ioProcessEvents) and do more or less the same things. that is another reason, btw to bring event loop handling to image level. -- Best regards, Igor Stasenko. Could I prevent VM (as you say, Igor) do process events using primitiveEventProcessingControl? I tried hacking NBFFICallback pvtEnter:stackPointer:primitiveMethod: by disabling events before block execution and enabling them after callback termination. Pharo still works for a while, then crashes.
[Pharo-dev] how to debug NB?
Hi all, I'm trying to write a binding of wxWidgets 3.0 into Pharo 3.0. I wrote some glue-code to implement a C interface to wxWidgets (that is C++). I can open windows on the screen of my Winxp-box, I place buttons into them, I change position and size of the windows and I can attach BlockClosures on MOVE and CLICK events. Wow: if a cow-boy like me is able to do that, it means NativeBoost is really magic! Here the question. Sometime Pharo crashes. it happens when an event occurs (and a st callback was attached on). In some sessions Pharo stay alive, in some other it dies. What should I do? Re-compile a vm and run Pharo in debug mode? I'm not sure I could understand the reason of the crash... Thanks paolo --- Questa e-mail è priva di virus e malware perché è attiva la protezione avast! Antivirus. http://www.avast.com
Re: [Pharo-dev] how to debug NB?
Il 12/01/2014 19.41, Igor Stasenko ha scritto: All i can say that callbacks for handling window events need special handling: - you basically should prevent VM to do event handling during handling of event by callback. Do I achieve that when starting in headless mode? (no ui, no messages...)
