search

stevehsudrawing / quanto

Quanto is a desktop customization tool based on Rainmeter.
https://forum.rainmeter.net/viewtopic.php?t=41809
Other
102 stars 3 forks source link

Program freezing during setuo #12

Open blueciffer56 opened 10 months ago

blueciffer56 commented 10 months ago
Screenshot 2023-12-07 133014

When I get to this screen, the program freezes up. Trying to reinstall results in the same issue.

stevehsudrawing commented 10 months ago

You may need to apply a layout via Manage Rainmeter (You can open it via Rainmeter tray icon), instead of Select a layout in Quanto. Currently, this issue is known to occur in some devices.

blueciffer56 commented 10 months ago

You may need to apply a layout via Manage Rainmeter (You can open it via Rainmeter tray icon), instead of Select a layout in Quanto. Currently, this issue is known to occur in some devices.

Yea I tried that, but because it freezes the rain meter entirely, I am not able to apply

stevehsudrawing commented 10 months ago

You may need to apply a layout via Manage Rainmeter (You can open it via Rainmeter tray icon), instead of Select a layout in Quanto. Currently, this issue is known to occur in some devices.

Yea I tried that, but because it freezes the rain meter entirely, I am not able to apply

Oh that sounds not good. I think it can mean that some of the skins in the layout don't work properly on your device.

You may need to add skins on your own. Once you have reinstalled Quanto and applied the default layout, don't click on the welcome screen and go straight to Manage Rainmeter. Disable the welcome screen at first (Active skins button on the upper left corner of the window -> The first option in the context menu -> Unload it). Open Fluent_Design\Extras\Settings\16x14.ini in the file tree on the left. After that, you should be able to add skins via Quanto Settings.

I need to know the crux of the matter. If you add a skin that causes Rainmeter to crash, please report it to me immediately.

I think the most likely cause of the crash is a bug in the Media Control Widget. Now you can try the latest release 1.31.1.