Re: Windows GUI startup message truncated

[PhilipNienhuis]

Torsten-3 wrote
> On 01.12.2017 23:03, Rik wrote:
>> On 12/01/2017 09:00 AM, 

> octave-maintainers-request@

>  wrote:
>>> Subject:
>>> Re: Windows GUI startup message truncated
>>> From:
>>> PhilipNienhuis <

> pr.nienhuis@

> >
>>> Date:
>>> 11/30/2017 10:06 AM
>>>
>>> To:
>>> 

> octave-maintainers@

>>>
>>> List-Post:
>>> <mailto:

> octave-maintainers@

> >
>>> Content-Transfer-Encoding:
>>> 7bit
>>> Precedence:
>>> list
>>> MIME-Version:
>>> 1.0
>>> References:
>>> <

> b56cf93a-b59f-2026-a309-62e8d5b7fa6a@

> >
>>> In-Reply-To:
>>> <

> b56cf93a-b59f-2026-a309-62e8d5b7fa6a@

> >
>>> Message-ID:
>>> <

> address@hidden

>>
>>> Content-Type:
>>> text/plain; charset=us-ascii
>>> Message:
>>> 2
>>>
>>>
>>> John W. Eaton wrote
>>>> See attached image.
>>>>
>>>> I installed one of the buildbot builds (w64 with 32-bit indexing) and 
>>>> this is what I see when Octave starts.  The startup message is
>>>> truncated 
>>>> to 14 columns.
>>>>
>>>> Thinking there could be some init file issue, I tried removing the 
>>>> ~/.config directory with the same results.
>>>>
>>>> Text entered at the command prompt and output from commands are not 
>>>> truncated, just the startup message.
>>>>
>>>> Does anyone have an idea about what could cause this?  I've never seen 
>>>> this problem before.
>>>>  
>>> I first thought (as usual) that it was caused by something in my own
>>> dev-octave or mxe-octave build tree (both are somewhat adapted locally),
>>> but
>>> good to know that it is "officially confirmed".
>>>
>>> Whatever the cause, it happened between 16 (still good) and 19 November
>>> (truncated), because I have mxe-octave builds of those dates installed
>>> here
>>> to check. My cross-builds are always based on the latest default branch.
>>> tips
>>>
>>> Philip
>> 
>> That's a very handy bracketing.  Looking through the Mercurial log, this
>> cset seems to be the only one directed at windows.
>> 
>> changeset:   24275:e9fe31118542
>> user:        Torsten &lt;

> mttl@

> &gt;
>> date:        Sat Nov 18 11:50:16 2017 +0100
>> summary:     improve re-docking of a floating widget under windows
>> 
>> --Rik
> 
> I will have a look at this. The strange thing is that starting with
> 
> changeset:   24318:a17862b28f0d
> user:        Torsten &lt;

> mttl@

> &gt;
> date:        Mon Nov 27 20:38:35 2017 +0100
> summary:     handle floating widgets on all platforms as done on windows
> (bug #52378)
> 
> the new re-docking approach is used on all platforms. Are there any
> observations of this effect on non-windows platforms so far?

Remarkably, when increasing the terminal font size from 11 to 15 (and
restarting Octave), the entire width of the terminal window is used again
(and the text is truncated to the right terminal window margin).

Resetting font size to 13, the text seems truncated to the limits of the 15
pt. font in the previous step, but much wider then in JWE's picture.

Finally, resetting font size to 11 gives back the 14 char width truncation
reported by JWE and seen by me.

In the end, with 12 pt character size (Courier New) it looks reasonably good
again (no truncation AFAICS).

I tried with some other fonts but that doesn't seem to make a difference.

Hmmm, looks like a typical case of "go figure"

Philip




--
Sent from: http://octave.1599824.n4.nabble.com/Octave-Maintainers-f1638794.html