Posts: 12,706
Joined: Nov 2003
Reputation:
129
spiff
Team-Kodi Member
Posts: 12,706
i think this is a bad idea. jumping straight into subsections - we'd had to add tons of logic to handle it.
Posts: 1,881
Joined: Aug 2007
Reputation:
1
2008-02-22, 19:27
(This post was last modified: 2011-01-30, 09:55 by skunkm0nkee.)
I'm not sure I understand what you mean by 'jumping into subsections'?
The reason the Container.PrevContent would be useful (to me anyway) is when handling transitions between views and containers
Posts: 12,706
Joined: Nov 2003
Reputation:
129
spiff
Team-Kodi Member
Posts: 12,706
like, if you have a favorite to e.g. a tvshow, or a particular season of a tvshow...
Posts: 1,881
Joined: Aug 2007
Reputation:
1
2008-02-22, 20:40
(This post was last modified: 2011-01-30, 09:56 by skunkm0nkee.)
Oh right, I see what you mean. That's not really what I was intending.
I wasn't proposing changing how the navigation works at the moment at all, all I was looking for was an additional boolean property that allows the skinner to work out what the current content type is (this part exists already via Container.Content) and what content was being viewed previously (thus my proposal for a Container.PrevContent)
If it was possible, then we can set up proper transition animations so when you click on a TV Show and that takes you into the seasons or episodes you can make a better link between the two views/containers.
Posts: 1,881
Joined: Aug 2007
Reputation:
1
2008-02-23, 03:49
(This post was last modified: 2011-01-30, 09:56 by skunkm0nkee.)
I did a bit of playing about with a few ideas and the simple effect I was trying to achieve was to go from tv shows to season and/or episodes and back again and try to have the wide icon appear in each of the views but have it in different positions/dimensions for each content type, with transitions linking them so that it seemed seamless (it was purely a test to start with and I was then hoping it would lead me to try more adventurous transitions once I proved the concept).
The problem I had in getting this was that I couldn't tell what type I had just viewed so couldn't tell what should be my starting point for the transition/animation. I gathered that the hidden animation wasn't working so was doing the animation when the next content type became visible and then it would be useful to know what the previous content type was.
I would guess that handling it via intro/outro animations would have the same issue, in that I would need to know what the next or previous state was so as to work out what transition should be carried out?