Reply to thread

Message

<blockquote data-quote="Albert" data-source="post: 823957" data-attributes="member: 67886">AW: Upcoming MP2 Alpha Release- TODO List !JacobJust, you're right, the control focus navigation problems you mentioned are of two kinds: SkinEngine related and skin related.Unlike MP1, where the skin developer has to DEFINE for each control which other control will get the focus when the arrows are pressed, in MP2 the SkinEngine calculates the next focus control depending on control positions and sizes. The algorithm takes the control which is the &quot;nearest&quot; in the given arrow direction. It's hard to define &quot;nearest&quot; and sometimes, the calculation results in a focus control a human would not have guessed. Personally, I think the focus movement is quite well in most of the cases. That's why I implemented it that way. But maybe, we can fine-tune the calculation further.The other kind of problems, skin related problems, simply have to be fixed in the screen files. Here, when the master template screens are not used, the skin dev has to take care of different settings in the screen, which have already been made in the standard template screens which are used for the menu navigation and so on.So thanks, you pointed me to some problems in the fullscreen content screens! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="Albert, post: 823957, member: 67886"] [b]AW: Upcoming MP2 Alpha Release- TODO List ![/b] JacobJust, you're right, the control focus navigation problems you mentioned are of two kinds: SkinEngine related and skin related. Unlike MP1, where the skin developer has to DEFINE for each control which other control will get the focus when the arrows are pressed, in MP2 the SkinEngine calculates the next focus control depending on control positions and sizes. The algorithm takes the control which is the "nearest" in the given arrow direction. It's hard to define "nearest" and sometimes, the calculation results in a focus control a human would not have guessed. Personally, I think the focus movement is quite well in most of the cases. That's why I implemented it that way. But maybe, we can fine-tune the calculation further. The other kind of problems, skin related problems, simply have to be fixed in the screen files. Here, when the master template screens are not used, the skin dev has to take care of different settings in the screen, which have already been made in the standard template screens which are used for the menu navigation and so on. So thanks, you pointed me to some problems in the fullscreen content screens! :-) [/QUOTE]

Verification