Re: Testing MXE-Octave

[Daniel J Sebald]

On 02/11/2013 04:14 PM, PhilipNienhuis wrote:
> John W. Eaton wrote
> > On 02/11/2013 01:38 PM, Philip Nienhuis wrote:
> >
> > > Here's some feedback on the most obvious glitches I found in the
> > > previous version (with 3.7.1 snapshot):
> > <snip>
> > > - The GUI's workspace pane isn't functional - entering something like "a
> > > = 10" doesn't make a show up in the workspace.
> >
> > Yeah, there are lots of problems with the GUI.  I don't think that these
> > problems are specific to the MXE cross build.
>
> IIRC it worked OK with the 3.7.1 snapshot on Linux, so I suspect is *is*
> related.
> The UPM version (admittedly based on 3.6.2) doesn't have this issue. On all
> recent Linux builds I've made the workspace pane works good as well.

The manifestation may be related to the build, but I think the general 
feeling is that there are some quirks to work out of the GUI still.  One 
in particular--and I think this is the one related to what you are 
seeing--is the workspace appears to stick.  That is, one can type some 
lines and get a response, but something like switching windows or 
dumping to the pager (not quite sure), causes the workspace window to 
freeze.  Move the position slider around and it can bring back the text 
somehow.  (It seems to be the text output that is the problem, while the 
typed commands seem to get processed.)

Just recently I've noticed a similar effect with the drop down menus, 
that those can stick sometimes.  This may be related to the same problem.

With the Qt method of signals and slots, debugging can be a little 
tricky in the sense that the underlying mechanisms are robust so the Qt 
code will act strangely rather than completely crash.

My guess is that something like a signal/slot associated with the 
workspace isn't being configured quite properly at launch of the GUI. 
Haven't had time to investigate.

Dan