[issue27603] Migrate IDLE context menu items to shell extension

2017-01-11 Thread Shane Smith
Shane Smith added the comment: Since you're a developer, I'm sure you need a lot of versions installed so you can check for backwards combatibility (spelling intentional). But until recently, only the most recent IDLE was in the context menu, so I'm guessing your workflow for that checking

[issue27603] Migrate IDLE context menu items to shell extension

2017-01-11 Thread Shane Smith
Shane Smith added the comment: I'm fine with a single implementation, so long as the implementation is what's best for the majority of users. Not my intent to increase the burden of work. So, let me ask the question alluded to in my first post: when is a nested menu actually desirable? I

[issue27603] Migrate IDLE context menu items to shell extension

2017-01-11 Thread Shane Smith
Shane Smith added the comment: Hi Vedran, that seems to now be the default behavior, regardless of previous installs (my 3.6 was a clean install, and it's still nested). Kind of a pain if you want to edit with IDLE frequently. While we wait for a more integrated solution, the hackish way

[issue27603] Migrate IDLE context menu items to shell extension

2017-01-07 Thread Shane Smith
Shane Smith added the comment: Would it be possible to allow the user to select whether they'd prefer a nested or flat context menu at install? I believe it went to nested as a result of issue23546. Unless there are a large number of installations (arbitrarily... perhaps 4 or more