[RESOLVED] Need help with CSS for new setting for AAO player

[DeathByAutoscroll]

Hello. I have functionally programmed a way to allow the player to change the sound of voice blips while playing a case (Demonstration video) however I have been unable to wrangle the CSS to make this new addition look even halfway decent without side effects, and I am requesting help with this by someone who knows how to CSS.

Current:


Goal:


The code can be found at https://bitbucket.org/deathbyautoworksp ... ceBlipVol/

[TimeAxis]

I’m not sure CSS would be the issue here. The goal is for it to be a volume slider, right? So you’d probably want to use a Range element. But it seems like to do that you might need to add a function to form_elements.js to add range elements since one doesn’t exist currently? I’m not 100% sure on that, or why it would be set up in such a roundabout way if so.

[DeathByAutoscroll]

I’m not sure CSS would be the issue here. The goal is for it to be a volume slider, right? So you’d probably want to use a Range element. But it seems like to do that you might need to add a function to form_elements.js to add range elements since one doesn’t exist currently? I’m not 100% sure on that, or why it would be set up in such a roundabout way if so.

A volume slider was an idea I have decided to drop. After applying the KISS principle and also inputting the language strings, it became clear that there would not be space for a volume slider that the user could have any kind of fine control over. The CSS is an issue as the text does not align with the other options, as well as the wrapping caused by comically long box for a 3 digit max input.

[Enthalpy]

I can give this a look over the weekend, but because a few other obligations are taking longer than expected, I can't commit to this any earlier.

[Enthalpy]

Having thought this over some, I wonder if it would be better to have a collapsible volume section that would let the user change blip, sound effect, and music settings...

If we do that, then the CSS problems go away, no?

[TimeAxis]

A collapsible section for all 3 sounds good to me. Personally I’m more partial to bars as well instead of having to input a number every time, which feels very janky. I don’t think fine tuned control over the exact number is necessary for volume. Ideally they would use page data to remember your settings as well.

[DeathByAutoscroll]

Having thought this over some, I wonder if it would be better to have a collapsible volume section that would let the user change blip, sound effect, and music settings...

If we do that, then the CSS problems go away, no?

I agree that would be better long term, although this currently significantly outstrips my current capabilities and the time I can currently dedicate to leaning how to do this. I'll have a look at trying to figure out how to make a custom sound/music section interface work fully when I have time, especially with how SoundHowler works with custom audio. If anyone else wants to take on this challenge before then however please feel free to go for it.

[Enthalpy]

Well, you can probably reuse the code we have for collapsible debug sections.

In any event, I'm not inclined doing the CSS learning I'd need to do to answer the original question when we're going to get rid of it soon anyways.

[DeathByAutoscroll]

Noted, will look at the debug menu! Marking as resolved for now with the new proposal/plan. Thank you for having a look over this and for the great suggestions.