bugGNU Octave - Bugs: bug #61461, Command Window hide part of the...


bug #61461: Command Window hide part of the line

Submitted by:  Stefan Pofahl <ellocco>
Submitted on:  Wed 10 Nov 2021 04:07:42 PM UTC  
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Other
Status:  Confirmed Assigned to:  None
Originator Name:  ellocco Open/Closed:  Open
Release:  dev Operating System:  Microsoft Windows

Add a New Comment (Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


( Jump to the original submission)

Tue 23 Nov 2021 10:02:59 AM UTC, comment #12: 

Might also be the logical pixels that make the difference if different scaling factors are used on different monitors...

Markus Mützel <mmuetzel>
Project Member
Tue 23 Nov 2021 09:58:07 AM UTC, comment #11: 

All three monitors have the same resolution: 1920x1200

Stefan Pofahl <ellocco>
Tue 23 Nov 2021 09:05:59 AM UTC, comment #10: 

Thanks. So this indeed is the same bug that I remember reading about before.
I still can't find the original report. So, marking this one as confirmed.

If I try to remember the details, ISTR that the command window got cut off at or around the width in pixels of the (smaller) primary monitor.

A long time goal is to replace the command widget with a cross-platform Qt widget. That will probably also resolve this issue.

A work-around is to use the largest monitor as the primary monitor on Windows.

Markus Mützel <mmuetzel>
Project Member
Mon 22 Nov 2021 05:44:28 PM UTC, comment #9: 

Hi Markus,
sorry for the late reply, yes it makes a difference.
If the external monitor is the main monitor the full line is visible, even if the command window is inside the octave main
window (is docked inside / not in separate window). Stefan

Stefan Pofahl <ellocco>
Sun 14 Nov 2021 10:45:05 AM UTC, comment #8: 

comment #3:

> Does changing the primary monitor make a difference to the behavior you observe?

Markus Mützel <mmuetzel>
Project Member
Sun 14 Nov 2021 10:15:26 AM UTC, comment #7: 

Status: "need info":
What is needed? Is there something a can test or report?

Stefan Pofahl <ellocco>
Fri 12 Nov 2021 03:52:41 PM UTC, comment #6: 

OT: yes, those two bug reports describe the situation I was trying to recall, as the subject recently came up in another discourse discussion. thanks for the pointers to direct that part of the conversation.

Nicholas Jankowski <nrjank>
Project Member
Fri 12 Nov 2021 03:26:44 PM UTC, comment #5: 

Off topic:
Afaict, Octave's interpreter is fine with handling non-ASCII characters on all platforms.
IIUC, Stefan was referring to the command window of the GUI. That might be a combination of bug #60683 and bug #59495. But it might also be something different if it crashes Octave entirely (not just the console).

Anyway, let's try and keep this on-topic.

Markus Mützel <mmuetzel>
Project Member
Fri 12 Nov 2021 03:17:41 PM UTC, comment #4: 

regarding your pasting crashes, it was mentioned before that the windows interpreter has issues with non-ascii characters.  copy/paste in the windows interpreter can often produce garbage characters, and pasting those back in, or pasting in text from another source with those types of characters in it (sometimes hidden) can cause Octave to crash. 

Nicholas Jankowski <nrjank>
Project Member
Fri 12 Nov 2021 02:46:17 PM UTC, comment #3: 

ISTR, there were reports that something was off when a "secondary" monitor was larger than the "primary" monitor and depending on whether the secondary monitor extended the desktop to the right or to the left.

Does changing the primary monitor make a difference to the behavior you observe?

Markus Mützel <mmuetzel>
Project Member
Fri 12 Nov 2021 02:19:03 PM UTC, comment #2: 

I am working with three monitors, all with the same resolution:
The configuration is: Laptop with docking-station and two monitors attached to the docking station.
If only a part of the line is visible is in my set-up dependent on the monitor,
e.g. on the build in laptop monitor the GUI is more reliable.
If I move the Octave GUI to the laptop-monitor the whole line can be seen :-)
There seems to be a workaround, if I un-dock the command window the whole line is displayed.
Furthermore, dependent on the total width of the GUI-window it differs how much of the line is hidden.
Attached two screen shots.

The GUI is quite vulnerable against pasting test into the command window, copying test into it can crash Octave.
Since I work with Octave 6.4 for MS Windows I observed at least 10 crashes.

Stefan Pofahl <ellocco>
Wed 10 Nov 2021 05:38:01 PM UTC, comment #1: 

Works for me.

Your screenshot looks similar to bug #53189 (and ISTR other reports I can't find atm).

IIRC, others that reported that issue in the past used a monitor with high DPI or buggy fonts.

Could that apply in your case, too?

Markus Mützel <mmuetzel>
Project Member
Wed 10 Nov 2021 04:07:42 PM UTC, original submission:  

I can see only a part of the whole line inside the command window.

Stefan Pofahl <ellocco>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

Attached Files


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by nrjank (Posted a comment)
  • -email is unavailable- added by mmuetzel (Posted a comment)
  • -email is unavailable- added by ellocco (Submitted the item)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.




    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2021-11-23 mmuetzel StatusNeed Info => Confirmed
        Release6.4.0 => dev
    2021-11-12 mmuetzel StatusNone => Need Info
    2021-11-10 ellocco Attached File- => Added command_window_cut_line.png, #52232

    Back to the top

    Powered by Savane 3.7