fwcd

Results 260 comments of fwcd

@CsCherrYY If you use the Java extension package (or more specifically, the Java Dependency Viewer), a project explorer is already included: ![grafik](https://user-images.githubusercontent.com/30873659/64221787-494eda00-cece-11e9-8d92-edc98c585c81.png)

Love the JSON-to-Codable conversion, that looks super useful!

Those are already very helpful insights, thanks! Most of the implementation in this PR is currently just standard boilerplate for adding a request, the actual logic is yet to be...

This actually ended up being a lot easier to implement than I thought thanks to the semantic refactoring!

Linux support somewhat depends on upstream (https://github.com/avahi/avahi/pull/18), so someone would have to put some work into polishing up/rebasing/adding tests to that PR before we could progress on #7.

> One primary issue is that marking entire classes `[[deprecated]]` will result in build failures due to `-Wdeprecated -Werror` Can we use `-Wno-error=deprecated-declarations` etc.? (IMO It would still be useful...

> A warning for deprected function that we want to keep in the code for now will introduce a lot of noise. Contributors will start to look into it on...

> The contributor should always start over with a clean build without any warning Yeah, that's fair and it makes sense to me to reduce the number of warnings as...

Here's another example of GLSL ![Screenshot 2024-02-01 at 16 29 36](https://github.com/mixxxdj/mixxx/assets/30873659/8337d2c1-f94c-47db-8362-f76bc8a4c28a) vs. GLSL (legacy) ![Screenshot 2024-02-01 at 16 29 44](https://github.com/mixxxdj/mixxx/assets/30873659/0fe76e1a-5e33-4fa1-baa7-78cdadc7aa7b) I've found myself switching back to the legacy waveforms for...

Both screenshots were taken with the (then) most recent 2.5/main builds