Is there property inside Xojo to detect WinUI compile option ?
So if making Xojo class or component inside Xojo that it can draw differently or make different decisions based on if we got WinUI or not.
(I know this has been requested for plugins but this time I am asking for just pure Xojo code)
I just realized
if I compile the component as Library…….
Then TargetWinUI will not work I would think ? since libraries are per-compiled…..
And if so then I think the request still makes sense.
Sounds like we need libraries to have a Windows UI variant just like plugins?
like this in plugins:
+-Windows
+-Windows arm64 // New for 2022r2
+-Windows x86-64
+-WinUI x86 // New for 2023r2 (Note: DLL name must match the same under Windows)
+-WinUI x86-64 // New for 2023r2 (Note: DLL name must match the same under Windows x86-64)
+-WinUI arm64 // New for 2023r2 (Note: DLL name must match the same under Windows arm64)
1 Like
Am not sure I would want 2 more targets in the Libraries, its already almost not workable to compile and manage them.
Would be much better to just be able to ask the runtime which it is.
You could make a plugin function in your own plugins to query the status.
Thats not nice though then the Library is dependent on a plugin.
2nd library matter, can Libraries know if we are running from IDE or in compiled App ?
(which of course is a must if Libraries are to be viable to be able to make Demo vs full version for example)
I think Björn would need a App.WinUI as boolean property to read the status when compiled.
And maybe an App.DebugBuild property for whether it’s in debugger.
Waiting is no problem I am just putting some test on viability of Libraries, to find showstoppers at this point before I put them to real use.
1 Like