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

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

[Octave-bug-tracker] [bug #37406] GUI/IDE can't track more than one file


From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #37406] GUI/IDE can't track more than one file saved outside the editor
Date: Thu, 20 Sep 2012 09:36:15 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.6.24-1.fc14 Firefox/3.6.24

URL:
  <http://savannah.gnu.org/bugs/?37406>

                 Summary: GUI/IDE can't track more than one file saved outside
the editor
                 Project: GNU Octave
            Submitted by: sebald
            Submitted on: Thu 20 Sep 2012 09:36:14 AM GMT
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

We're all learning here with this Qt stuff...

Here's an observation about the use of the static function warning.  The
"warning" function sort of halts everything, and isn't the type of thing to
use for notification of a file-update-outside-application.  Note from the Qt
documentation:

QMessageBox::warning

Warning: Do not delete parent during the execution of the dialog. If you want
to do this, you should create the dialog yourself using one of the QMessageBox
constructors.

Yes, we are issuing a warning to the user about the file being saved outside
the file editor, but the problem is that when the warning message is displayed
Qt will not handle another file being updated outside the application.  (Open
two files in the GUI/IDE editor and at the console command line type "touch
file1.m; touch file2.m".  The second file will not be recognized.)

Generally, a program isn't supposed to wait on entry from the user, i.e.,
polling loop. Instead, we'll have to figure out a way, per the documentation's
suggestion, to construct the QMessageBox for the warning and connect some
slots to the signals it issues to handle the user's response.

Let's save this for later when we clear up a few more show-stoppers.  Please
downgrade the report priority.





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?37406>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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