Re: Communicating with GUI

[Rik]

On 04/08/2013 09:21 AM, address@hidden wrote:
> Message: 8
> Date: Mon, 08 Apr 2013 12:20:54 -0400
> From: "John W. Eaton" <address@hidden>
> Cc: octave maintainers mailing list <address@hidden>
> Subject: signal/slot communication for the workspace model/view
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> I checked in another set of changes that alter the way Octave
> communicates with the GUI:
>
> http://hg.savannah.gnu.org/hgweb/octave/rev/0f143f68078d
>
> This patch is for passing workspace info to the GUI using
> signals/slots.  Updating the workspace view should be relatively fast
> and reliable now but there is still room for improvement.  We are
> still rebuilding the entire list every time Octave prompts for input.
> Instead, we should be tracking whether the symbol table has changed
> and only update if needed.  Further, we could cache the info attempt
> to update only the portions of the data that have actually changed.
4/8/13

John,

There was a note on the Maintainer's list about this, but somewhere in the
abundant series of changes in the last week the communication between the
pager and the GUI has regressed.

I'm now back to the ancient behavior where if I use a command like 'help
ver' the GUI displays the first screenful of information and then waits for
a prompt.  But the keystroke for continuing paging needs to be entered in
the original shell window that launched the Octave GUI rather than in the
GUI itself.  Actually, it seems that the keystroke is captured by the GUI
but I have to hit <ENTER> in the shell window.  This behavior is with
changeset 16467:cc9e2751e073.  I could do an hg bisect if you want, but
perhaps you have an idea about where the problem lies.

--Rik

signature.asc
Description: OpenPGP digital signature