Hi,

sorry for answer so late this... the problem with Storm is that is still work 
in progress... very very alpha (not even usable for real)... I'm doing a heavy 
refactor right now to make it more efficient (gaming and performance are in 
same direction here :), and to make it more suitable to object composition... 
but well, you know... time is tyrant :)

anyway, I you want to make some dig into the fwk, I will be glad to help :)

Esteban

On Apr 11, 2013, at 5:09 AM, Jacob Wagner <[email protected]> wrote:

> If I run the following code in one of the latest pharo 2.0 release images:
> 
> ConfigurationOfStorm project lastVersion load
> 
> (which loads version 0.2 of storm). 
> 
> I get a ton of debug dialogs that pop open saying: 
> "MessageNotUnderstood: StormObject class"
> 
> (in the stderr file i see this, many times)
> StormObject class(Object)>>doesNotUnderstand: #eventPossiblyChanged:
> WeakMessageSend>>value:
> WeakMessageSend>>cull:
> WeakMessageSend>>cull:cull:
> WeakAnnouncementSubscription>>deliver: in Block: [action cull:
> anAnnouncement cull: announcer]
> BlockClosure>>on:do:
> BlockClosure>>on:fork: in Block: [Processor terminateActive].
> 
> Configuration 0.1 works for me.  My platform is windows 7. 
> 
> I also get this error when loading any of the last 4 mcz packages in
> storm-core from monticello after loading configuration 0.1.  
> 
> Thanks for any help with this issue as although I'll be playing around with
> storm 0.1, i'd like to have the latest code working too to work with more
> examples.
> -Jacob 
> 
> 
> 
> 
> --
> View this message in context: 
> http://forum.world.st/Storm-game-engine-bug-tp4680740.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
> 


Reply via email to