2013-01-19, 17:38
Hi guys,
currently we can't focus empty container and this is causing some headaches with focus sometimes (see http://forum.xbmc.org/showthread.php?tid...pid1303866 ).
Most desired fix is to make empty container focusable but there are some issues that need to be thought about:
So what are your thoughts on this?
EDIT: forgot to add - this for sure won't be added before Frodo, so don't worry about breaking your skins now
currently we can't focus empty container and this is causing some headaches with focus sometimes (see http://forum.xbmc.org/showthread.php?tid...pid1303866 ).
Most desired fix is to make empty container focusable but there are some issues that need to be thought about:
- Making empty container focusable could mess directional navigation in some situations - now if container is empty, we just pass navigation through that container and move along (I mean <onleft> etc navigation). With proposed fix we would stop navigation on empty container which might be unwanted in some cases (f.e. in confluence home window we could focus recently added/addon shortcuts container even if they would be empty). To avoid that we would need to add <enable> condition to containers where we want old behaviour or the other way around - add some flag that will allow to focus empty containers (as most of the times focus headaches are with containters with media listings and not static content).
- We have no builtin way to indicate that container is focused. So here goes question - do we need such builtin method? We already need to make use of "Control.HasFocus(container_id)" in itemlayouts to differentiate unfocused container from focused one. To show/hide indicator we could use visible condition "Control.HasFocus(container_id) + StringCompare(Container(container_id).NumItems,0)" (or something like that, this was not tested).
So what are your thoughts on this?
EDIT: forgot to add - this for sure won't be added before Frodo, so don't worry about breaking your skins now