QPropertyAnimation and QStackedLayout:functionality.

[savaliya_ambani]

Thanks Lykurg.

yes ,i have set the real index number of a particular button with its sub menu page also.

i can also directly connect the signalmapper's mapped(int) to with the setcurrentindex(int).
connect(signalmapper,SIGNAL(mapped(int)),Menustack , setCurrentIndex(int));
but ,this is also not working.

is it that i can link only QComboBox and QListWidget witht the QStackeLayout's setcurrentindex(int) ?

[Lykurg]

is it that i can link only QComboBox and QListWidget witht the QStackeLayout's setcurrentindex(int) ?

You can. Most like you have somewere a minor error which blocks the change. So please make sure the right indexes are delivered etc. Best you would do a simple, compileable and minimal example reproducing your problem. Then we could see your acctual code and maybe find the error. (because you pasted code is not consistent and would not work. Also please use the [code] tags next time)

[savaliya_ambani]

Dear Lykurg,

i have done by other way.

connect(signalmapper,SIGNAL(mapped(int)),widget, SLOT(MenuEvent(int)));

void widget::MenuEvent(int index)
{
if(index == menupage1)
{
MenuStack->setCurrentIndex(0);
}

if(index == menupage2)
{
MenuStack->setCurrentIndex(1);
}

if(index == menupage1)
{
MenuStack->setCurrentIndex(2);
}

if(index == menupage1)
{
MenuStack->setCurrentIndex(3);
}


}

But, still this is not showing any thing. Only the TOP Widge is what i can see.

[savaliya_ambani]

Dear All,

I have also run the another test code with same but minimized functionality,but still
it is having the problem,the same as shown above.

when it comes into :
void widget::MenuEvent(int index)
{
}

The instruction i am writing for setting the index ,MenuStack.setCurrentIndex(n) ;is not taking any effect.

what can be the related issue with this? Dear in my organisation it is very difficult to post the module code i am working. i can only explain the flow:

* create the main widget,on which there are forur buttons,each for one menu page
* create anohter four widget ,which will be my menu pages with no parent
*connect mapped(int) with the MenuEvent(int) slot.
*add all four menu page into QVBoxLayout object
* set object layout
*And finally Handle the event and do setCurrentIndex( int).

This is what i have done. I think what i have shown and discussed is enough.

[Lykurg]

when it comes into :
void widget::MenuEvent(int index)
{
}

Did it come so far? Have you check if the slot is actually called?

* create the main widget,on which there are forur buttons,each for one menu page
* create anohter four widget ,which will be my menu pages with no parent
*connect mapped(int) with the MenuEvent(int) slot.
*add all four menu page into QVBoxLayout object
* set object layout
*And finally Handle the event and do setCurrentIndex( int).

This is what i have done. I think what i have shown and discussed is enough.

No that is not enough, because of that decription it should work. And you should not post your project, you should strip it down, that only the problem is left.

How did you set the signal mapper of?

[savaliya_ambani]

yes, it comes here:
void widget::MenuEvent(int index)
{
}

The signal mapper is from the main widget. And when i take any menu page,i passed this *signalmapper into the class created for taking object of each menu page. And in that class it receives the refrence to the signalmapper and
mappes its own buttons with this signalmapper.

thats it.
only problem is that setCurrent Index has no effect.

[Lykurg]

only problem is that setCurrent Index has no effect.

Well last statement of mine: setCurrentIndex works well, so it is not a problem of Qt. Your syntax seems to be OK according to what you have said. But without real (not complete) code I can't help further, since my crystal ball is currently out of order, unfortunately.

[Lykurg]

But, still this is not showing any thing. Only the TOP Widge is what i can see.

As told, your code is meaningless and one can nothing see. So please provide a minimal compilable example, reproducing your problem.

Side note: use else or better a switch statement to fasten up your code.