28 May 2012 6:49 AM #1
Controller action code does not get saved (restart of SA fixes it.)
Architect Build tested:
- Build: 442
- ExtJS 4.1
- After having worked some hours with SA, I noticed that changes that I was making to controller actions, were not functioning in the browser.
Of course, since the changes were not saved, the deployment task was also not copying the files over....
A restart of SA fixed this. Luckily I copied the changes to my editor, and reinserted them after the restart.
Steps to reproduce the problem:
- Sorry, really, I wouldn't know... it just happened :P
The result that was expected:
- Changes in Controller actions code should be written to disk
The result that occurs instead:
- code is not written to disk
Screenshot, Project, or Video:
- not attached
- not provided
- Vista 64 Ultimate
29 May 2012 8:16 AM #2
Hmm, that's not good! Unfortunately without any way to reproduce this is going to be difficult to track down. Please let us know if you encounter this again and can provide any more information on how to trigger it. We'll keep an eye out for it as well of course.Jason Johnston
Sencha Architect Development Team
29 May 2012 2:45 PM #3
yes, unfortunately I've been using architect only for a few days and this happened during a lot of testing/changing/redesigning, so unfortunately I wasn't focused on what exactly I did that triggered this misbehavior.
However I posted it so you are aware and so that others are warned / may add what triggers this.
If it happens again I'll try to replay the steps that triggers this, so we have a test case.
BTW, Where can I post some Feature requests? In the Help & Discussion Forum?
29 May 2012 2:49 PM #4
29 May 2012 10:22 PM #5
I have ran into this issue before too. (Windows 7 x64) Build 442
My workaround has been to:
1.) Change a existing Controller > Basic Function code.
3.) Deploy (You can see here in the deploy notes that 0 files were copied)
4.) Notice that page is not updated
5.) Include an extra/dummy "view" to the controller that is not deploying.
(Repeat as needed)
8.) Remove extra/dummy view
What happens before #1... not sure what triggers the break. Restarting Sencha Arcitect does fix the issue, as well as view trick.
-- This happens more often when I am making very small changes
-- Usually fast Save(CTRL+S) + (click ok) + Deploy(F5) + (click ok) <-- fix this clicking breaks my workflow... lol
-- All our Sencha Architect Ext JS apps have remote data (model/stores).
I would estimate that the code which is checking for a state change is not capturing the change, you may have race conditions on the diff check/save/deploy.
No visibility/console output to provide insight...
29 May 2012 11:48 PM #6
Thanks for confirming this. It hasn't happened to me again, yet .
As for the 'clicking' thingy, I have opened 2 Feature Requests for workflow optimization here:
30 May 2012 6:46 AM #7
Thanks @CasualNetworks for the info. I still haven't reproduced it but your observations might be enough to steer us in the right direction at least, so I've opened a ticket linked to this thread so that it doesn't get lost.
Anyone, if you have more observations on how to reproduce this, please add them to this thread. Thanks!Jason Johnston
Sencha Architect Development Team
29 Aug 2012 8:14 AM #8
I'm experiencing the same issue, however a restart of Architect does not fix the issue.
My issues (assuming they're related):
- Controller action code is not being saved correctly
- Creating a new controller and dragging an existing action to the new controller doesn't help. The code appears to be saving, but the actions aren't ever run when fired.
- Probably related, when I drag an action between existing controllers, the code reverts if I've had that action in the controller previously.
29 Aug 2012 8:22 AM #9
29 Aug 2012 8:38 AM #10
Thanks for the quick response aconran - seems like you're always on the ball.
I wrote wrong, when I said controller action, I should've said application action.
As for the controllers... In my frustration with things not saving, I've tried creating new controllers and/or dragging application actions between old (working) controllers. I've moved things around a bit trying to get something to work I can get code to work if I drag into an older working controller, but logically it doesn't make sense to have it there - hence the moving around to try and get my program to both work, and be logical.
In this process of moving application actions around between controllers, if I'd had it there previously, the action reverts to whatever the previous definition of the action was in that controller - even if I'd modified the action. The expected behavior would be if I had edited an action and then dragged it to another controller, the code of that edited action would go along with the move.
I did a little poking around in my metadata folder and can see that though I've created a new controller it isn't being added to my Application file - even though the controller exists in the metadata controllers folder.