Is Stacked Widget the only option

pragati

yes the DMM.h is the one which contains dmmmenu definition.

Actually we have to use these screens everywhere frequently in different subdirs which are part of this project so...stackwidget will not create a problem?

ChrisW67

No. You can use as many instances of widgets as you like in as many places as you like. Some of those instances you can place in a QStackedWidget,

pragati

Will stacked widget create any problem in memory allocation or take more space ?

infoctopus

listen to people, QStackedWidget is your friend

pragati

@infoctopus.....:).......Yeah I want to....but some of my colleagues think that QStackedWidget will affect system's memory....So just to be assure and stay with QStackedWidget I need to be clear at this point of view....so guys help me out in deciding....please!!!!

pragati

My requirement is....I am going to have four different components in my project with lots of screens in it each and many will interact with each other....Its like a gui we have in our mobile...you can go back to main menu then switch to some other....the only difference is I am having different modes on which the device will work.....

So what you say what shall be the approach to achieve this kinda functionality

infoctopus

pragati, you either have your widgets (for "screens") in memory all the time (regardless of using QStackedWidget) OR you create/delete that widgets dynamically. I suggest to start with QStackedWidget and see if memory consumption is acceptable. If not, then create/delete objects when needed / not needed.

pragati

:)

I am already facing a problem in connecting widgets.....I am able to go next screen from main menu but from that screen I am not able to come back again to main menu. It is not allowing me to create an instance of the main menu's class in the screen from which I have to go back
:(

infoctopus

you can post a project illustrating the issue so people could help you in their little time

pragati

Yeah I will do .....thanx anyways!!!