Even though set in the Application Painter, the application icon and font defaults are stored in a binary object in the PBL separate from the application object binary.

If you could look inside the PBL you would see:

appname.sra - The application object source code

appname.apl - The application object compiled code

appname.pra - The additional settings binary object

I am pretty sure I submitted a feature request to move the icon name to the application object source code. It would make rebuilding the target from source and building the exe much easier.

Thank you Chris and Bruce!

Unfortunately, we all know that the icon property is not a real application object property but something called an "additional property". Setting it leaves no trace in an application object source code. Apparently, this information is recorded somewhere in a local PBL file. We store our source code in SVN using PBSCC proxy, so this information never finds its way to SVN. We are creating PBLs from the source code files pulled from SVN (either in PB with PBSCC proxy or via PowerGen for PB10/12 or via OrcaScript for PB2017) and the information about the icon file is simply not present in these PBLs. Building an exe file from such dynamically created PBLs with an icon file is possible with OrcaScript but it is rather awkward because of the pdbflags parameter. PBC does not need it, but there is no way to specify an application icon...  Quite a dilemma! Am I getting this right that this is not going to change any time soon? Is there maybe a way of recording the information about the icon file into a PBL file the way PB IDE does?

Best regards,
Konstantin

The pbc just automates the options in the PowerBuilder project object.  There's no option there for the app icon.  Instead, that's on the application object.

Hi Konstantin;

   The PB App's icon for the EXE is controlled via the "Application" object and its icon property mapping.

Regards ... Chris