I've decided to illustrate with pictures, first, rather than expecting someone to debug my skin.
I use region 1 for the launcher, defined thus:
region,1,0,-1
defregion,1,122,0,118,16,1
I also use region 4 for each page of the launcher icons, defined thus:
region,4,0,-1
The defregion for 4 is defined above region 1, as follows:
defregion,4,0,0,0,0,3
Here we have the skin compressed, showing the date and launcher part:
(http://arbitrajeu.co.uk/Collapsed.jpg)
Then, when I enable the RSS region, it's all offset of some reason:
(http://arbitrajeu.co.uk/RSS.jpg)
The region for RSS is defined thus:
region,15,0,-1
defregion,15,0,0,240,56,2
But then when I enable the weather region too, it's all okay:
(http://arbitrajeu.co.uk/Weather.jpg)
The weather region (0) is defined thus:
defregion,0,0,38,240,100,4
...
region,0,0,-1
It appears that my region 15 (RSS) is inheriting the x position from the defregion for region 1. I've checked for rogue offsetadd commands and am using none that affect the x coordinates.
Any thoughts?
1) Do you have a offset,offset_-1,offset_-1 after each defregion ? this resets the offsets to what is defined by the defregion.
2) I would think this is the problem:
region,1,0,-1
defregion,1,122,0,118,16,1
thsi defines region 1 to be
1) x = 122 +current x offset
2) y = 0 + current y offset
if you have the aforementioned offset command, it would make the current offsets equal to those defined in the defregion.
unless youre resetting the x offset back to 0 somewhere all subsequent command that rely on the x offset will be offset b y 122 pixels.
to reset the x offset you could do a offsetadd,-122,0 or offset,0,offset_-1 (this means set the x offset to 0 and the y offset to whats defined as the offset for the current region)
hope this help
Superb. Just the job.
Whilst I had taken on board the "it's good practice to put offset,offset_-1,offset_-1 in every region", I'd not actually thought through what I was doing when I did it. Thanks for pointing out that it is effectively like putting an offset,x,y command in periodically throughout the code. Makes total sense now.
Progress resumes...