Forum Archive

Hi Ole,

I really like the new object inspector. It's a great new feature inside the console. Just a few suggestions from me:
- is it possible to make the panel resizable? Some of the object descriptions are cut off.
- possible to make the objects copy-able? Would be great for searching the correct methode, attribute,... and than just copying into the code.
- and a last one: Why only for console? I would like this feature also within the code editor.

Regards
Tom

P.S.: Thanks for continuing the journey!

is it possible to make the panel resizable? Some of the object descriptions are cut off.

Not planned for now, but I'll keep it in mind.

possible to make the objects copy-able? Would be great for searching the correct methode, attribute,... and than just copying into the code.

That's still on my todo list.

and a last one: Why only for console? I would like this feature also within the code editor.

Well, you could dock the console to the editor to get something similar.

Well, you could dock the console to the editor to get something similar.

Did not realize this.....sometimes the solution is nearer than the problem. This is exactly what I was thinking about.

The search or filter would be handy. Or possibly a locals/globals/all type switch/segment might even be better

A few other improvements ideas for both object inspector and debugger:
1) Support for ObjCInstances. I realize this might not be possible, since it can be sometimes hard to tell which attributes are side effect free. Though I think the same method that works
in objc_util for handling obj.propname=value should work? Or, expand the leaves based on property-like names in dir(), but don't actually call the getter until expanded another level (e.f show frame() as a leaf, then if that is expanded by the user, show the result). Much of the need for this is obviated by suggestion 3 below...

2) Ability to edit basic types in place. I had this basically of working in my crude debugger vdb -- basically an textfield with an action tied back to the appropriate setattr for basic attributes, or setitem for dict and list items.

3) the debugger really needs a mini console, or ability to switch to pdb in the main console. Think "immediate window" in visual studio -- at least for me, that is where the action happens in a debugging session.

@JonB , does your point 3. Infer a floating view? As far as I can see you can't access the inspector while a view is presented. Maybe, there is a way I don't know how to do. I can imagine the activation method could be a little tricky. But for a debugging option, would not be unreasonable to do a weird keystroke combination to invoke it. Like macOS does with sticky keys. Hit the shift key 3 times rapidly to turn it on. Just a idea anyway.

i was suggesting a console conneed to the debug window, which runs a Pdb style command line. Not for the Object Browser, that was debugger specific.