12-30-2012 12:59 PM
Yes, but when the sheet is closed it will not be destroyed. Can you please suggest how to destroy it in QML?
recently learned this ;-)
from QML did it
01-03-2013 06:44 PM
Thank goodness I found this thread.
I thought I was going insane wondering why my application would act on weird after closing the sheet that I opened from the Applicaiton menu......
01-09-2013 03:32 AM
I don't think calling .destroy() in QML is valid for a sheet.
It compiles and runs and all, but I don't think it actually does anything. I ran my app through a profiler, and the memory keeps on piling up with the sheets....
We better not be punished for this since this is an OS bug, as we are creating a workaround to make sheets work with the Application Menu....
01-09-2013 07:32 PM
01-23-2013 08:23 PM
Just want to chime in to say that I appear to have fallen victim to this bug, but from a different approach.
In my app, I have a Sheet that instantiate in QML via createObject(). I have a signal that gets sent up to my Python code to validate the input on the Sheet, which fires a signal back to the sheet telling it what inputs are valid or not. The sheet then pops up a SystemToast alerting the user to the problem.
After closing and reopening the sheet, the signal gets sent once but results in 2 SystemToasts. If I close it and reopen again, I get 3 of them.
Modifying my code to destroy the object causes my code to crash when I call sheet.close(). I could rearchitect to work around this, but my code to insert data also depends on this. It would result in multiple rows being added. Furthermore, I'd really like to keep this architecture as it results in more modular code.
01-23-2013 08:28 PM