News:

HOT TIP! Enable the History Window in the main UI when trying to problem solve. It provides a handy log of what is happening. Roll over lines in the History to get more details.

Main Menu

stop scrolling history button

Started by PegLegTV, December 05, 2016, 02:52:53 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

PegLegTV

would it be possible to had a button or check box for the history window that will stop it from scrolling when we are trouble shooting? similar to what Eventghost has.

jitterjames

Sure. I'll look into it when I get home next week.


jitterjames

#3
There's a new beta available with this and a couple other minor updates.

http://voxcommando.com/mediawiki/index.php?title=ChangeLog#Version_2.2.3.2

PegLegTV

Sweet thanks, this will make it a lot easier when trouble shooting or testing commands that have a lot of actions

I think there may be a bug though with 2.2.3.2, I get two different warnings

Error loading plugin: C:\Users\pegle\Desktop\VC Laptop\Plugins\PY\PY.dll
Error loading plugin: C:\Users\pegle\Desktop\VC Laptop\Plugins\Wemo\Wemo.dll


I had the install clean old dll files and then launched when finished, I also tried doing a restart, but I still receive the errors (I tried the update twice, tried to update from 2.2.2.9 both times)

I also checked to make sure the dll files where in the plugin folders, they where
I also checked to make sure that the dlls weren't blocked, they weren't

let me know if you need me to check anything else for you

the auto scroll seems to work really well  8) Thanks

jitterjames

Wow.  That's very odd.

I'm using the same installer and Wemo and Py plugins (along with everything else) seem normal here.  I just did an normal update.

Nothing will be blocked normally (AFAIK) unless you've downloaded a .dll file directly.

PegLegTV

QuoteNothing will be blocked normally (AFAIK) unless you've downloaded a .dll file directly.

That's what I thought, but thought I would double check it sense the dll's where there

PegLegTV

Finally had some time to dig into the dll problem and it appears that it was something on my end

thankfully I keep nightly and weekly backups of my VC setup (SyncBackFree), I tested my nightly first (from 12/17 5:00 AM today) and it had the same problem with 2.2.2.9

so then I tested my weekly (12/16 6:00 AM), and running 2.2.2.9 every thing worked perfect, so I rand the installer and everything is working great and I'm now running 2.2.3.2

I took a look through some of my personal logs (logs that I have VC create) and it looks like my system may have crashed yesterday (12/16) at 6:40 AM because it's showing that VC started at that time and I leave VC on at all times

Sorry for the false bug  :-[