1. Forum
  2. Usenet
  3. COMP.LANG.CLIPPER.VISUAL-

  • Using/enabling Windows 10 styles in VO application

    From Stefan Ungemach@21:1/5 to All on Fri Mar 4 03:02:28 2022
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Stavros Spanos@21:1/5 to All on Fri Mar 4 07:17:15 2022
    Hello Stefan.

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


    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Wolfgang Riedmann@21:1/5 to Stefan Ungemach on Wed Mar 9 08:07:15 2022
    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>
    <!-- Windows 10 -->
    <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>
    <!-- Windows 8.1 -->
    <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>
    <!-- Windows Vista -->
    <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>
    <!-- Windows 7 -->
    <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
    <!-- Windows 8 -->
    <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



    --

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Stefan Ungemach@21:1/5 to Wolfgang Riedmann on Wed Mar 9 04:51:47 2022
    Wolfgang Riedmann schrieb am Mittwoch, 9. März 2022 um 08:07:21 UTC+1:
    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>
    <!-- Windows 10 -->
    <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>
    <!-- Windows 8.1 -->
    <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>
    <!-- Windows Vista -->
    <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>
    <!-- Windows 7 -->
    <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
    <!-- Windows 8 -->
    <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
    --
    Hi Wolfgang,

    that sounds great. Could you please point me in the right direction about how to use that manifest?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Stefan Ungemach@21:1/5 to Wolfgang Riedmann on Wed Mar 9 05:24:08 2022
    Wolfgang Riedmann schrieb am Mittwoch, 9. März 2022 um 08:07:21 UTC+1:
    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>
    <!-- Windows 10 -->
    <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>
    <!-- Windows 8.1 -->
    <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>
    <!-- Windows Vista -->
    <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>
    <!-- Windows 7 -->
    <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
    <!-- Windows 8 -->
    <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
    --

    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>
    <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
    <application>
    <!-- Windows 10 -->
    <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>
    <!-- Windows 8.1 -->
    <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>
    <!-- Windows Vista -->
    <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>
    <!-- Windows 7 -->
    <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
    <!-- Windows 8 -->
    <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>

    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)?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Wolfgang Riedmann@21:1/5 to All on Fri Mar 11 08:20:35 2022
    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


    --

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Stefan Ungemach@21:1/5 to Wolfgang Riedmann on Wed May 11 07:34:17 2022
    Wolfgang Riedmann schrieb am Freitag, 11. März 2022 um 08:20:38 UTC+1:
    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


    --

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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)