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

[Bug] Windows system Error, when trying to edit the default stylesheet #32

Open
Golddouble opened this issue Jan 10, 2022 · 3 comments
Open
Assignees

Comments

@Golddouble
Copy link

Golddouble commented Jan 10, 2022

I use your Lutris variant of SM 17. I use the installation, I have made about 1.5 years ago.

When I go to ...
menu->Tools->Optins->Fonts
... press the "stylesheet button" and press the edit button, then I get the following message:

ksnip_20220110-151805

.
.

Lutris: 0.5.7.1
ksnip_20220110-215526

@Golddouble
Copy link
Author

Golddouble commented Jan 11, 2022

I have solved this.

  1. open Lutris
  2. select the programme (-> Supermemo 17)
  3. At the right side click on "Wine Registry"
    -> Wine Registry opens
  4. navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CSSfile
  5. in the folder "CSSfile" create the key "shell"
  6. in the created folder shell create the key "open"
  7. in the created folder "open" create the key "command"
  8. select the created folder "command"
  9. double click on "(standard)" (on right side)
  10. put in the filed "C:\windows\system32\notepad.exe %1"
  11. close the registry
  12. start supermemo 17 new and try if it now works.
    -> result: now we can edit the stylesheet

Could this "registry entry" be included in your Lutris SM Installer, so that is made automatically in the future?

@alessivs alessivs self-assigned this Jan 11, 2022
@alessivs
Copy link
Owner

Could this "registry entry" be included in your Lutris SM Installer, so that is made automatically in the future?

Yes. This is the correct way, for CSS and other file types. It will be included.

@Golddouble
Copy link
Author

Golddouble commented Feb 9, 2022

I get a similar error, when I try to make a SM repair.

File-> Repair Collection "Basic Checkup"

Result:
k20220209-135730

But here the entry in the registry is already present.
k20220209-135958

So my expectation would be, that it should work. Strange. Any idea?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants