Closed leviwilson closed 6 years ago
Could you be more specific, what is the current behaviour and what it should be?
I was more or less using this issue as a placeholder. What I was thinking about doing was to change all of the existing UiaDll.dll
calls to return error information when an exception is caught in the dll like :RA_Click
does. Most of the other calls try to do what you ask, and then eat the exception by logging it out the STDOUT
. We may want to handle this on a case by case basis as far as issues go. I was just thinking there should be more consistency in how we are calling down into UiaDll.dll
.
Why not raise a Ruby Exception when something blows up inside of the dll?
I have to agree that printing out to STDOUT
is really not a good idea.
I agree, I think that it should be doing this.
Closing this due to inactivity.
This is kind of a generic request, but there are methods in the
UiaDll.dll
that output error information if an exception is thrown rather than relaying that information back to the caller. It would be nice to have some consistency in doing this and to allow the caller to decide what to do with the exception.