Issue 1007 in moose-technology: GTDebugger should bound self to the current object, not to context

Status: New
Owner: ----
CC: [hidden email]
Labels: Type-Defect Priority-Medium Component-GlamorousToolkit Milestone-5.0

New issue 1007 by [hidden email]: GTDebugger should bound self to the  
current object, not to context
http://code.google.com/p/moose-technology/issues/detail?id=1007

Right now, in the first pane of the inspector, self is bound to the  
context. It should be bound to the current object

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Updates:
        Status: Fixed

Comment #1 on issue 1007 by [hidden email]: GTDebugger should bound  
self to the current object, not to context
http://code.google.com/p/moose-technology/issues/detail?id=1007

Name: GT-Debugger-TudorGirba.140
Author: TudorGirba
Time: 16 November 2013, 11:30:53.157003 am
UUID: 405817fb-292b-4f96-b69a-99ae3a39921c
Ancestors: GT-Debugger-TudorGirba.139

Issue 1008: GTDebugger should offer the possibility of browsing the  
selected method
       
Issue 1007: GTDebugger should bound self to the current object, not to  
context


--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev