You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 22, 2024. It is now read-only.
So I am playing w/ the clipboard_monitor commands again. Honestly it works really well, so this one is kind of a nitpick. I would consider this issue as low priority.
As you can see you get that operation error. At that point if you do clipboard_monitor_stop, you will see a different op error: 758.
Maybe you're wondering "sinn3r why would you do that?" I dunno, cuz I am an asshole?
Even though you see the error, it's still not that bad. You can simply start again and the monitor is back in business.
So I guess it would be nicer to have something that checks if there is already a monitor or not. Or maybe it does already? I haven't tried to look at the code to find out. A print_warning that says "Go Home, You Are Drunk!" or something like that would be great.
The text was updated successfully, but these errors were encountered:
We can see that gClipboardState is set to NULL this point, which is what causes things to misbehave.
Very nice catch! This is actually not a low priority issue as you have pointed out @wchen-r7, I think it's a higher priority. The reason is because this results in the clipboard monitor running infinitely, which will ultimately blow enough memory to crash (or at least be more obvious forensically). It could also prevent clean shut downs.
I will get on this pronto. Well played, nice find!
So I am playing w/ the clipboard_monitor commands again. Honestly it works really well, so this one is kind of a nitpick. I would consider this issue as low priority.
If you do this:
As you can see you get that operation error. At that point if you do clipboard_monitor_stop, you will see a different op error: 758.
Maybe you're wondering "sinn3r why would you do that?" I dunno, cuz I am an asshole?
Even though you see the error, it's still not that bad. You can simply start again and the monitor is back in business.
So I guess it would be nicer to have something that checks if there is already a monitor or not. Or maybe it does already? I haven't tried to look at the code to find out. A print_warning that says "Go Home, You Are Drunk!" or something like that would be great.
The text was updated successfully, but these errors were encountered: