[pywin32-bugs] [ pywin32-Bugs-1027851 ] cursor stays in interactive window after dblclick

[SourceForge.net <no...@so...>]

Bugs item #1027851, was opened at 2004-09-14 06:55
Message generated for change (Comment added) made by rupole
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1027851&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: pythonwin
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: bob gailer (ramrom)
Assigned to: Nobody/Anonymous (nobody)
Summary: cursor stays in interactive window after dblclick

Initial Comment:
Double-clicking a traceback line (opens and) activates
the module edit window, but the cursor stays in the
interactive window. It would be more useful to have the
cursor appear in the edit window.

----------------------------------------------------------------------

>Comment By: Roger Upole (rupole)
Date: 2008-02-25 17:25

Message:
Logged In: YES 
user_id=771074
Originator: NO

It appears that after the double-click processing
that opens the file and moves the cursor to the
specified line, scintilla unconditionally sets the cursor
back to the location that was clicked.  I may try to work
out some way of setting the cursor asynchronously.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1027851&group_id=78018