Hello,
While investigating a destroy issue in our application we noticed that 'ClassFactory.getNextGlobalIDForClass("Canvas")' can return ID's which are 'unexpected'. Sometimes it returns 'isc_Toolbar_36' when called with 'Canvas' arguments.
I know that that isn't necessarily a problem though, it just caught our eye.
What does seem to be a problem is that it returns ID's that still have a matching object. We have a case where a certain Canvas is destroyed when we destroy a grid on a totally different page/tab in our application. I'm not yet sure what's the actual cause is but it seems to be pointing to faulty re-use of ID's.
I recall similar problems when we where switching from the 3 to the 4 release a while ago.
We are on v9.0p_2013-10-17/Pro Deployment (built 2013-10-17) - are you aware of any fixes applied after that to fix similar issues?
While investigating a destroy issue in our application we noticed that 'ClassFactory.getNextGlobalIDForClass("Canvas")' can return ID's which are 'unexpected'. Sometimes it returns 'isc_Toolbar_36' when called with 'Canvas' arguments.
I know that that isn't necessarily a problem though, it just caught our eye.
What does seem to be a problem is that it returns ID's that still have a matching object. We have a case where a certain Canvas is destroyed when we destroy a grid on a totally different page/tab in our application. I'm not yet sure what's the actual cause is but it seems to be pointing to faulty re-use of ID's.
I recall similar problems when we where switching from the 3 to the 4 release a while ago.
We are on v9.0p_2013-10-17/Pro Deployment (built 2013-10-17) - are you aware of any fixes applied after that to fix similar issues?
Comment