search

marcopixel / monstercat-visualizer

A real time audio visualizer for Rainmeter similar to the ones used in the Monstercat videos.
MIT License
920 stars 103 forks source link

Cant drag this skin #314

Closed classych1c closed 4 years ago

classych1c commented 4 years ago

So I got the visualizer to work and it moves when sound is playing. My problem is that I can't move it at all. When I try to make it draggable through rainmeter it has it locked so I can't change it. Any solutions?

eileenthg commented 4 years ago

Have you tried unchecking "Keep on screen" at Rainmeter manager for the visualizer?

classych1c commented 4 years ago

No but I’ll be sure to try that. If this changes anything I late found out that I can’t move any of my skins on Rainmeter. I tried deleting and reinstalling some skins but it didn’t change anything.

classych1c commented 4 years ago

So I tried your suggestion but it didn't seem to work at all. Here's what is looks like. I also tried turning various other settings on an off to see if that would change anything but nothing seemed to work. image

eileenthg commented 4 years ago

Why is "Draggable" off? That setting is supposed to be on if you want to drag the visualizer around. ah i guess that's the problem. don't know how to fix that.

hshams28 commented 4 years ago

Having the same issue here and have tried the above mentioned as well. Also to note: the "Draggable" option is also greyed out for me.

sctanf commented 4 years ago

Are other skins also not draggable? Try going to the Rainmeter manager and click on the settings tab at the top, there is an option that disables dragging. If it is on, that's probably why you can't drag anything, and you have to turn it off so the other draggable toggles will stop being grey.

marcopixel commented 4 years ago

This seems to be an issue with your local Rainmeter installation, check if you have the latest version of Rainmeter installed and check if the Rainmeter.ini file has correct permissions (needs to have write access).

Since it's about a month since the last reply, i'll assume this issue has been fixed. If not, please reply as a comment down below!