Option to turn off Enable/Disable XMBC notifications

[coldlucas23]

Cold you please add an option to disable those notifications, or just include it on the "Show layer switch baloon notifications" option, so when it's disabled, notifications about enabling/disabling XMBC also gets hidden.

Thank you!

[phil]

Yes, thats not a bad idea, especially because on Widows 10 the new notifications are a bit of a pain.
Do you think it should also apply to the update notification (that does not happen very often)?

I'll add it to my todo list (probably just use the existing balloon setting for simplicity!

[coldlucas23]

Thanks for the response

Well, I think the update baloon is quite important, so there's no need to do so.
But changing the subject, I don't know if I should create a new topic or not, but for simplicity, I'll add it here:

I was setting a way to make my SetPoint work with XMBC and I found myself in the need to have more than one Default profile, so I though about exporting the two Default profiles I need in .xmbcs files, so every time I want to change, I just execute the file I want to be the default.

But I don't know if this is a new addition, but I can't do it, the 'Export' button is disabled for the Default profile, I don't remember it being disabled before...

Can you make it so we can export the Default profile, or have two or more Default profiles (with the possibility to activate only one at a time)?

Thanks again for your attention.

[phil]

No its never been possible to export the default profile - cant you use different layers or are you using layers for something else?

I will have a look at allowing multiple defaults but its going to require a significant underlying change as the file ans internal mem structures all assume only one default. Allowing import/export will probably be ever - you could always just have multiple settings files for the time being and have a batch/script to exit xmbc, switch them in and out and restart xmbc!.

Phil

[coldlucas23]

Done!

For anyone who's going to read this, here's the script:

EDITED AND CORRECTED!
"C:\Program Files\Highresolution Enterprises\X-Mouse Button Control\XMouseButtonControl.exe" /Exit
cd "C:\Users\[Your User]\AppData\Roaming\Highresolution Enterprises\XMouseButtonControl\"
rename "XMBCSettingsALT.xml" "XMBCSettingsSHF.xml"
rename "XMBCSettings.xml" "XMBCSettingsALT.xml"
rename "XMBCSettingsSHF.xml" "XMBCSettings.xml"
start XMouseButtonControl.exe

save as .bat, have an alternative of the settings file named "XMBCSettingsALT.xml" and place it in the same directory of the former.
This solved my problem, thanks!

[phil]

FYI instead of killing the task, to quit the existing running instance of XMBC, you can use a command line argument to a new call to XMouseButtonControl.exe and it will communicate with the running instance and instruct it to quit.

I think its /exit but you can do a /? to see all the available CLI options (there are quite a few!)

[coldlucas23]

Unfortunatelly I don't know nothing about cmd, I can only use Google to try to do something on my own, but I couldn't understant what you're talking about.
What command is this that can have an \exit argument?

[phil]

The XMBC application itself has /Exit (probably case sensitive)
so if you use:
xmousebuttoncontrol.exe /Exit
it should close the running instance of XMBC