Support for Different Icon Settings for each OS

[fsw]

I have some PB programs that I have to compile a Windows version for it as well (besides macOS) and it seems to me that it's weird that the app icon uses the same icon entry in the PB file across all operating systems.

This is very unfortunate, as the icon file format differs:
macOS -> icns
Windows -> ico

and probably:
Linux -> png

Because all OS use the same icon entry in the PB file, I have to manually select a different icon file every time I recompile an app on another OS.

[mk-soft]

I create different main files. MainWindow, MainMacOS, MainLinux
In these different ones, the main file is included with IncludeFile, so you can configure different OS.

[Mindphazer]

That's very clever !
Thanks for the tip

[HeX0R]

I'm using different projects which are loading the same source files, but with different compiler settings.

[fsw]

HeXor, mk-soft obviously you are way smarter than me

These are very good suggestions/working methods... but hear me out please:

In my humble opinion these are work arounds for the PB-IDE lack of handling it itself.

We have CompilerIf/ElseIf/End and other Compiler commands, to handle different operating systems.
This way we can use ONE source file for all operating systems.
Not handling things like app icons for different operating systems is clearly an oversight that could be fixed.

Actually, thinking of it:
If I have to use different main source files for the handling of app icons (and maybe other things) why have CompilerIf/ElseIf/End and other Compiler commands available?
I could just add different operating system code in these separate files as well.

HeXor, mk-soft, please don't get me wrong... I like your guys suggestions and it will surely help me short term to ease my work, but in my humble opinion, this could be made much easier.

Thanks for reading

[HeX0R]

I can hear you loud and clear, no worries .
The question is, how do you want that to be integrated?
I mean when you compile on different OS it is not just the icon which is different, it's also the binary extension, the library extension, the subsystems, the compiler used,...

Therefore I think using projects should be the way to go, but probably not like I am doing it.
I'm only doing it like this, because I can't simply put linux, maxOS and windows targets in one project, because windows, doesn't know the linux compilers, and as soon as I jump into the linux target settings, PB tells me, it doesn't know that compiler and switches it back to the windows compiler.

If that could be improved (e.g. simply hide all targets that doesn't fit the current O.S.), it should be perfect.

At least for me

[fsw]

I'm only doing it like this, because I can't simply put linux, maxOS and windows targets in one project, because windows, doesn't know the linux compilers, and as soon as I jump into the linux target settings, PB tells me, it doesn't know that compiler and switches it back to the windows compiler.

Yes.
That's why I hoped Fred would emit Go and not C.
With Go I just have to set 2 variables on the command line when I call the compiler and I can compile for another OS or another hardware architecture.
I guess I'm spoiled

If that could be improved (e.g. simply hide all targets that doesn't fit the current O.S.), it should be perfect.

At least for me

I concur.