we also sometimes see this.
Most of the time, when you change code in a FID, you have to close and reopen the FID, before the new code works
Also, when you touch or create forms, with the solution Model, we see that changes in code, do not work immediately, but only after a restart of the debug client
i have already a case for this, but how to reproduce?
If you do have some information that you see if i change this (is it always scripting?) then i dont see it.
jgarfield:
At first I thought it was when I used the Solution Model to do things, but I’m not sure thats it anymore.
Before the current version (5.2.2) the solutionModel was definitely a stopper.
As we do a lot of modifications to our forms using the solutionModel (lucky we have tight naming conventions for each element) we had to start the debug client after each change.
Discussing this with Johan resulted in a fix which works absolutely fine!
At this moment I can’t share other situations where I’ve seen this.
jcompagner:
i have already a case for this, but how to reproduce?
If you do have some information that you see if i change this (is it always scripting?) then i dont see it.
I’ll try to find a pattern in when it happens, but I don’t see it yet. I’ve been working in one area of our app recently and it currently seems arbitrary, sometimes I can make a change and it will go through, other times not. I know there has to be some real reason however, so I’ll keep my eyes open.
this is purely about making changes right?
not SVN activities on the files?
Also if you see something that doesnt come through
if you make a new method/function in that js file do you see that appearing in the solution explorer list on that js node? (so i dont mean the outline view but really the list in the Solution explorer view)
This is al purely with js? or also with form design?
When you instantiate custom objects when you start your client and then change the code that does the instantiation or change the code that builds the object, you of course have to re-instantiate the object to see the changes, which usually involves restarting a client.