Vector art tends to be done at bargain basement 90s clip art quality these days by lazy developers who don’t want to hire actual vector art skilled designers (notorious on iOS), but yes, there’s nothing really that visually complex in the Reason GUI that couldn’t be recreated in vector.EvilDragon wrote: Wed May 01, 2019 5:46 pmBetter yet, drop the bitmaps and vectorize them as they are right now. Then they can be blown up to support any size and resolution. But that's tens of thousands of bitmaps and also fiddling with the core of the codebase as well.Jace-BeOS wrote: Wed May 01, 2019 4:34 pmThis is all I want. Thing is, they must have made the original assets at low resolution, otherwise why have they STILL not enlarged the rack UI? It’s likely not the re-coding of the GUI (which isn’t simple, I know), but the bitmaps needing recreation from scratch.
It would eat some CPU though (especially if they use a “bitmap to vector” converter that does a shitty brute force job), with the large number of lines/curves and gradient fills needed to faithfully reproduce the current designs. This is another reason why developers drop apps on the market with super shitty line drawings for GUIs. It’s not a huge CPU impact, but it’s definitely more than writing a set of static/animated/alpha-transparency bitmaps to screen. I can imagine users noticing increased CPU usage and complaining.
Maybe GPU can be utilized here, but that seems to present a huge kettle of bugs every time some developer attempts it (especially on Windows). Either way, this needs to be addressed by the industry some day soon. it should’ve been done by now, but...
Not that we will need to perpetually increase sizes. I expect there’s an upper limit to the resolution we can practically use (size of screens and pixel density won’t perpetually increase, though we don’t seem to be at the end of usable increases yet).
