VA CTD when editing order change of Windows Mouse Lock in a command.

[scottb613]

Hi Folks,

64 Bit - v1.10.3

VA CTD when editing order change of Windows Mouse Lock in a command.

Regards,
Scott

[Pfeil]

Has this happened more than once?

Does it happen even when you create a new profile and replicate the same set of actions?

What are the steps to reproduce the crash, in detail?

[scottb613]

Hi Pfeil,

Thanks for the response.

It's repeatable in my profile - however - on your advice - I created a new profile and attempted same - no crash. It seems as it's just a problem unique to my profile.

Image of me replicating event in new profile - it works here. In my original profile - when I drag and drop the mouse command to the #1 position it CTD's.

We can disregard.

Thanks.

Regards,
Scott

[scottb613]

Hi Pfiel,

If it's any help - here's an image of me doing the same thing in my profile with an issue - as soon as I try to drag and drop the same mouse command - VA CTD.

I added my actual profile in question - for review - as well.

Regards,
Scott

[Pfeil]

Does it occur in multiple commands in your profile? If so, only when modifying existing commands, or even when creating a new command?

I added a "Block Mouse Input" to the "Mouse Click 56" command, then drag-and-dropped it, which causes no issues on my machine.


What you could try is to make a backup of the profile database by clicking the "Click here to browse VoiceAttack's data folder." link on the "System / Advanced" tab of the VoiceAttack options window and making a copy of "VoiceAttack.dat" in a safe location, import the profile you've already exported, then see whether the issue still occurs in the imported copy.



As an aside, rather than creating multiple variations of that command, you could retrieve the spoken number from the command phrase.

E.G.
Mouse Click [5;10;25;50;56;90;180]

Code: [Select]

Fully restrict mouse movement
Play sound, '{VA_SOUNDS}\confirmation_beep.wav'
Start Loop : Repeat [{CMDSEGMENT:1}] times
    Click left mouse button
    Pause 0,1 seconds
End Loop
Unrestrict mouse movement
Play sound, '{VA_SOUNDS}\confirmation_beep.wav'


[scottb613]

Hi Pfiel,

Thanks for the instantaneous response - I'll try what you suggested, and I'll post the result. Have to run out for a bit now.

and THANK YOU - if VA can read spoken numbers - it will make my life so much easier. Anxious to try that suggestion as well.

Regards,
Scott

[scottb613]

Hi Pfeil,

One final thought before I run out - when I switched to "Fully Restrict Mouse Movement" I could move them around at will 
 - I only got the CTD when using "Block Specific Mouse Actions".

I'll follow up when I have more time.
 

Regards,
Scott

[Gary]

@scottb613 -  If there's any way for you to get your VoiceAttack.dat (%APPDATA%\VoiceAttack) up to me at support@voiceattack.com, I can throw it into the debugger and see if I can identify what is up.  Could be something that can be easily fixed.  Like Pfeil, I'm not able to reproduce that here.

[scottb613]

Hi Pfeil,

I tried same on other commands within profile with issue - CTD.

I've used loops before - I read up on CMDSEGMENT - how do I create this loop - I can't seem to do it with the commands available in the menu?

"Start Loop : Repeat [{CMDSEGMENT:1}] times"

Hi Gary,

I looked at the file you suggested - time stamp was from hours earlier today - I stopped and started VA - no change on time stamp. I replicated the failure CTD - no change on time stamp. Is this correct? If the time stamp doesn't update - how can it have current data. I'm a Unix guy - so PC's aren't my forte.

Regards,
Scott

[Pfeil]

It's the "Loop Start - Repeat a Certain Number of Times" action, which you're already using in those commands.

Only difference is using the token to retrieve the number predefined in the dynamic command section of your command phrase (E.G. the phrase shown in italics above the code block for my example), rather than using a literal number directly.


VoiceAttack.dat is the profile database. As the issue seems to be occurring with a specific profile, chances are there's corrupted data in the database (which is why importing the profile could resolve the issue, as it should re-create the profile data, without transferring the corrupted data)
As the crash occurs while you're editing a command, there would be no reason for the profile database to be written to, as you haven't committed any changes yet at that point (until you use the "Apply" or "Done" buttons, they only exist in memory and aren't written to disk)

[scottb613]

Hi Pfiel,

Once again - thanks for your help and patience. I'm away from home for the weekend - I'll send the file and try recreating your loop when I get in next week.

Much appreciated.
 

Regards,
Scott

[scottb613]

Hi Folks,

File packed and sent.

Loop working as you stated - thanks. Big improvement.

Also - I checked the issue on a second machine where I have VA loaded - it also CTD when attempting the move that started this thread. I don't have any idea why you're not seeing the same - unless I buggered up two machines.
 

Regards,
Scott

[Pfeil]

Did you copy over the profile database from your other machine to the second one, or was the profile imported from a .vap file?

[Gary]

I got the .dat and was able to reproduce the problem.  I also exported the profile and then re-imported and experienced the same result.  I'll be out of pocket for a bit, but will pick this back up when I get a moment.

[scottb613]

Hi Folks,

Exported via VAP.

Thanks for all the interest/help and completely at your leisure.


Regards,
Scott

[Pfeil]

Gary fixed this in the latest beta (v1.10.3.26).

[scottb613]

Pfeil and Gary,

Thank you kindly...
 

Regards,
Scott