Re: Windows GUI startup message truncated

[Daniel J Sebald]

On 11/29/2017 03:45 PM, John W. Eaton wrote:
> On 11/29/2017 04:24 PM, Daniel J Sebald wrote:
[snip]
> > Also, you could close the File Browser, Workspace and Command History 
> > windows, exit and relaunch to see if the missing section is part of 
> > the Command Window or the main window (i.e., does the width of the 
> > visible portion change with window size changes?).
>
> Ah.  If I have more than one tab open in the part of the GUI that 
> normally displays the command, editor, documentation, and variable 
> editor widgets when Octave starts, the message is truncated.  I'm not 
> sure that this is relevant, but it appears to be truncated to 
> approximately the width of the GUI tab thing that is used for switching 
> between the widgets.  If only the command window is visible when Octave 
> starts, then no "switcher tab" is displayed and the message is not 
> truncated.  I wonder if somehow the initial width of the widget is set 
> to the width of the tab and that is used when the interpreter is 
> starting and displaying the message.  Hmm.

Good observation.  That sounds plausible.  Perhaps the Octave-core 
thread and shell emulator need to be launched after the size of the 
window is resolved by the final GUI layout.  Maybe the emulator is 
drawing too early and all that Qt's Windows underlying framework can 
resolve is that the window must be at least the size of the tab (i.e., 
it knows the minimum width but still not the maximum width).

Dan