Recent

Author Topic: Manifest resource weird behavior  (Read 612 times)

nimble2010

  • New Member
  • *
  • Posts: 14
Manifest resource weird behavior
« on: June 28, 2024, 03:13:11 am »
Hi guys, I've spent some time trying to figure out why I can't run an OpenGL / SDL implementation and it turns out to be due to the usage of the manifest resource in the project's configuration. My doubts were confirmed after disabling it and finding this old thread:

Ah, it seems this is a bug related to enabling the Windows XP manifest for the project. This is bug report 0013235.

Does anyone have an idea when this might be fixed? I would do so myself, except I haven't a clue where to start!

Regards

Albert

Thanks Alberto for those links, they are a good resource.

Disabling the XP manifest resource seems to fix the problem and run my OpenGL program fine but with that I cannot have transparency on most controls (I still use forms). The transparency property in design-time becomes completely useless and using ControlStyle does not work either.

How can I address that? Tracking the XP manifest option in source code didn't get me anywhere.

Thank you

Thaddy

  • Hero Member
  • *****
  • Posts: 15505
  • Censorship about opinions does not belong here.
Re: Manifest resource weird behavior
« Reply #1 on: June 28, 2024, 06:58:32 am »
On Windows, the manifest is indeed necessary for opacity to work. That's how the Windows API works. Actually how GDI+ is invoked as the default drawing API.
But a manifest resource can contain many more information, e.g. access rights.
So the manifest resource needs to be debugged.
I have not enough knowledge of SDL, if at all, I use OpenGL always directly or use Windows API's, but can you point me to the offending manifest?
I might be able to see where it goes wrong.
That is, unless SDL transparency clashes with the Windows transparency: that is almost unfixable.
The OpenGL API does not use high level native Windows drawing API's.(GDI and GDI+) It uses the graphics driver directly.
In the worst case, with OpenGL you would probably need a complete OpenGL drawn widget set, comparable to the custom drawn widget set to support consistent opacity for all controls.
That is, I see no technical reason why the Windows drawing API's would clash with OpenGL.
In effect all use the same low-level graphics drivers.
« Last Edit: June 28, 2024, 09:01:25 am by Thaddy »
My great hero has found the key to the highway. Rest in peace John Mayall.
Playing: "Broken Wings" in your honour. As well as taking out some mouth organs.

Thaddy

  • Hero Member
  • *****
  • Posts: 15505
  • Censorship about opinions does not belong here.
Re: Manifest resource weird behavior
« Reply #2 on: June 28, 2024, 08:31:47 am »
I mixed up Opacity with Transparency and they are not quite the same therefor I removed my previous post. That said, that applied patch from 2009 looks OK, but the opacity, and that needs to be fixed in the same spot.
« Last Edit: June 28, 2024, 09:00:09 am by Thaddy »
My great hero has found the key to the highway. Rest in peace John Mayall.
Playing: "Broken Wings" in your honour. As well as taking out some mouth organs.

 

TinyPortal © 2005-2018