1)
PS: they look bigger than the standard 45x45, is this intended ?
Almost... they're very slightly bigger - indeed. This was more about maintaining design principles with the Info_Panel versions. The illusion is clearly
accidental while the 45x45 restrictions were simply produced by Firaxis for more accurate compression aims.
Say -- 256, 128, (80), 64, (45), 32, (22-FontIcons) are scaling relatively sharp when the filter (or methods) used doesn't ruin direct visual references between a whole range of UI situations and the images purpose.
In leeman terms -- same impact of proportional
symbols at
any resolutions for multiple and different screen space ratios.
2)
made some tests with 45x45 buttons, but there's a lot of buttons and they take too much space. IMHO drop this or use much smaller buttons as in Civ IV
Uh? The default (CivPedia style) framework has a tight gap in between these individual flips. They use a 49x200 file to squeeze the basic 45x45 items four times -- on a "Pad" with sidebars which leaves (only) 2 pixels wide empty L&R! On screen, the limited space is even more obvious. Lowering such images to (say) 36.. 32.. (etc) would defeat the whole purpose of providing simple and yet easy to use solutions to a drop-down list. Exactly why i was mentioning the indirect "flaw" earlier, btw.
Don't give up though -- there *IS* an extremely cool response to that tricky problem. I'll create an example structural design in a picture later to reveal how it would show on screen. Let me give you some hints;
- Each individual (49x50) flips area can
overlap the next to its left.
- A shadow layer (light or dark, that depends) obscures the entire row of F1 items (from right to left) when nothing is selected or mouse hovered on.
- Scan the row (mousing) and the F2(s) deploy above everything (again with some tricky shadowing process L&R) allowing us to select it to access the corresponding popup.
- The advantage to this system is that you can have a very tight row where we only "see" the IconFrame edges (4,6,10,16.. or even 22 wide) for anything that isn't selected.. yet.
- Another is that we keep the individual 45x45 files.
- Coding this stuff is just a matter of proper XML functions and values (Anchor, offset, size - etc).
Once the general (coding) principle is made clear by both of us, the easy part will be to create the necessary graphic assets.
Be patient, i'll have an example -- soon.
3)
sorry I don't have the time to do all this
Two things i can always inspect for myself to see if i can fix whatever i need to - agreed. Don't worry about this - for now. I might have some LUA
CODE questions much later though.
Ya know there are two things that still keep bothering me a little. No offense to the choosen features or design decisions taken already.
