Dev question : Texture filters

[Steff]

I currently rework and test the noggit UI.
Yesterday I added some more usefull word filters to the texture filter window.



Now the window is getting to big I think for smaller then hd screens.
Now my question is.

Are the zone filters usefull or could I just take them out.
I never used them and even if they are gone you can just reload noggit and only load the textures of the zone you want. This way you get the same result. Only textures from one zone.

Please vote and tell me your reasons why they are needed.

[Skarn]

Hmm, I think it is a weird idea to remove them. I often use the Load all tilesets function, so that it loads all the existing texture files. Then I remember I saw some required tileset in some zone and I use that filter. Could I reload Noggit? Yeah, possibly. Though why should I do it if there is a filter?

[Nupper]

I found zonefilters very useful but i think sorta of a page per page for zone names would be useful.

[Gratural [Харгард]]

Zone filter are needed, especialy if standart textures not used (as in my project)
But you can hide zone tags by
1. Adding button  "show|hide zone filter tags", like button "From txt' in ojbect edit mode, or
2. Adding text form for sorting texture into texture palette (by entrering part of texture or folder name )

[Steff]

Thanks for your suggestions.
Don´t forget the vote

[schlumpf]

Texture palette should be manually defined sets with additional filters and manual filters, and predefined sets for zone and blocking tilesets.

[Kaev]

Pages or a scrollable area should keep the window small and would allow to keep all filters. Does anything speak against using such things in this case?

[schlumpf]

Pages or a scrollable area should keep the window small and would allow to keep all filters. Does anything speak against using such things in this case?

Scrollable frames are a pain to implement, so the sdl version never got them. Pages are already used for textures, iirc.