On 07/02/2018 03:23 PM, Enrico Forestieri wrote:
> On Mon, Jul 02, 2018 at 12:36:38PM -0400, Richard Kimberly Heck wrote:
>> On 07/02/2018 06:14 AM, Daniel wrote:
>>> On 26/06/2018 04:41, Richard Kimberly Heck wrote:
>>>> On 06/25/2018 06:43 PM, Scott Kostyshak wrote:
>>>>> One thing I observed is that,
>>>>>      I think an older version version of Windows GUI class is being
>>>>> used in
>>>>>      2.3.0. I marked the difference between the GUI of 2.3.0 and
>>>>> 2.3.0 RC2
>>>>>      fyi. Top one is 2.3.0 RC, bottom one is 2.3.0
>>>> The version of Qt I'm compiling against is probably different from that
>>>> used for RC2. I'm not sure whether it's "older" or just different. This
>>>> may just be a matter of what 'theme' is being used in different cases,
>>>> and so something that is user-configurable.
>>> I just installed LyX on Win 10. I have the same problem with the GUI
>>> looking outdated. It doesn't take up the default Win10 look. With
>>> Uwe's old unofficial installer for 2.3 it looks fine. I have never
>>> used any theme or so.
>> Possibly, this is due to a difference in Qt versions. But I don't know
>> what Uwe's was built with.
> This is unlikely. Most probably the qwindowsvistastyle.dll is not being
> found. This can be due to either a deployment problem or to the fact that
> it is actually missing. This dynamic library is responsible for the
> "modern" look.
>
> However, note that styles can be changed from the command line through
> "lyx -style nameofstyle", where nameofstyle on windows can be "windows"
> (probably what is being used), "windowsvista" (requires a dll), and
> "fusion" (common to all platforms), which maybe has a better look than
> "windows". So, I would try whether "lyx -style fusion" looks better
> (I am assuming that "lyx -style windowsvista" would fail, because it
> would be otherwise chosen by default).

Thanks for the info. That file was not included in the package I was
building, so I'll rebuild with it, and we'll see how that goes.

Riki

Reply via email to