Now when I run FileDelete it throws a message box. Could someone elaborate on this design choice? The error has to be captured via catch or suppressed using try with no complementary catch statement. Is the idea to force users to use try, catch, finally within __Delete?Changed __Delete to catch and report exceptions when called during object cleanup. It previously had the (erroneous) effect of "postponing" the exception until the next function call or the end of the try-block/thread.
__Delete & Unhandled Exception
__Delete & Unhandled Exception
In Version 1.1.28
Re: __Delete & Unhandled Exception
Sounds like a bug - any command should only throw errors when it is inside a Try/catch block.
Could you share the problematic code?
Could you share the problematic code?
Recommends AHK Studio
Re: __Delete & Unhandled Exception
Code: Select all
start({"provider":new test()})
start(obj){
obj.provider := ""
}
class test{
__Delete(){
FileDelete, % this.temp1
try FileDelete, % this.temp2 ; ImageData
try FileDelete, % this.temp3
}
}
Re: __Delete & Unhandled Exception
It's already fixed in the test build via commit bfe39d27.
Re: __Delete & Unhandled Exception
Thanks! I suspect I'm the only person who initializes classes within a temporary object.
Who is online
Users browsing this forum: No registered users and 9 guests