<div dir="ltr">Workspaces have the the ability to accept dropped morphs to bind to it, so you can send messages to the dropped morph.<div>Should be possible to use similar method to bind to a pane in the debugger. </div><div>Just have a menu item for the pane you can drag and drop in the Workspace.</div><div><br></div><div><br></div><div>Best,</div><div>Karl</div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jan 27, 2018 at 12:53 PM, Marcel Taeumel <span dir="ltr"><<a href="mailto:marcel.taeumel@hpi.de" target="_blank">marcel.taeumel@hpi.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div id="m_9181038131179186642__MailbirdStyleContent" style="font-size:12pt;font-family:calibri;color:#000000">
Hi Tim,<div><br></div><div>this sounds more like our Workspace needs a way to hijack another tool's bindings. ;-)</div><div><br></div><div>Best,</div><div>Marcel</div><div><div class="h5"><div class="m_9181038131179186642mb_sig"></div><blockquote class="m_9181038131179186642history_container" type="cite" style="border-left-style:solid;border-width:1px;margin-top:20px;margin-left:0px;padding-left:10px">
<p style="color:#aaaaaa;margin-top:10px">Am 26.01.2018 20:23:48 schrieb tim Rowledge <<a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</a>>:</p>How about a persistent (for varying definitions) text morph view within debugger-land, functioning somewhat like the code view in an explorer. The current inspector views throw away anything when you change the inspector focus, which is both good and bad. Having a persistent place to run snippets would be useful. I’m not sure what the most convenient way to bind it would be. The explorer approach mostly works and is at least familiar even when it does something to annoy you.<br><br>I don’t think it would even have to be within the debugger window strictly speaking. Having an option to open it and put it out of the way could be useful. And we could pre-fill it with happy little lines of code applicable to the object(s) being debugged; imagine CodeProcessCogulator class>>debuggerSnippets returning a list of useful fragments.<br><br>tim<br>--<br>tim Rowledge; <a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</a>; <a href="http://www.rowledge.org/tim" target="_blank">http://www.rowledge.org/tim</a><br>Useful Latin Phrases:- Cave ne ante ullas catapultas ambules = If I were you, I wouldn't walk in front of any catapults.<br><br><br><br>
</blockquote>
</div></div></div></div><br><br>
<br></blockquote></div><br></div>