You are doing it the hard way by using the constructors directly instead of the “create” factory methods.
But when you create a TbtQuad directly:
width, height… the width and height of the quad.
ie: 1, 1 means a 1 unit by 1 unit quad. 100, 100 means a 100x100 unit quad.
imageWidth, imageHeight are the size of the image you will be using in ‘pixels’… basically these are used to interpret what x1, y1, x2, y2 mean in pixel coordinates. It’s more useful to put image pixel values in here than to hand-calculate texture coordinates.
Likely, they are not shrunk but stretched vertically. Probably the image scale is wrong for how big you want to make the buttons versus how big (in pixels) the tbt image is.
Note: if you want to make your own style file then it should be in src/main/resources and not in the java folders.
Could be that your style file is not being used. I don’t know where you put it, what you named it, etc…
You could try adding a prinln or throw an exception or something to see if it’s even being run.
Depending on your build environment, sometimes if you put it in src/main/java then it will be compiled for you but that’s not what you want. (And likely it would not compile properly anyway so I guess it’s not doing that for you.)
As for why the label color isn’t changing, that’s hard to say. The styling snippet you’ve provided should do it. I don’t know what else could be wrong.
Indeed they are stretched, and by adjusting the Container size I get them the right size. However, when I have excess space I’d like it to have more vertical padding between them, rather than scaling my Button… how should I do?
If it were me, I’d turn on trace logging for the style package and/or after I’ve loaded the styles write some debug code to peek at the various values, dump selector attributes, etc…
Set the vertical fill of your container not to stretch things.
Edit: So far, the only thing i couldn’t do with it is use hide mode which is based off whether a component is set to be visible like a swing component.
It’s always possible that it’s loading your local styles first for some reason… but then I’d have expected the container background nulling not to work.
I mean, it’s too bad. Cutting/pasting DynamicInsetsComponent wouldn’t have take too much more effort, really.