-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gci error handling (part 1 - click on Explorer in launcher) #6
Comments
We're not getting the error from FFI as I was expecting, but while playing around I did see an FFI error come up along with a number of other errors, so the mystery is why is there a delayed or missing response to the GCI error ... I will spend some more time next week digging a bit deeper into things to see what's happening ... |
As a first step I left the
So at least for a direct connect logic the GCI error is being caught almost immediately ... when the same thing is done from pharo there is no immediate error, but the MNU for #addDefaultExplorer is a side efect of the #newDefaultTakspaceLayout command not returning a value ... and I would have expected that the gci error would have been delivered to the FFI side immediately ? |
In an attempt to test the new GCI Error handling in SparkleFFI, I added
Exception new _signalGciError.
toRsrSendMessage>>executeFor:
(picked at random):The GCI connection is opened and when I click on the
Explorer
buttonm I get the following Pharo error:At this point, I'm not sure why the gci error is not being seen ... and can't tell if the explorer or RSR is masking the error or what ... the same thing happens if I put a
halt
in the same place ...The text was updated successfully, but these errors were encountered: