Originally posted by BodgeIT
View Post
I get that page defaults to location 0,0 and that all we can do is move a "sized" background around that page using <posY><posX>. At the moment I'm trying to use this as a highlighting background to group my buttons. I just can't get the background to show on the page.
I'm expecting the above script to drop my background
onto the screen into position 0,0. I was then going to move it to the correct position. I just don't see the background.
onto the screen into position 0,0. I was then going to move it to the correct position. I just don't see the background.
<posX> and <posY> within <background> will likely default to 0 but probably <width> and <height> are too as there are no <defaults> available for <background>.
The existing <width> and <height> tags you have included are at the <page> level - and so set the page width/height - not the background. A page currently always defaults to position 0,0 and occupies the full width and height of the screen so these pos tags are not currently used.
<background>
<image>back-control.jpg</image>
<visible>true</visible>
<posX>175</posX>
<posY>70</posY>
<width>225</width>
<height>225</height>
</background>
I remember you mentioning about setting defaults and that if they weren't set, that items could disappear but I have a default for the background set.
It seems the moment you add <alpha> to the page, all buttons are affected although this may only be in effect when a <group> tag is used.
This is where I feel the current override logic simply fails and yet I get it works...wierd.
This is where I feel the current override logic simply fails and yet I get it works...wierd.
<defaults>
<button>
<alpha>
....would be the way to create a default button transparency - either within <overrides> , within <layout> or within a <page> depending on the intended scope of the defaults. You could also include an <alpha> tag within any specific <button> that you didn't want to take the default value.
This requires those extra <defaults> features - and the <alpha> default - as I said before... hopefully in the next beta, but that's on Martyn's todo list.
The tag spreadsheet is a really good cross reference of the validity of the tags at the various nested levels... I will be reposting an updated one but it is pretty good for sorting out things like the above....
I know example enhanced XML files would help too....
K
Comment