Page 1 of 1
4.53 to 4.60 upgrade causes error in previously good program
Posted: Mon Jun 10, 2013 8:53 pm
by amc
I have recently upgraded from 4.53 to 4.60
Everything seems to run ok except one program which is now throwing an error (see image).
The error occurs when a button is pressed which has code in "onclick"
the code is
Code: Select all
var filename = get("filename");
pui.download({ "id": filename });
hideElement("FieldSet3");
hideElement("Button3");
applyProperty(getObj("Button5"), "visibility", "visible");
any clues ?
thanks
Tony C
Re: 4.53 to 4.60 upgrade causes error in previously good program
Posted: Tue Jun 11, 2013 12:04 pm
by dieter
Hello,
we also had a problem (lost connection when displaying a window) with version 4.6.0. But Profound has released an new version 4.6.1. Our problem seems to be solved with this update. Maybe your problem is also solved in the new version.
Dieter
Re: 4.53 to 4.60 upgrade causes error in previously good program
Posted: Tue Jun 11, 2013 12:10 pm
by David
This is a known issue in 4.6.0 and 4.6.1, sorry. We are working on a fix for this now, and will advise when an update or patch is available.
Re: 4.53 to 4.60 upgrade causes error in previously good program
Posted: Tue Jun 11, 2013 4:52 pm
by Scott Klement
Sorry about that, guys!
This is now fixed in our development environment, and the fix will be included in our next release (4.6.2). We have not yet decided on a date for that release.
If you can't wait for the next release, please send an e-mail to
support@profoundlogic.com, and we'd be happy to send you a patch to fix your installation.
Re: 4.53 to 4.60 upgrade causes error in previously good program
Posted: Tue Jun 11, 2013 10:54 pm
by amc
updated to 4.61 & applied the 4.62 patches that Scott provided , all good now :)
Re: 4.53 to 4.60 upgrade causes error in previously good program
Posted: Wed Jun 12, 2013 11:28 pm
by Scott Klement
Just to clear up a misunderstanding...
4.6.2 has not yet been developed. There is no update to 4.6.2 at this time (though, I hope we can have one soon.) What I meant to say is that when 4.6.2 (eventually) does get finished and released, that it will fix the problem described in this thread.
The patch I have been giving people is to fix the problem on 4.6.1