[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #44282] 'gui_mainfcn' undefined
From: |
Markus Mützel |
Subject: |
[Octave-bug-tracker] [bug #44282] 'gui_mainfcn' undefined |
Date: |
Mon, 18 Nov 2019 07:03:39 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0 |
Follow-up Comment #7, bug #44282 (project octave):
You are right. But there is also this comment in TestGUI_OpeningFcn in the
file from bug #57212:
% UIWAIT makes TestGUI wait for user response (see UIRESUME)
% uiwait(handles.figure1);
To be honest, I don't know what to make out of these contradicting comments.
If that function (with "uiwait") is executed before the figure is set to
visible, it would remain invisible until it is closed (or uiresume is called),
wouldn't it?
Also in that case, the handles might become invalid which we should probably
check for, too.
It might also be that I misunderstand the sequence in which the functions are
executed in that case...
Imho, it's ok to leave the documentation as short as it is right now.
We usually include a copyright holder for all files. Do you want to add your
name?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?44282>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/