Strange problem. 
To debug it you can switch to the Spec based debugger:

SpecDebugger register.

Then just trigger a debugger and from the small debugger choose the glamour debugger.
If you still get nowhere send me a problematic image (if you can)
 



On Tue, Jan 21, 2014 at 5:04 PM, Usman Bhatti <usman.bhatti@gmail.com> wrote:
On Tue, Jan 21, 2014 at 3:33 PM, Andrei Chis <chisvasileandrei@gmail.com> wrote:
Are you on windows/linux? (On mac cmd+s should work).

The issue isn't with the GTDebugger. 
In fact, I have a jenkins job that takes a moose image, loads some tools and GTDebugger behaves correctly in this image.
In this customized image, I load some other tools and GTDebugger does not have the accept button neither does it save on ctrl + s.
I'll have to dig a bit deeper to know whats going wrong, may be something wrong with my jenkins config or the image construction script.

I tried to debug GTDebugger to see why the desired actions are not installed in my target image:

GTGenericStackDebugger>>installCodeActionsFor: aPresentation
Halt now.
self installActionsForRootPragmas: self codeActionsPragmas in: aPresentation
 
But my image slowly stops responding. May be I shouldn't be launching a debugger on a debugger ;).

tx.



On Tue, Jan 21, 2014 at 3:15 PM, Usman Bhatti <usman.bhatti@gmail.com> wrote:
Hello,

Ctrls + S in GTDebugger does not save anymore the code source. I'm sure I saw it working before leaving for vacations but it seems the bug has reappeared. Is this still a known issue?


regards,
Usman

_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev