[Top][All Lists]

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

[Octave-bug-tracker] [bug #39179] octave_qt_link::do_edit_file always re

From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #39179] octave_qt_link::do_edit_file always returns true even when QScintilla not present
Date: Mon, 20 Jan 2014 06:10:42 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15

Follow-up Comment #8, bug #39179 (project octave):

Yes, that was the idea of the patch/changeset.  I.e., that the GUI sends back
a response that an editor tab was not opened.  The script can then
appropriately respond by opening its own editor, whatever preference that is.

The issue is that we need a solid paradigm for communicating data across the
threads.  It's hard to add new features in an elegant way without that.  To
this point we've avoided using mutex's although there seems no good solution
without them.  They're essential for communicating data from worker (Octave
core) to GUI.  (Worker must suspend momentarily.)  Going the other direction,
there might be an alternative which is to have functions of Octave core
overrided similar to object-oriented programming.  In such a scheme the GUI
would launch the worker and then install it's own functions like "edit" and so
on.  Otherwise, the normal edit would happen.  The latter concept I'm
interested in from a see-what-happens sort of perspective, but the mutex data
exchange I'm pretty much sold on.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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