Add an empty library to your target called images.pbl. Then in the build process assign a .pbr file to the images library. The .pbr would have a list of all image files in the application.

Make sure that all image references in your code are only the filename (no path info). Then put all the image files in one folder and add the folder to your system path.

When the target is deployed, all the images will be in images.pbd and the app will be able to load images without having to worry about current folders. You also won't have to deploy the image files to the client.

Hi Michael;

  There have really been no changes to picture handling in Appeon PB 2021 / 2022 Rx releases other than a few improvements to render images a bit better but, that should be all transparent to your App code.

   Ronnie brings up a few good points to check. I have seen these type of things derail images but by no means a fault of the PB App EXE. Another possibility is that you are running out of a) App memory (ie 32 bit address space); c) running out of MS-Windows resource handles; or maybe c) Images have been improperly linked into a PBD / DLL.

   FYI: IN all of PB 2022 R1, R2 & now R3 - no other tickets were created referencing this type of problem.

Regards ... Chris

drag the window mostly off screen & uo_3.setRedraw(TRUE) - doesn't help.

The buttons work. The problems are with the pictures only.

Do the button actions cause the current directory to be changed (which can break references to the image files)?

If not, there may be a refresh issue with PB22.

If you drag the window mostly off screen and then back, do the images reappear?

Do the images reappear if you script the following (for example)?

uo_3.setRedraw(TRUE)

Hi, For this particular issue I would suggest open a support ticket and provide a little test case that reproduces the problem.  https://www.appeon.com/standardsupport/newbug