Stoppedpuma

Results 191 comments of Stoppedpuma

It shouldn't collide but it should hide like the rest of the icons, This also happens with the new icons: ![image](https://github.com/woelper/oculante/assets/58333920/9bd0eaf0-8f1f-43f2-8530-fe0686ddef5a)

The current implementation is mostly fine, the problem occurs when the icons collide (folder and menu colliding into next and previous) instead of start to hide like the icons to...

That works though I think the order of which Icons disappear should be reversed on the left side (Colour channel disappears first, next and previous last if that makes sense?)...

One more issue I didn't realise before was RGBA seems to have the same anchoring problem, if it's not a lot of work you should probably figure out the file...

> Currently it is possible to select the same element multiple times to form a processing pipeline and to control their sequence. Great call, this was an oversight! I'll look...

@B-LechCode Could I actually ask your use case? The more I think about this, the more it's just extra complexity. In my mind Oculante is designed for quick edits and...

Thanks for the explanation, I'll have an updated design likely sometime today!

@B-LechCode The design has been updated accordingly! This update includes remove buttons in the filter chain and add buttons in the filters drop down ![image](https://github.com/user-attachments/assets/5775bfc8-a70f-4372-af5f-ccefef0dc8fc) ![image](https://github.com/user-attachments/assets/cd171360-5d9e-4572-80b3-808977bd55ee)

I guess this should be treated as a feature request then, as you state this is "intentional" would you be open to implementing this type of behaviour?

For example, you have multiple files in a directory called `example-x.png` as well as other files which you don't want to open. This is where using oculante `example*` would come...