region, defregion confusion

[kwerner]

I'm trying to change the "height" of the launcher area in slider-l.txt (I prefer one row of icons with no text).  

Shouldn't changing this:
defregion,14,0,0,240,56,1

to this:
defregion,14,0,0,240,19,1

change the height to 19?  It still comes out to 56.  I've already reformatted all the shortcuts and buttons so they are in one row.  I'll try to attach my modified skin.


Which brings up another question, why is there a region 15 with 0 height and 0 width?  I see there are two pages created, but why not create region 14 page 1 and region 14 page 2?


Thanks,
Kevin

[arbitrajeu]

I'm trying to change the "height" of the launcher area in slider-l.txt (I prefer one row of icons with no text).  

Shouldn't changing this:
defregion,14,0,0,240,56,1

to this:
defregion,14,0,0,240,19,1

change the height to 19?  It still comes out to 56.  

The defregion defines the height of the region, but that height should tally with the offsetadd commands inside the region.  Looking at your skin you still have:

Code Select Expand

offsetadd,0,2
...
offsetadd,0,56
You need to make all the offsetadd commands add up to 19 too.

Which brings up another question, why is there a region 15 with 0 height and 0 width?

Region 15 doesn't need dimensions as it's always embedded within region 14, which controls the repainting process.  Region 15 is just used to group together all the shortcut and button commands for two pages of shortcuts.

I see there are two pages created, but why not create region 14 page 1 and region 14 page 2?

Generally there are a number of ways to do everything.  I think most things can now be achieved with variables, rather than changing regions.  Having a separate region in this case means that you can separate the shortcuts/buttons from the general formatting and framing of the launcher.

[kwerner]

Cool that did it, thanks for the pointers!