1. Vijay Jha
  2. PowerBuilder
  3. Thursday, 6 October 2022 05:52 AM UTC

Hello Team,

I have already migrated PowerBuilder 2017 to PowerBuilder 2022 and everything went into success. What I see is , There is ' NO Icon ' while launching application through EXE whereas, There is an 'ICON' while launching application through IDE.

I have already kept my image folder in the same directory where application resides.

 

Thank You

Vijay Jha

Vijay Jha Accepted Answer Pending Moderation
  1. Friday, 14 October 2022 09:18 AM UTC
  2. PowerBuilder
  3. # 1

Hi All,

 

This issue is resolved now. We had assumption that compiled exe will load the image file during runtime if, we will be adding app icon into the same folder where application's workspace resides and it was an obvious assumption as we don’t use any PBR files in our application.  The images/icons/etc. all come from c:\xx\xxx ( the different folder than the folder where workspace resides)  at run time.  The workstation’s library PATH system variable at the windows level is updated when we install our application on a workstation to include the c:\xx\xxx so windows can find the image/icon file.  That’s why we don’t specify the full path for images within our application– we just put the image file name and count on windows to find it in c:\xx\xxx (or any alternative folder if the workstation was setup to not use c:\xx\xxx but instead go to a any drive instead).

But, what we did is we have added the application icon into the folder where app workspace resides and then rebuild the exe without making any change into app icon segment. We rebuild the exe and everything went into success. We have then deleted that ICON from the folder where app workspace resides and icon is still appearing as it is, while launching through both IDE & EXE so, the image is actually embedded into the compiled exe and no more required after exe gets rebuild.

I would like to thank everyone who helped me with their expertise.

Thank You

Vijay Jha

 

Comment
There are no comments made yet.
kitty he @Appeon Accepted Answer Pending Moderation
  1. Sunday, 9 October 2022 11:23 AM UTC
  2. PowerBuilder
  3. # 2

Hi Vijay,

 

Sorry that we can't reproduce the issue. If you can reproduce the issue, please report a bug via our support ticketing system at https://www.appeon.com/standardsupport/newbug and attach a simple reproducible test case for us to analyze the issue.

 

Regards,

Kitty

Comment
There are no comments made yet.
Vijay Jha Accepted Answer Pending Moderation
  1. Friday, 7 October 2022 10:26 AM UTC
  2. PowerBuilder
  3. # 3

@Andreas - No luck cry as I tried with 32*32 as well.

Comment
There are no comments made yet.
Andreas Mykonios Accepted Answer Pending Moderation
  1. Friday, 7 October 2022 09:19 AM UTC
  2. PowerBuilder
  3. # 4

Also, icon format support to have multiple "versions" of the same image with different sizes.

If you create such an icon, powerbuilder will choose the best icon to use depending on the object it should be placed on.

Andreas.

Comment
There are no comments made yet.
Andreas Mykonios Accepted Answer Pending Moderation
  1. Friday, 7 October 2022 09:12 AM UTC
  2. PowerBuilder
  3. # 5

Don't need the logo.

Can you make it 32x32 and test it? In the past we had some issues with icons of size 24x24 and 48x48. In our case menus were affected, but worth to try.

Andreas.

Comment
There are no comments made yet.
Vijay Jha Accepted Answer Pending Moderation
  1. Friday, 7 October 2022 08:55 AM UTC
  2. PowerBuilder
  3. # 6

@Andreas,

 

Hi, Please find details below,

 

Our logo is of Blue color , sorry cant share logo due to policy issues.

 

Thanks

Vijay Jha

Comment
There are no comments made yet.
Andreas Mykonios Accepted Answer Pending Moderation
  1. Friday, 7 October 2022 08:09 AM UTC
  2. PowerBuilder
  3. # 7

Can you give some details about the icon (dimensions, color depth etc)? I wonder if there is an incompatibility due to some sort of bug...

Andreas.

Comment
There are no comments made yet.
Vijay Jha Accepted Answer Pending Moderation
  1. Friday, 7 October 2022 07:12 AM UTC
  2. PowerBuilder
  3. # 8

Hi Andreas,

 

This is 'AppIcon!' only.

 

Thanks

Vijay Jha

Comment
There are no comments made yet.
Andreas Mykonios Accepted Answer Pending Moderation
  1. Friday, 7 October 2022 06:37 AM UTC
  2. PowerBuilder
  3. # 9

Well, can you check the value in the icon property of your windows? Is it "AppIcon!"? Normally this should be unchanged during migration. But take a look to be sure it has the correct value.

Andreas.

Comment
There are no comments made yet.
Vijay Jha Accepted Answer Pending Moderation
  1. Friday, 7 October 2022 06:22 AM UTC
  2. PowerBuilder
  3. # 10

Hi All,

 

I have already followed the instructions given by Andreas Mykonios, Chris Pollach & Roland Smith but unfortunately it is not working.

My Issue -

I have created EXE from IDE after migrating PB 2017 to PB 2022 Build 1878. There is an ICON in the EXE at the desktop but while launching the application the same ICON should display in the top left corner of our application and therefore in all the subsequent windows like the previous EXE which was built with PB 2017 but, unfortunately the ICON is not displaying.

 

@Chris @ Roland - I have kept the IMAGE folder in the same directory where workspace resides and in the properties of EXE I have already trimmed the path for the ICON and only kept the ICON name like IC000.ICO 

@Andreas - I have already set the 'Current Workspace' for SET ROOT and rebuild the EXE but, no luck.

 

Thanks

Vijay Jha

 

Comment
  1. Roland Smith
  2. Friday, 7 October 2022 12:40 PM UTC
Make sure that the Control Menu property of the main window is checked.
  1. Helpful
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 6 October 2022 12:44 PM UTC
  2. PowerBuilder
  3. # 11

When setting the icon in the application object, make sure you have only the file name, not the full path.

Use this:  myapp.ico

Not this:  C:\PBSource\MyApp\myapp.ico

 

Comment
  1. Chris Pollach @Appeon
  2. Thursday, 6 October 2022 18:43 PM UTC
Adding ti Roland's response .. since the .ICO file for the EXE has no path (which it should "never" have" .. the .ICO file *must* reside in the SAME folder as the WorkSpace file & NOT any sub-folder thereof. HTH
  1. Helpful 1
There are no comments made yet.
Andreas Mykonios Accepted Answer Pending Moderation
  1. Thursday, 6 October 2022 11:26 AM UTC
  2. PowerBuilder
  3. # 12

Hi.

You are building your application using IDE or pbc220 or pbautobuild220?

The icon is set using relative path, full path or only icon filename?

If you are using IDE try the following before build: right click in the white space in the system tree. A menu will show:

Choose "Set Root...". A response window will show.

Choose "Current Workspace" and OK.

Try again to build you executable.

Andreas.

Comment
There are no comments made yet.
Sivaprakash BKR Accepted Answer Pending Moderation
  1. Thursday, 6 October 2022 06:44 AM UTC
  2. PowerBuilder
  3. # 13

Hello Vijay

1.  Was there ICON in PB 2017 app when run from exe ?
2.  Have you included that ICON in PBR file and added it while compiling ?   Not sure whether it's required or not.

Happiness Always
BKR Sivaprakash

 

Comment
  1. Vijay Jha
  2. Thursday, 6 October 2022 10:59 AM UTC
Hi Sivaprakash,



Please find the response below -

1. Was there ICON in PB 2017 app when run from exe ? -> Yes.

2. Have you included that ICON in PBR file and added it while compiling ? Not sure whether it's required or not. -> I think its not required as we don’t use any PBR files in our application. The images/icons/etc. all come from our designated folder at run time. The concept is same for all other previous version of PB ( Earlier, we had migrated PB 12.5 to PB 17 in the same fashion)
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.