View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0008476||MediaMonkey (current)||Properties/Auto-Tools||public||2011-10-05 19:31||2012-02-01 04:04|
|Target Version||4.0.3||Fixed in Version||4.0.3|
|Summary||0008476: Issues re. first run in Elevated mode (D&D problems, etc)|
|Description||When MM is run in elevated mode (e.g. on first run, or upon configuration changes to the OS integration panel), attempts to drag and drop artwork / tracks fails.|
e.g. drag image from firefox onto the Art & Details window
--> 'Do not enter' symbol appears by the cursor instead of the 'copy' symbol
|Fixed in build||1465|
I am afraid that we cannot do anything about this, based on links like
this is problem with any program.
The problem is tied to how security permissions work. The ability to drag and drop from a normal applications to an elevated one would break the security model behind UAC.
I guess we should compose KB article based on tips from here:
||I suppose the only 'fix' would be to not run MM in elevated mode after changes are made to the config, but rather to quickly run an elevated config process, after MM has been closed to take care of config changes.|
I'm not sure if we can make small APP that will start in Elevated Mode to do config (after install for example) and start MM in non elevated mode while app will wait for MM to finish settings or Add command switch to start that small app in Elevated mode after user Click OK in OS integration Panel?
Guess it is something for MM 4.1
Another problem reported is that even in portable mode, MM is forced to run 'Elevated' the first time it is run (which shouldn't happen since there aren't/shouldn't be any system changes in portable mode).
The current approach of forcing MM elevate:
- the first time it is run
- on any run subsequent to making config changes
is problematic for several reasons:
1) it's confusing in normal scenarios (i.e. why is MM running elevated)
2) it breaks d&d for the duration of that session
3) it triggers re-elevation issues for users that install as Admin but run MM as standard user (see 0008943)
4) it triggers elevation in portable mode which shouldn't happen.
From a user's perspective, the app should never run elevated except when:
a) installing the app
b) upon making config changes that require elevation (e.g. spawn a separate elevated process)
Assigning to Jiri for feedback re. 4.0.3.
||This will be fixed by fixing 0008943.|
||Fixed in 1465|