So, about this StandardButtonOrigin...

[JavaWiz]

I have a dilemma.

I'd like to change the WizUiControls to honor the way sub places the buttons, so I added the StandardButtonOrigin() method to the WizUiButton and the WizUiButtonList.

The problem is that it is not the default behavior (and it probably should be). If I make a change, it will break (well, not break, but cripple) the current plugins using that code. All the skin files would have to change to account for the button position being based on the middle, top (x,y) instead of left, top.

As soon as ANY of the plugins (using WizTools) install the new version of WizUiHelper, ALL plugings will need to make the skin changes, AND any user will have to reinstall ALL plugins with the updated skins.

Although I'd like to be in-sync with subs button placement logic, I think it may cause too much grief to make the change now.

Any suggestions on how to handle (or just leave be)?

[Ted the Penguin]

didnt you implement something to allow the plugin developer to specify whether or not they want to use centered or left positioning? you could leave it like that, and then let other plugins update themselves to use the new way of doing things. whats wrong with going that way?

[Ted the Penguin]

Seconded.

As a plugin developer, it is of little concern. As a "skinner", its one of those things you can do to make the skin cohesive throughout, regardless of screen.

As a plugin developer, do what you need to do to be satisfied with your "product". Us xml jockey's can make do.

at some point I need to show you what I have done with sassari, I now have many of the skin files down to just the placements, everything else is in baseskin.xml.

[Fatman_do]

I have a dilemma.

I'd like to change the WizUiControls to honor the way sub places the buttons, so I added the StandardButtonOrigin() method to the WizUiButton and the WizUiButtonList.

The problem is that it is not the default behavior (and it probably should be). If I make a change, it will break (well, not break, but cripple) the current plugins using that code. All the skin files would have to change to account for the button position being based on the middle, top (x,y) instead of left, top.

As soon as ANY of the plugins (using WizTools) install the new version of WizUiHelper, ALL plugings will need to make the skin changes, AND any user will have to reinstall ALL plugins with the updated skins.

Although I'd like to be in-sync with subs button placement logic, I think it may cause too much grief to make the change now.

Any suggestions on how to handle (or just leave be)?

I wouldn't know how to handle it either. Easy way out is to leave it be. To change it would depend on if you can get the other plugin developers to "buy into it".

[Fatman_do]

at some point I need to show you what I have done with sassari, I now have many of the skin files down to just the placements, everything else is in baseskin.xml.

Ahhhh, perfection.

[Ted the Penguin]

Ahhhh, perfection.

I guess I could get like 90% of the stuff into base.xml, except things that change sizes or names in different plugins. mind you its still a work in progress, but I can send you a copy of what I have right now for sassari

[Ommina]

Although I'd like to be in-sync with subs button placement logic, I think it may cause too much grief to make the change now.

Any suggestions on how to handle (or just leave be)?

Other than giving an n-month warning that it is going to change so developers can get ready for the changes, I'm not sure what you can do without causing a fuss. (Although, even then, end users will not have any good reason to know that things are going ot change, and likely wouldn't even realize it until they install the first plugin and the others break.)

Can you, perhaps, do some math magic to determine which origin the developer is using? If treating the supplied x-value as the middle leads to a negative left value, you can (probably) conclude that the value supplied is supposed to be treated as the left.

Hardy perfect though by any means.