Re: [Pharo-users] gtInspector override default select behavior

2017-08-09 Thread Andrei Chis
On Mon, Aug 7, 2017 at 11:11 PM, Evan Donahue wrote: > Perfect. > > Do you know if these methods are systematically documented anywhere? I feel > like if I understood Glamour better these things might be more obvious, but > I can never manage to infer the gtInspector calls from the Glamour docs.

Re: [Pharo-users] gtInspector override default select behavior

2017-08-07 Thread Evan Donahue
Perfect. Do you know if these methods are systematically documented anywhere? I feel like if I understood Glamour better these things might be more obvious, but I can never manage to infer the gtInspector calls from the Glamour docs. Thanks. -- View this message in context: http://forum.worl

Re: [Pharo-users] gtInspector override default select behavior

2017-08-07 Thread Andrei Chis
Hi, On Mon, Aug 7, 2017 at 5:28 AM, Evan Donahue wrote: > Hello, > > I have a gtInspector extension a tree-structured object. By default, when > I click on one of the objects in the gtInspector, the inspector opens up > another inspector on that node (using the finder-style display). > > What I

[Pharo-users] gtInspector override default select behavior

2017-08-06 Thread Evan Donahue
Hello, I have a gtInspector extension a tree-structured object. By default, when I click on one of the objects in the gtInspector, the inspector opens up another inspector on that node (using the finder-style display). What I would like to know is, is it possible to override the default click beh