Test Release v3.2.0

[dulux-oz]

Yeah, its a PITA (as I said) - but once you do get your head around it it makes an elegant kind of sense, I actually like the new Categories system - although I miss the colour, the look and feel of the old category "pennants" - and I had to rewrite some of the new windowclass to get them to work with my existing extension code - but because we can get rid of all the old "*small" windowclass definitions it actually makes the overall code footprint smaller.

But as I said (Moon, you can treat this as a request) I really prefer my old "dynamically sizing" sidebar code (as I mentioned a few posts ago) - well, the functionality and more granular approach, at least

[Blackfoot]

On the one hand.. I really felt there needed to be a redesign on the functionality of setting the graphics for the 'small tabs' at the bottom of all the sidebar windows.. as it was really pretty awful. I literally had JUST created new graphics for all of them.
I'm going to try and figure a way to use my new window graphics (pennants) along with the new functionality.. it might involve moving some stuff around to make it work... but hopefully it should be the best of both worlds.

[dulux-oz]

I'll look forward to seeing what you can come up with

[Blackfoot]

It seems to lose track of my sidebar selections when I /reload FG.

[dulux-oz]

Yeah, I noticed that as well - it appears the selections are being written out to the Camapign Log file, which isn't done under a /reload but is when you use the return to launcher or exit options. it may also do it with a /save, but I haven't checked.

It'll also whipes a selection for an Extension that is no longer loaded, and won't put it back when the Extension is reloaded

[Blackfoot]

Tested it with quitting out.. it retains my selections... it's only /reload that causes it to forget.
I tried /save.. it didn't help.

[callahan09]

No its not. The pathing is written into the registry and so it can only point to one location.
Why are you running 3.2.0? Generally you only run it at this time if you are developing extensions or rulesets or you are bug testing

I was testing 3.2 because I was curious about the new features, and also I am a developer myself and thought I'd contribute a note about any bugs or bad behavior I encountered, which is something I enjoy doing. If I'm ever not a help then just let me know to keep my nose out from where it's not welcome

[damned]

I was testing 3.2 because I was curious about the new features, and also I am a developer myself and thought I'd contribute a note about any bugs or bad behavior I encountered, which is something I enjoy doing. If I'm ever not a help then just let me know to keep my nose out from where it's not welcome

hah - awesome - more bug testers are always helpful. I was just checking

[damned]

I kinda freaked out when I saw this redesign as well. I had just finished new graphics for all my sidebar windows. Oof. I'm inclined to move at least some of these back to being small icons in order to improve the situation... and removing or replacing the 'sidebar' graphic is going to be essential... although that was previously designed as part of 'desktop' no??... so that shouldn't be a big deal to rearrange.

I also had just finsihed 2 complete sets of themes for morecore which now have redundant elements!

[Paul Pratt]

The sidebar change was pretty shocking. I liked the one column. For Dark Heresy I just added buttons back to story/npc's/items for quests/encounters/parcels. Leaves me with the old footprint. Add GM buttons to the data_library to get the old functioning back. There is a lot more you could do with modifying data_library. The bummer I found with the two stacking sidebar is the way it stacks, certain graphics just won't work well. Beveled edges, edge art, etc. It took some time to remap the frame defs to make it look right.