jonib wrote:Sem;colon I think you need to link or create a new thread about this so other interested people can give feedback, most wont look in this thread about a audio lib that they are not interested in.
hmm, yes, I guess that's a good idea, I'll do that.
I don't like this it should have at least the same functionality as the old code.
I usually agree, that's why I'm asking. Anyway, it would improve the stability to leave it out, that's why I would kinda prefer it in this case.
Is there some information missing in the audio library? I think all info that the old method should be available.
No, it wouldn't say something is missing. You need to know that the design how it at the moment saves the name (not an ID or anything) of the audio device as string and uses this name to identify the audio adapter. If the name changes (via driver update) or if you have two adapter with the same name, your configuration stops working or doesn't work as intended. I could create a function that does some mapping of names to IDs but it's all very dirty. The cleanest way would be, in my opinion, to start all over using IDs, but this brakes backwards compatibility. Using the dirty helper function I mentioned could preserve compatibility, but we end up with some actions in the EG tree use the ID, some use the name - the name changes, one method brakes, the ID changes the other brakes, it's not reliable and leading to frustration for the user.
If the driver changes the device name just print an error that tells the user to check the settings.
You can't just remove functionality because it might not work all the time without adjustment.
I don't want to remove any functionality, but I would prefer to shift it from the core into a plugin, that's all. I'd prefer that from a support perspective. The user would blame the plugin for the error and not EventGhost in total. I'd like to see the core of EG rock solid.
A redesign could be relevant at some point maybe when XP is not supported anymore. If extra events is a problem there could always be options to disable them.
True, but that's a bigger design change, where should the option be to deactivate events from the EG core features? We don't have a place for this in the GUI right now.
Thank you for the feedback!!