[Pharo-dev] So, again, why 'object inspect' should answer an object?

Igor Stasenko siguctua at gmail.com
Mon Aug 26 16:32:33 EDT 2013


... or another reason to answer the inspector window..
because right now it is badly broken:

EyeInspector class>>inspect: anObject
    InspectorWrapper openInspector: (self inspector: anObject).
    ^ anObject

but:

Morph>>inspectInMorphic: evt
    evt hand attachMorph: ((Smalltalk tools inspect: self) extent: 300 at 200)

that explains why, when i taking the morph's halo
and then use debug context menu and press inspect it,
it puts morph info the hand, and changing its dimensions..
instead of putting inspector  window into hand!

you can imagine how annoying it is, when you want to debug morphic code.

The solution is, of course to answer an inspector window instead of
inspected object.. or, since people argued against this, for such cases,
there should be extra protocol, like

Smalltalk tools inspectorWindowOn: object

(i changed the code to answer a window right now, but we need to solve that
dilemma)

-- 
Best regards,
Igor Stasenko.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20130826/5f8fa65f/attachment-0002.html>


More information about the Pharo-dev mailing list