A FogBugz case was opened by Stephane Ducasse.
Case ID: 10466
Title: Better interruption
Status: Work Needed
Category: First Impression Counts
Project: Marketing Actions
Area: Misc
Priority: 3 - Must Fix
Milestone: Pharo3.0: 30/03/2014
Assigned To: Stephane Ducasse
URL:
https://pharo.fogbugz.com/default.asp?10466and I could not interrupt anything.
No cmd+. no interdiction sign did anything :(
So is it normal?
Not being able to interrupt something is a pain.
stef
the problem stems from the point that when you press cmd+.
an interrupt process logic looking for some other active process
to stop it..
now since UI process blocked by semaphore, as well as rest,
it finds nothing to interrupt and ignores it :)
i think we should think about it, like putting synthesized context
with '1halt', to UI process, so when it will awake, it will be halted.
Or... if interrupt handler found nothing, then always spawn new UI process
opening debugger on old one.
You are subscribed to this case. If you do not want to receive automatic notifications in the future, unsubscribe (
https://pharo.fogbugz.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&command=view&ixBug=10466) from this case.
_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Locked
