octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #60051] akward behavior of GUI editor pane (in


From: Hartmut
Subject: [Octave-bug-tracker] [bug #60051] akward behavior of GUI editor pane (in Octave 6.1.90)
Date: Sat, 13 Feb 2021 13:01:06 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:85.0) Gecko/20100101 Firefox/85.0

URL:
  <https://savannah.gnu.org/bugs/?60051>

                 Summary: akward behavior of GUI editor pane (in Octave
6.1.90)
                 Project: GNU Octave
            Submitted by: hardy
            Submitted on: Sat 13 Feb 2021 06:01:03 PM UTC
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Regression
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: 6.1.0
         Discussion Lock: Any
        Operating System: Any

    _______________________________________________________

Details:

I observe two "akward" behaviors in Octave's GUI editor pane. 

This happens under Windows 10 as well as under Ubuntu linux with the current
release candidate Octave 6.1.90. Here is what I mean:

* Open an m file in the GUI editor pane. Use the Octave settings "remember
open m-files in editor". Close this tab of the m-file in the editor. Close and
restart Octave. Result: The m-file does re-open in the editor pane. (But it
should stay closed).

* I also managed to fully remove the GUI content of the editor pane. (I am not
quite sure what I did, but only "normal usage".) Not only are all m-file tabs
now closed, but also the editor stuff itself is invisible (no menu, no icon
buttons). After every start of Octave (GUI) I need to type "edit" into the
console, in order to generate the empty GUI editor console. Only then can I
open m-files in the GUI editor.

This "akward" behavior has already been present in Octave 6.1.0, but I think
it was ment to be fixed (I remember to have seen it somewhere in the repo some
weeks ago), but now I STILL see it in the current release candidate 6.1.90.

Can anyone else see this? Does this has to do with the Qt version change we
did for Octave 6.1.90? 

I would really like to see this fixed, this bothers me a hundred times a day
when using Octave. My hope was, that 6.2.0 will have it fixed anyways, but now
this bug seems to be still staying.




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60051>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]