[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #43837] Window focus on debug not intuitive
From: |
anonymous |
Subject: |
[Octave-bug-tracker] [bug #43837] Window focus on debug not intuitive |
Date: |
Tue, 16 Dec 2014 17:38:01 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 |
URL:
<http://savannah.gnu.org/bugs/?43837>
Summary: Window focus on debug not intuitive
Project: GNU Octave
Submitted by: None
Submitted on: Di 16 Dez 2014 17:38:00 UTC
Category: GUI
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Incorrect Result
Status: None
Assigned to: None
Originator Name: Wolfgang Rosner
Originator Email: address@hidden
Open/Closed: Open
Discussion Lock: Any
Release: dev
Operating System: GNU/Linux
_______________________________________________________
Details:
I'm still busy debugging qtfm.
In Editor Window, I have to set breakpoints and click stepwise execution
buttons.
In command window (retranslated from German "Befehlsfenster"), I have to enter
keystrokes as required by the code under scrutiny. (in this case, it are only
keystrokes for the less commanda to scroll output)
It happened more than once that I thought I was in Command window, but was in
editor window actually, so keystrokes entered messed upt the code to be
debugged
Proposed solutions:
- mark the active window, g.g by a blue frame (or whatever the theme says)
- switch focus by clicking on window top frame or into empty space in window,
not just in the last line
- in editor, have documents locked by default and deliberately ask for
entering edit state before doing so, so that you cannot change source file
accidentially
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?43837>
_______________________________________________
Nachricht gesendet von/durch Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #43837] Window focus on debug not intuitive,
anonymous <=