ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> komodo-beta
komodo-beta
[Komodo-3-beta] Interactive Shell comments
by Peter M Buck other posts by this author
Jul 5 2004 8:10AM messages near this date
view in the new Beta List Site
Re: [Komodo-3-beta] Commas in line fools tooltips for arguments | [Komodo-3-beta] "Edit with" doesn't make Komodo top window
I'm glad to see the interactive shell, but it doesn't appear to do
what I was hoping for.

	1) I want to be able to manipulate the variables of a script that
I'm currently debugging.  For example, I'd like to be able to add an element
to an existing array--something that I at least haven't figured out how to
do with the Debug/Locals window.

	2) Also, if I begin debugging a script, then click on F12 to open
the default interactive shell (perl), and then click on (e.g.) Step In,
instead of debugging continuing in the existing Debug window, a new instance
of Debug is opened.

	3) While I'm on the subject, another bug, reported in 31473, still
exists.  Actually, I admit, you might not consider it a bug (I never got any
feedback after the original submission), but it's certainly undesirable
behavior from my point of view.

	Suppose debugging is started on a script (A) and then a second
script (B) is opened in Komodo, so B has focus.  If (for example)  Step In
is clicked on, the original script (A) is given focus and debugging
continues there, rather than a debugging session starting on the script that
currently had focus (B).  I could accept that only one debugging session can
take place at a time (although the behavior reported in (2) above seems to
belie that), but I'd rather have a message telling me that I have to finish
my first debugging session before I can start a new one than to have a step
taken in a debugging session I might really not want to continue with yet.

	- Peter Buck

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved