Reply to thread

Message

<blockquote data-quote="CyberSimian" data-source="post: 1307566" data-attributes="member: 141969">One of the limitations of the MP1 skin engine is that controls cannot use expressions in the XPOS and YPOS tags. Hence a control cannot move to a different position based on the value of a skin variable. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" />To achieve a similar result, you can duplicate the control, with different positions, and with different visibility conditions, so that at any one time only one of these duplicates is visible. I am reasonably certain that the skin engine allows you to specify multiple controls with the same id, and if the id is one of the predefined ids, the skin engine will apply the same processing to each copy of that control. (Hmm, perhaps you should test that before making extensive changes, just to be sure that it will work in the way that you want.)-- from CyberSimian in the UK</blockquote>

[QUOTE="CyberSimian, post: 1307566, member: 141969"] One of the limitations of the MP1 skin engine is that controls cannot use expressions in the XPOS and YPOS tags. Hence a control cannot move to a different position based on the value of a skin variable. :( To achieve a similar result, you can duplicate the control, with different positions, and with different visibility conditions, so that at any one time only one of these duplicates is visible. I am reasonably certain that the skin engine allows you to specify multiple controls with the same id, and if the id is one of the predefined ids, the skin engine will apply the same processing to each copy of that control. (Hmm, perhaps you should test that before making extensive changes, just to be sure that it will work in the way that you want.) -- from CyberSimian in the UK [/QUOTE]

Verification