Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Secondary IDE shortcuts settings are not saved #307

Closed
GoogleCodeExporter opened this issue Aug 24, 2015 · 6 comments
Closed

Secondary IDE shortcuts settings are not saved #307

GoogleCodeExporter opened this issue Aug 24, 2015 · 6 comments
Labels
auto-migrated Type-Defect

Comments

@GoogleCodeExporter
Copy link 

Reproducible with version 1.9.9.7, on WindowsXP Home Edition, SP3. Python
2.6.2 is installed.

1. Tools / Options / IDE Shortcuts
2. Select a command that already has a shortcut, for instance IDE
Navigation / actNavInterpreter which has the Ctrl+Alt+I shortcut
3. Add another shortcut, for instance F11

Remark: in the "Press new shortcut key", the shortcut is shown in another
language, and is inconsistent with what is shown in the "Current Keys"
window. I would fill in another PR for that except it's probably not the
most important problem.

4. Click OK.

Note: at this point, both shortcuts work as expected.

5. Quit (File / Exit)
6. Launch Pyscripter

Note: the secondary shortcut has disappeared.

Settings should be saved, it is not the case for IDE secondary shortcuts. 

See also issue 305 on editor keystrokes' strange behaviour.

Original issue reported on code.google.com by misch...@gmail.com on 31 May 2009 at 5:52
@GoogleCodeExporter
Copy link
Author 

Additional information:

1) Exported shortcuts

- exported the shortcuts, before quitting the application this is present in 
the file:

    [IDE Shortcuts\Action58\SecondaryShortCuts]
    Item0=F11
    Count=1

- after quitting/restarting Pyscripter, and exporting the shortcuts, the lines 
above
are not present anymore.

2) If the new settings (F11 in the example) is used as primary shortcut, it is 
saved
as expected. So it seems the issue is only related to secondary shortcuts.

Original comment by misch...@gmail.com on 31 May 2009 at 5:55

@GoogleCodeExporter
Copy link
Author 

This is a regression introduced in 1.9.9.7.  Will be fixed in the next version.

Original comment by pyscripter on 31 May 2009 at 9:38

  • Changed state: Verified

@GoogleCodeExporter
Copy link
Author

Original comment by pyscripter on 31 May 2009 at 10:20

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author 

Problem persists in 2.0.0.0.

Not a big deal - I only need one shortcut for any task... but was pretty 
brain-racking trying to figure out why my custom shortcuts kept disappearing.  

Resolved problem by deleting original shortcut (as it only seems able to save 
one shortcut assignment).

Original comment by pztric...@gmail.com on 31 Jul 2010 at 1:27

@GoogleCodeExporter
Copy link
Author 

Fixed in version control

Original comment by pyscripter on 19 Aug 2010 at 12:01

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

Original comment by pyscripter on 30 Sep 2010 at 3:08

  • Added labels: Type-Defect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter