Using/enabling Windows 10 styles in VO application

Stefan Ungemach

unread,

Mar 4, 2022, 6:02:29 AM3/4/22

to

Hi there,

is there any way to move past the classic windows styles to make VO applications look more modern?

Please spare me comments about using VO in 2022 - we _are_ on a migration path, there _are_ needs to maintain some existing VO applications and I'm not in for philosophical lectures from Geoff :)

TIA
Stefan

Stavros Spanos

unread,

Mar 4, 2022, 10:17:16 AM3/4/22

to

Hello Stefan.

We use Code Jock OCX and we are ok with it. It uses Windows 10 styles.

Wolfgang Riedmann

unread,

Mar 9, 2022, 2:07:21 AM3/9/22

to

Hi Stefan,

you have to enable the new common controls using a manifest like that:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
manifestVersion="1.0">
<assemblyIdentity
version="1.0.0.0"
processorArchitecture="X86"
name="VO.Application"
type="win32"
/>
<description>Visual Objects Application.</description>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel
level="asInvoker"
uiAccess="false"
/>
</requestedPrivileges>
</security>
</trustInfo>
<compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
<application>

<supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>

<supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>

<supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>

<supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>

<supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>
</application>
</compatibility>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
</dependentAssembly>
</dependency>
</assembly>

HTH

Wolfgang

Stefan Ungemach wrote:

> Hi there,
>
> is there any way to move past the classic windows styles to make VO
> applications look more modern?
>

> Please spare me comments about using VO in 2022 - we are on a
> migration path, there are needs to maintain some existing VO

> applications and I'm not in for philosophical lectures from Geoff :)
>
> TIA
> Stefan

--

Message has been deleted

Stefan Ungemach

unread,

Mar 9, 2022, 8:24:10 AM3/9/22

to

Hi Wolfgang,

thank you - but we are doing that already. Here's our manifest file:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
manifestVersion="1.0">
<assemblyIdentity version="1.0.0.0"
processorArchitecture="X86"

name="KOB.adKOMM.Kommunalsoftware"
type="win32"
/>
<description>adKOMM Kommunalsoftware</description>

Unfortunately, every datawindow still appears in XP style. What am I doing wrong (I want to make datawindows look like the new "borderless" windows in newer applications)?

Wolfgang Riedmann

unread,

Mar 11, 2022, 2:20:38 AM3/11/22

to

Hi Stefan,

> Unfortunately, every datawindow still appears in XP style. What am I
> doing wrong (I want to make datawindows look like the new
> "borderless" windows in newer applications)?

that is a bug in the Windows API - and Sven Ebert pointed me to a
message that Microsoft has acknowledged it already.
It has nothing to do with VO as it is occurring in every MDI
application, even in Windows Forms:

https://github.com/dotnet/winforms/issues/3691#issuecomment-732538552

I was very surprised that Microsoft had not fixed that for Windows
11....

Wolfgang

--

Stefan Ungemach

unread,

May 11, 2022, 10:34:19 AM5/11/22

to

Thank you all. Now we have abandoned the MDI concept completely and the windows are nicer...