Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #13565 > unrolled thread

Using/enabling Windows 10 styles in VO application

Started byStefan Ungemach <stefan.ungemach@bingo-ev.de>
First post2022-03-04 03:02 -0800
Last post2022-05-11 07:34 -0700
Articles 7 — 3 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  Using/enabling Windows 10 styles in VO application Stefan Ungemach <stefan.ungemach@bingo-ev.de> - 2022-03-04 03:02 -0800
    Re: Using/enabling Windows 10 styles in VO application Stavros Spanos <stavros.spanos2@gmail.com> - 2022-03-04 07:17 -0800
    Re: Using/enabling Windows 10 styles in VO application "Wolfgang Riedmann" <wriedmann@gmail.com> - 2022-03-09 08:07 +0100
      Re: Using/enabling Windows 10 styles in VO application Stefan Ungemach <stefan.ungemach@bingo-ev.de> - 2022-03-09 04:51 -0800
      Re: Using/enabling Windows 10 styles in VO application Stefan Ungemach <stefan.ungemach@bingo-ev.de> - 2022-03-09 05:24 -0800
        Re: Using/enabling Windows 10 styles in VO application "Wolfgang Riedmann" <wriedmann@gmail.com> - 2022-03-11 08:20 +0100
          Re: Using/enabling Windows 10 styles in VO application Stefan Ungemach <stefan.ungemach@bingo-ev.de> - 2022-05-11 07:34 -0700

#13565 — Using/enabling Windows 10 styles in VO application

FromStefan Ungemach <stefan.ungemach@bingo-ev.de>
Date2022-03-04 03:02 -0800
SubjectUsing/enabling Windows 10 styles in VO application
Message-ID<0885e9e3-db18-40e8-b130-fe21c6e1e4b2n@googlegroups.com>
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

[toc] | [next] | [standalone]


#13566

FromStavros Spanos <stavros.spanos2@gmail.com>
Date2022-03-04 07:17 -0800
Message-ID<89e14c1c-f789-408e-9e93-eb7f75d8cb81n@googlegroups.com>
In reply to#13565
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

[toc] | [prev] | [next] | [standalone]


#13575

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2022-03-09 08:07 +0100
Message-ID<j8r216Fh130U1@mid.individual.net>
In reply to#13565
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



-- 

[toc] | [prev] | [next] | [standalone]


#13576

FromStefan Ungemach <stefan.ungemach@bingo-ev.de>
Date2022-03-09 04:51 -0800
Message-ID<a0427cf6-aed9-49d0-959c-2266ad0b90f4n@googlegroups.com>
In reply to#13575
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?

[toc] | [prev] | [next] | [standalone]


#13577

FromStefan Ungemach <stefan.ungemach@bingo-ev.de>
Date2022-03-09 05:24 -0800
Message-ID<c8d1147f-74f5-4023-a260-65107864b5cen@googlegroups.com>
In reply to#13575
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)?

[toc] | [prev] | [next] | [standalone]


#13578

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2022-03-11 08:20 +0100
Message-ID<j90bi3FhjsuU1@mid.individual.net>
In reply to#13577
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


-- 

[toc] | [prev] | [next] | [standalone]


#13590

FromStefan Ungemach <stefan.ungemach@bingo-ev.de>
Date2022-05-11 07:34 -0700
Message-ID<dfbd590b-4af6-4ca5-9354-07d536188b0en@googlegroups.com>
In reply to#13578
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...

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web