Hi,
I am having issues with the release 3.3.2.2:
Images are not displayed at runtime and MyDesktop’s Paint event never fires. When I debug the source code, the images exist, they are valid. It just doesn’t display.
The release 3.3.2.1 did not have these issues.
Any help?
Hi Sergio,
You’re correct, setting the Session Timeout by calling Application.SetSessionTimeout() would invalidate your session, so the paint won’t work.
Also, I want to quickly mention, that it is far better to set the ImageSource property, or the Image for that matter to the image you want to display you want as opposed to using the Paint event, because it’s resource heavy.
HTH,
Alaa
Dear Frank,
I’ve been away from development activities, and I’ve just returned.
I found out what causes this problem. Right at startup of the application, I had used the command:
Application.SetSessionTimeout(600)
This command stops calls to Paint events as well as not loading images from 3.3.2.2 (including the last update 3.3.2.3).
Thus, I added the parameter below inside the Default.json instead of the command above during the application startup.
“sessionTimeout”: 600
The problem was solved. Obviously the questions are: Why? What happens with Application.SetSessionTimeout?
Best wishes,
Sérgio
Hi Sergio,
how are these images being set up? As Embedded Resources?
Any chance to share a test case for us?
Best regards
Frank
Please login first to submit.
