Mouse Button Shortcuts Fail

Alan Kilborn

@notsobitwise said in Mouse Button Shortcuts Fail:

My new problem is that launching directly from the NPP folder is the only way to avoid Admin mode which I don’t need.
This is behavior I have never seen before- no matter how I launch, it always goes into Admin mode. I even tried calling a batch file that launches the EXE and also tried having it launch a shortcut located in in the EXE folder. Neither the shortcut nor EXE properties specify Admin.
I looked for a command line argument to force no-admin but could not find one. Is there some option to do this?

I had this same problem a few years ago.
I didn’t know why it was happening.
Then one day it stopped happening (and I was glad).
I hope it is easier for you to figure out why.

NotSoBitWise

@alan-kilborn

Since I want NPP to launch with Windows, I created a shortcut and placed it in my “user” Startup folder.
From here, when selected, it does not launch as Admin.
Unfortunately, on restart, Windows does launch it in Admin mode.

However, I have found a solution…in place of Windows File Manager, for years I have used XYplorer that so too many features to cover here including a scripting language for custom configuration. If you aren’t familiar check it out; it’s cheap and the developer is very responsive. (I am not a paid promoter, only a user)

One very helpful feature is the ability to configure toolbar buttons to do pretty much anything. So I configured it to launch NPP and it does so without forcing Admin mode.
It would be nice to have NPP auto launch with Windows but since I have XY up all the time, it’s a minor inconvenience to load it manually.

This was my first post here and from the quick response I received appears a great community. Thanks very much to all who responded!

Alan Kilborn

@notsobitwise

Well, I use XYplorer as well, and it is great…but I think your problems related to admin mode are not really germane to what file manager you use.

artie-finkelstein

@notsobitwise said in Mouse Button Shortcuts Fail:

However, I did find the problem- NPP is launching in Admin mode.

This may not be the only/real issue:
I run the entire Win7 system in Admin Mode with Notepad++ always launching in Admin Mode. Unfortunately I’ve just spent the last few days removing Setpoint and all the other Logitech telemetry ~~crap~~ programs so I can no longer check if my having Notepad++ in Admin Mode worked because Setpoint was also in Admin Mode.

If it matters:
I’m still using the Logitech Unify receiver and have switched to X-Mouse Button Control to remap the scroll wheel tilt codes.

NotSoBitWise

@alan-kilborn

I did not mean to give that impression, and I agree, choice of file manager is not the issue. My point was explaining how I had finally found a way to launch without forcing Admin mode.

I might speculate that since I am an Admin, that context is impacting how NPP is launching. XY is not launched in Admin mode so when it executes the launch, the different context may be the difference. Pure speculation on my part as I have no clue why I’ve experienced this.

NotSoBitWise

@artie-finkelstein
Thanks for passing along, I was not familiar. It looks like a major improvement over SetPoint and I would love different button behavior across different apps. Any issues using it?

artie-finkelstein

@notsobitwise
It did take me a bit to figure out that I had to create a new profile for Notepad++ by clicking on the Add button under the large almost empty Application / Window Profiles area to enable a custom (per application) profile, the rest was nicely guided by application dialogs.

I installed XMBC with Setpoint still running and then started uninstalling Setpoint and all the Logitech zombies; numerous reboots, renames and manual registry edits as guided by the remnants displayed by Autoruns. I don’t think Logitech believes anyone really wants to remove their ~~spyware~~ software. I have an alert in the Device Manager for the Human Interface Devices > Logitech Unifying USB Receiver entry telling me that

Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)

However, I am still using the M705 with it’s previously paired Unify receiver. I may have to resort to reinstalling the Unify driver software when I next need to pair a Logitech device with one of the Linux boxes, but that can wait.

In summary, no problems with XMBC, too many problems with Logitech not honoring the program uninstall command(s).

NotSoBitWise

@artie-finkelstein
Could you have just started by uninstalling SetPoint and reverted to the generic Windows mouse driver and then installing XMBC?

Unifying software isn’t resident in memory so is periodically running it for pairing a problem?

artie-finkelstein

@notsobitwise
Yes, but I wanted my tilt-wheel mappings available no matter where I was in the conversion process, so I chose the path I followed.

Yes, pairing would be an issue, but I’m not buying any more Logitech products (have you read their latest EULA?; they now sell mice that won’t enable all the buttons if you don’t first install a download that has licence terms I won’t agree to.)

NotSoBitWise

@artie-finkelstein
The Logitech software has been problematic for years. In SetPoint, the toggle setting to control application specific buttons does not persist during system restarts. It also fails to support all the mouse options so you still need to load the Windows mouse utility for some settings. Their newer Logitech Options utility has made things worse since you still need SetPoint AND Windows Mouse for complete control. You have to wonder what their design strategy might be.