bugGNU Octave - Bugs: bug #44257, GUI command window garbled when...

 
 

bug #44257: GUI command window garbled when maximized, ok, when non-maxed

Submitted by:  None
Submitted on:  Sun 15 Feb 2015 10:15:43 AM UTC  
 
Category: GUISeverity: 3 - Normal
Priority: 5 - NormalItem Group: Incorrect Result
Status: FixedAssigned to: None
Originator Name: Ingmar GutberletOriginator Email: -unavailable-
Open/Closed: ClosedRelease: 3.8.2
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 Jump to the original submission)

Tue 10 Mar 2015 02:01:11 PM UTC, comment #13:

I tried the 4.0.0-rc1 and it solved the problem in Windows8.1.

Thanks for the link.

Garth Schmalenberg <gschmalenberg>
Sat 07 Mar 2015 03:28:53 PM UTC, comment #12:

Windows XP may not be a supported version for Octave. This remains to be seen, but there are significant problems with segmentation faults that only occur on that platform.

So, since this fix works on Windows 7 and above I'm going to mark this fixed.

Rik <rik5>
Project Administrator
Sat 07 Mar 2015 12:41:58 PM UTC, comment #11:

I tested this on WinXP SP3 and on Win7 x64 Pro. I uninstalled 3.8.2 on both first, also removed ~/.octaverc and ~/.octavehist to avoid possible side effects, then installed 4.0.0rc1.

WinXP, Screen 1920x1080 96dpi : Upon first start of 4.0.0rc1 the screen came up maximized and garbled as before, but no further starts of 4.0.0rc1 produced a garbled screen. Since this happened at least once with 4.0.0rc1 as well, I have attached a screenshot of this, should this ever pop up again.

Win7, Screen 1920x1080 96dpi: No problems with garbled screen before, none now.

(file #33279)

Ingmar Gutberlet <gutberle>
Sat 07 Mar 2015 02:15:56 AM UTC, comment #10:

I uninstalled 3.8.2 and installed 4.0.0.0 rc1 and didn't see any problem with the cursor not moving in either the command window or the editor. I'm running windows 8.1

Delbert Johnson <del_johnson>
Fri 06 Mar 2015 06:38:38 PM UTC, comment #9:

I don't know for certain, but I think it would be best to uninstall 3.8.2 and then install the new one.

Rik <rik5>
Project Administrator
Fri 06 Mar 2015 06:33:17 PM UTC, comment #8:

Can I install the RC side by side with a 3.8.2 release?

Ingmar Gutberlet <gutberle>
Fri 06 Mar 2015 04:44:28 PM UTC, comment #7:

Could you try the new 4.0 Release Candidate of Octave and see if the problem remains. It is available at ftp://alpha.gnu.org/gnu/octave/octave-4.0.0-rc1-installer.exe.

Rik <rik5>
Project Administrator
Fri 06 Mar 2015 01:46:17 PM UTC, comment #6:

Not sure if this is the same issue but when typing, the cursor doesn't move to the end of the command line so constantly overwrites characters that have already been typed. I tried minimising and maximizing the window and also setting different screen resolution and still the same result, I am running windows 8.1

Garth Schmalenberg <gschmalenberg>
Sun 22 Feb 2015 07:45:27 PM UTC, comment #5:

I posted a comment on bug #41938 (and a possible solution) based on the suggestion by Torsten. It could be that these two problems are related. Please refer to bug #41938 for further information.

The information in #41938 should be considered prior to releasing version 4.0.

Delbert Johnson <del_johnson>
Sun 22 Feb 2015 09:11:29 AM UTC, comment #4:

I guess the issue you are seeing is the one reported in bug #41938 since there are no non printable characters in your terminal as reported here. Are you using a scaling factor of 150% or higher for your display?

Torsten <ttl>
Project Member
Sat 21 Feb 2015 09:45:45 PM UTC, comment #3:

I have the same problem. My max screen resolutions on my Lenovo Yoga Po 2 is 3200 x 1800 which is considerably higher than the 1920 x 978. If this is a new trend then the 4.0 release needs to account for it.

What I see are the text lines overlap vertically and the cursor overlaps horizontally the 2nd >> prompt and is elevate slightly above it.

The other windows do not display this problem.

I have included a screen shot of just the command window

I am running Windows 8.1 on a 13.3 inch laptop display

(file #33146)

Delbert Johnson <del_johnson>
Sun 15 Feb 2015 05:14:48 PM UTC, comment #2:

This has very likely been fixed. Octave is in the midst of generating a 4.0 release which will be the first to officially support both a GUI and the MS Windows OS (3.8.2 is experimental for both of those features). When the first 4.0 release candidate is available I would ask you to download and verify whether this bug still exists.

Rik <rik5>
Project Administrator
Sun 15 Feb 2015 12:11:50 PM UTC, comment #1:

I just did some more testing and found that this has to do with screen size per se and not with window maximization.

I can dynamically provoke an instant switch from readable text to garbage by dragging the window size in x and y direction (or both, of course).

There seems to be a critical threshold around ~1.9 MPixel total, but there are no definite x or y borders. 1920x977 works as does 1755x1080, but 1920x978 fails as does 1756x1080 and even these threshold values vary +/-1-2 pxls x or y upon successive trials.

Ingmar Gutberlet <gutberle>
Sun 15 Feb 2015 10:15:43 AM UTC, original submission:

I installed the MXE build of 3.8.2 on my WinXP home machine and am reliably running into the following problem with the GUI version.

Whenever I start the gui version in maximized windows mode (1920x1080), the gui command window shows only completely garbled non-printable characters.

If I then reduce the window size, the command window shows the expected text. Maximizing and reducing reliably switches between garbage and text.

If I quit the gui version in non-maximized size and restart, it comes back up non-maximized and shows text, but if I then maximize the window it again shows garbage, etc.

If I close (~hide) the command window in maximized mode by clicking the "X" close button in the upper right and then close Octave and restart, Octave comes back up maximized and with a command window showing the expected text and no garbage, even if I cycle between reduced window size and maximized windows size.

However this is a one-timer and the next time I close Octave, it comes back with garbage in the maximized window or with text in the reduced window, but with cycling between the two prompting the garbage display.

Anonymous

 

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

Attach File(s):
   
   
Comment:
   

Attached Files
file #33279:  Octave_400rc1_GarbledScreenError.jpg added by gutberle (716KiB - image/jpeg - Screenshot of garbled screen upon first start of 4.0.0rc1)
file #33146:  Command_Window_Text_Overlap.bmp added by del_johnson (101KiB - image/bmp - Screen shot of just the command window)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by gschmalenberg (Posted a comment)
  • -unavailable- added by ttl (Posted a comment)
  • -unavailable- added by del_johnson (Updated the item)
  • -unavailable- added by rik5 (Posted a comment)
  • -unavailable- added by gutberle (Posted a comment)
  • -unavailable- added by None (Submitted the item)
  •  

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

    Only project members can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 4 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sat 07 Mar 2015 03:28:53 PM UTCrik5StatusNone=>Fixed
      Open/ClosedOpen=>Closed
    Sat 07 Mar 2015 12:41:58 PM UTCgutberleAttached File-=>Added Octave_400rc1_GarbledScreenError.jpg, #33279
    Sat 21 Feb 2015 09:45:45 PM UTCdel_johnsonAttached File-=>Added Command_Window_Text_Overlap.bmp, #33146

    Back to the top


    Powered by Savane 3.1-cleanup1