Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved PB 2019 R2 application icon

  1. Issue
0
Votes
Undo
  1. Sanjay Shivade
    Sanjay Shivade
  2. PowerBuilder
  3. Friday, 4 September 2020 21:37 PM UTC

Hi,

All of our executables built using PB 2019 are missing application icons.  Could you let us know how to resolve this issue? I reviewed relevant Q&A but couldn't find satisfactory answer. 

 

I will really appreciate your help.

 

Thanks

Sanjay

httpclient.sendrequest fails when deployed but wor...
Find out column name in an expression.
Responses (4)
Michael Kramer
Michael Kramer Accepted Answer Pending Moderation
  1. Friday, 4 September 2020 23:17 PM UTC
  2. PowerBuilder
  3. # 1

Hi, I just checked and my PB 2019 R2 #2323 deploys app's icon as part of .EXE file. It displays in Windows Explorer as expected.

How I do it:

  1. Application Painter > Properties Pane > General > [Additional Properties] > Icon > Icon Name
  2. Strip off path so filename is as short as possible. (screen shot #1)
    Sometimes my graphics are in subfolder, like "resources/favicon.ico".
    Never C:\DEV\ . . .
  3. Deploy app using project painter
  4. Look at .EXE file in Windows Explorer => Image displayed
  5. Run app => Desktop taskbar displays app's icon (see screen shot #2)

Never had a problem with app icons nor images in general when my filenames strip off excess path.

HTH /Michael

Comment
Sanjay Shivade
  1. Sanjay Shivade
  2. Tuesday, 8 September 2020 22:38 PM UTC
This worked for me. The app icon started showing up after removing the path explicitly. I am not sure why we didn't have to do this in earlier versions. Thanks for your help.



Sanjay P.S.
  1. Helpful
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Saturday, 5 September 2020 13:29 PM UTC
  2. PowerBuilder
  3. # 2

what build number of 19R2 are you using?  there was a fix for this in a newer build of 19R2

Comment
Load more comments
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Saturday, 5 September 2020 13:55 PM UTC
Correct ... MR2328 had a fix for the missing App icon.
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Sunday, 6 September 2020 22:53 PM UTC
Well, I'm on 2353 and it's been happening to me too after migrations from 2017:(

Solution: go into the application object. Assign an empty string for the icon, apply save.

go back in again: assign the correct icon again with full path, "Apply" button, then I delete the path and only leave the icon name, as the icons are in the same folder as the application object's pbl (and in the pbr file).

Solved.

  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 7 September 2020 01:55 AM UTC
Yep, No path. I've been doing it that way since PB 1.0. ?
  1. Helpful
There are no comments made yet.
Sanjay Shivade
Sanjay Shivade Accepted Answer Pending Moderation
  1. Saturday, 5 September 2020 21:19 PM UTC
  2. PowerBuilder
  3. # 3

My build version is :

Appeon PowerBuilder Cloud Edition

Version 2019 Build 2170

Built on Dec 25 2019 at 13:04:09

 

Please let me know if there is a fix available for this. Thanks!

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Saturday, 5 September 2020 21:35 PM UTC
Hi Sanjay ... The icon issue started in PB 2019 R2 build 2323. Build #2170 should be OK. That was the last MR for the GA version of PB 2019 before R2 was released.
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Sunday, 6 September 2020 22:54 PM UTC
  2. PowerBuilder
  3. # 4

This has been happening to me too.

I'm on build 2353 and it's been happening to me too after migrations from 2017:(


Solution: go into the application object. Assign an empty string for the icon, apply and save.
Go back in again: assign the correct icon again with full path, "Apply" button, then I delete the path and only leave the icon name, as the icons are in the same folder as the application object's pbl (and in the pbr file). Apply and Save again.
Problem solved.

 

Comment
Michael Kramer
  1. Michael Kramer
  2. Tuesday, 8 September 2020 22:13 PM UTC
You deserve points for solving the issue through struggles and experimentation!

Accidentally I started with empty string. Assigned with full path. Then removed path. So accidentally I followed you recipe. DIdn't realise though so my solution was "trust luck" it seems.
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Tuesday, 8 September 2020 22:19 PM UTC
Haha!

Well it's just old way of doing it isn't it.

I did find it strange that it happened to all of my applications after migrating them from 2017 R3 to 2019 R2.

Just a one time thing I hope.

regards
  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.