ActiveState Powered by ActiveState

ActiveState Community


4.2 bugs and feature requests

Posted by jnfarmer on 2007-08-10 09:00

(I'm currently using Komodo 4.2 Beta 6 on SuSE linux 10)

I've been using Komodo Edit and IDE for about a month now at work, while learning Expect/Tcl at the same time, and I really like the product. However, there's a few things I noticed:

  1. Syntax-checking breaks (says 'in progress' forever) if I accidently put variable names in an if-statement with no preceding '$' (Problem is in both 4.1 and 4.2 Beta 6):

    set test 1
    if { test } {
       return 0
    }
  2. The editor view moves back to focus on the current cursor position if the Komodo window is changed (resized, panes opened, etc) while viewing a different section (VERY annoying). This doesn't seem to happen in windows versions.
  3. When you turn one of the panes (left, bottom, or right) off, and then back on again, the blinking cursor dissapears in the editor. If you turn the pane back off again, the cursor is visible once more. If you turn on multiple panes (leaving you with an invisible cursor), just turning one of them off again will make the cursor re-appear. Happens in both linux and windows.
  4. Sometimes the output from a script that is run with Ctrl-r appears in the editor box instead of the output box, overwriting some of my code (have to Ctrl-z undo to restore it). I haven't pinpointed how to reproduce this reliably, but I've seen it happen in both Komodo Edit 4.1 and IDE 4.2 Beta 6. (I've had this happen in linux, but I don't know if this happens in windows -- I use linux a lot more at my job.)
  5. When I run a script inside a namespace, the global variables (for that namespace) all appear in the 'Local' variable tab, and not in the 'Global' variable tab. The Global tab does have a listing for the namespace, but when I expand its tree, it just says "...Next Page..." and lists none of the global variables. It would be very nice to not clutter up the Local tab with all the global variables (or even better, have either way as an option).
  6. [Feature Request] I would like to be able to 'cancel' scrolling, such as by moving the cursor farther away from the scrollbar causing it to snap back to the original scroll point (not cursor point). If this behavior is controlled by the environment that komodo is running on (in Windows, for example, moving away from the bar does cancel scrolling), a shortcut key like 'esc' would be ok instead of moving the cursor away from the scroll bar.
  7. [Feature Request] Display locations of errors and warnings next to the verticle scroll bar (ideally, that you can click on to quickly go to the error). I've seen this kind of thing in lots of other programs (eclipse, file compare programs, etc) and I think it would be a good option to add.
  8. [Feature Request] If you type something like quotes that automatically adds the completing quote, have a way to skip past it easily after you're finished typing inbetween them. Tab seems like it would work well because it currently doesn't do anything when typed in this situation. If you can already do this and I am just ignorant, I appologize :)
  9. [Feature Request] When an error happens while running a script, it shows the line number of the error relative to the start of the procedure (among the reported information). Is it possible to add a way to show local line numbers relative to the start of each proc in the editor window? Perhaps a shortcut that switches between display of normal line numbers for the whole file and line numbers local to the individual procedures(nested within other scopes)?

    Maybe you could let people mouse-over the line numbers on the side of the editor, and if the number corresponds to a local scope, the color of the line numbers for the entire local scope changes color to indicate the user can click on them to switch from global line numbers to local line numbers. (Or whatever.. I'm just tossing around an idea here.)

trentm | Fri, 2007-08-10 11:06

1. could you log a bug for that please?
http://bugs.activestate.com/enter_bug.cgi?set_product=Komodo

2. looking at it... Looks like this is this bug: http://bugs.activestate.com/show_bug.cgi?id=65230

3. That is a matter of focus. When the editor pane has focus, the cursor shows. You could log a feature request (at bugs.activestate.com as above) to have the cursor show without focus on the editor pane -- but I'm not sure if that would be easily possible with our editor component.

4. I suspect it is tied to whether you the "Insert output" checkbox was selected. If there is a current multi-line selection in the current file when your hit Ctrl+R, that dialog guesses that you want to filter those lines so it automatically selected "Insert output" and "Pass selection as input". Perhaps that shouldn't be done by default -- or should be made optional.

5. Could you log a bug for that (will ensure the dev responsible for the debugger will see it)?

6. That scrollbar behaviour is controlled by the system so I'm not sure if that is possible with the GTK-based Linux implementation. Do you know of other Linux apps whose scrollbars display this snap-back behaviour?

7. [Syntax check results] Do you mean in the gutter (the vertical bar on the *left* side of an editor pane)? Yes agreed, that would be handy. What we were hoping to do in a subsequent Komodo version is have a bottom pane tab with "check results" that would provide a clickable list of warnings and error in the current file/all open files/files in the current project. I wonder if that would be sufficient.

8. [Soft Characters] is difficult to use there because *can* be used for "complete word" (see the "Smart Editing" preferences panel). or sometimes typically works -- but, yes, not always. We need to do some thinking about how magic to make . There have been suggestion that also grow to be a trigger for autocomplete (like is now). Toddw: There has been talk of using the ENTER key for performing this soft-char skipping movement, still under discussion, suggestions are welcome.

9. Interesting idea. First time I've seen it suggested. It would be quite difficult for us to get that kind of numbering shown in the line-number-gutter because scintilla (the editor component) handles showing that and it is controlled at a level that doesn't know about the language/syntax of the buffer content.

The mouse-over idea might be possible. This page describes the basic editor-level facilities we have to work with: http://scintilla.sourceforge.net/ScintillaDoc.html
I'm not sure if it provides hooks for a mouse hovering over the *gutter*.

-->