Closed Wajinn closed 1 year ago
I guess the issue causes by gg. gg is clearing images when close. So image can not be reloaded.
Not yet sure of the cause. But, did notice that image.v file doesn't allow for specifying the path to the image again, unlike the other objects. Can not use: app.wm.uis["main_page"].get_object_by_id("image")[0]["path"].str = "picture.jpg" How GUIs with images are to be handled with MWM, might need to be clarified.
Images is an exception in MUI. It's not handled by path directly. The path will not be stored. The path will be opened by gg. And the pointer will store the image. When the window was closed, gg is releasing the images. So i need to self-cache images or find a way to force gg to store these caches.
Until fix the issue, you can reload the images yourself
Excellent, as usual. And the example nicely clarifies a way for this to be done.
Suggestion:
Maybe it would be good if the MWM example had a more complex GUI (containing an image) and was clear about intended usage for multiple GUIs. Would think a significant percentage would want or need multiple GUIs.
Issue:
It seems that MWM has problems with images, where if the original GUI contains an image, then it will disappear after switching back and forth between GUIs. The image disappears when the GUI is later shown. In the example below, an image was added. In the tests done, the image will show only the first time, then disappear when coming back to the main page GUI.
Not yet sure of the cause. But, did notice that image.v file doesn't allow for specifying the path to the image again, unlike the other objects. Can not use:
app.wm.uis["main_page"].get_object_by_id("image")[0]["path"].str = "picture.jpg"
How GUIs with images are to be handled with MWM, might need to be clarified.