QFrame objects, added after the whole application has started, that look as if they are disabled
-
Hi.
After the application is fully started, a block (a QFrame object) is removed and then reinserted.
There is configuration mask which allows to remove and add the various blocks.
The code that adds the block is the same as it does when the application starts.
Once the block is added, the information drawn above is not displayed and it is not possible to move the block.
The block is the one to the right of each screen below.
The one removed and reinserted is the one of the first screen without the 2200 in red).
The second screen shows the fully functional block after starting the application.Does anyone have any idea what could be causing this problem?
-
Hi.
After the application is fully started, a block (a QFrame object) is removed and then reinserted.
There is configuration mask which allows to remove and add the various blocks.
The code that adds the block is the same as it does when the application starts.
Once the block is added, the information drawn above is not displayed and it is not possible to move the block.
The block is the one to the right of each screen below.
The one removed and reinserted is the one of the first screen without the 2200 in red).
The second screen shows the fully functional block after starting the application.Does anyone have any idea what could be causing this problem?
@giusdbg Found.
I have a number of object derivations from the QFrame object, to prevent connects on child objects from failing, I have to use the setParent( parent ) function.
Apparently I was using it in a gray and unexpected area in the construction of qt objects and events.
By moving the setParent to the end of each final derived object and also placing the call to show(), it works much better.
(waiting to be able to fix the connect and use the qt in a more orthodox way). -
G giusdbg has marked this topic as solved on