sysregion values

[frisbeemonkey]

Despite having answered two questions on sysregion="1" tonight, I was wondering if anyone could give me a basic description of what each value for sysregion does.
From my understanding:
sysregion = "1" - tells winamp to draw the layer whether or not there is a visible background under it.
sysregion = "0" - ?
sysregion = "-1" - ?
sysregion = "-2" - tells winamp to anti-alias the edges of the layer to blend it in with whatever is under it (does this work with the desktop on XP/2000?)

I'm having problems with a toggle button, it draws fine when off, but when pressed or active it only draws where the off setting originally was. There is no background behind it, so I have sysregion set to 1 which works for the initial setting, but not when you change states.
Anyways, if you know what the other values of sysregion do(or know that my understanding of the other two is wrong) or have any ideas unrelated to sysregion as to why my toggle button is behaving that way, please let me know.
Thanks,
~Frisbeemonkey

[Naamloos]

-2 is cut out from the bg

[Gonzotek]

Try increasing the amount of the transparent pixels surrounding the initial element (image="", as oppposed to activeimage="") to make it large enough to cover any other images the button has. It sounds to me like it's using the sysregion of the first image for the second.

-=Gonzotek=-

[AndrewMackowski]

Naamloos is right for sysregion="-2", sysregion="0" means that the layer will be drawn normally, ie. only if there is background behind it. And I am clueless for what sysregion="-1" does--even though I've experimented with it.

[frisbeemonkey]

Alrighty, thanks for clearing that up everyone. If anyone finds out what sysregion="-1" does, please share.

As for your suggested fix, Gonzotek, the three images are all the same dimensions(they all are within the rectangle of the off-state image.) And when it draws the other two states, it leaves a black filled area where off was(which should now be transparent.) On a side note, it works in XP w/o any problems(when desktop transparency is on.)

~FrisbeeMonkey

[KrypticK2]

Hmm ok this is a old thread and i'm not sure if everyone has figured it out already or not but here it goes. From what I can tell if you use sysregion="-1" it only knocks out the graphic directly on top of it. -2 knocks everything out on top of it. Anyhow i'm pretty sure someone had to of cleared this up by now. It's just I read this thread while trying to fix my one drawer and tried -1 just to see and it worked. So I figured alright i'll just give a response about it.

[SOOPRcow]

sysregion="1" - draws object even if there is no background bellow it. The object still has to be within the layouts region. Only used if desktop alpha is turned off.

sysregion="0" - default.

sysregion="-1" - As far as I can tell it does the same thing as sysregion="0" but I have yet to try KrypticK2's idea.

sysregion="-2" - Cuts The layouts region based on the given bitmap. Any pixel with an alpha value greater then 0 is used to cut the region. Once again only works if desktop alpha is turned off.

sysregion="and" - Draws a pixel only if its parent group's (or layout's) background image has a pixel (with alpha value greater then 0) in the same exact spot directly bellow the pixel (the image can be moved and it will be updated correctly). This does not require desktop alpha to be off.

Hope that helps

[Strike&Co.]

Originally posted by SOOPRcow
sysregion="1" - draws object even if there is no background bellow it. The object still has to be within the layouts region. Only used if desktop alpha is turned off.

sysregion="-2" - Cuts The layouts region based on the given bitmap. Any pixel with an alpha value greater then 0 is used to cut the region. Once again only works if desktop alpha is turned off.

So what happens if DTA is turned on? I'm using sysregion 2 and was hoping sysregion 1 would be helpful, but I'm running win98 so I have no clue what my stuff looks like with DTA on.
I'm assuming I should make the parts of the background that get the sysregion="2" treatment transparent on the png; but that means I'll need to doctor up a second image for that use, and I have no clue how the sysregion="1" stuff would come out.
Bother.

[J_Bloggs]

Just make it to not use DTA, to much DTA would mean people with win98 wouldn't be able to use it, and you wouldn't want to not be able to use your own skin now would you?

[Digitalhigh]

So sysregion="and" would be useful if, say, you wanted to render a drop shadow for a drawer or something. The drawer slides out, and once there's something beneath the shadow, it shows up, correct?

[rpeterclark]

Frisbee, did you ever find a solution to your problem? I have run into this and have not figured it out yet. Any suggestions?

[frisbeemonkey]

No, I never did. The problem was with my SpaceGhost skin, which I ended up abandoning for better things. What you could try is using an AnimatedLayer. onLeftButtonDown go to a pressed Frame, onLeftButtonUp go to the new state's(on or off) Frame. I haven't tested this out, but AnimatedLayers seem to handle updating better. If it is something with an action you can't mimic in MAKI, don't forget you can always just create a dummy Button and leftClick it when you want to perform the action.
Hope this helps,
~FrisbeeMonkey