Help with script - Copy clipboard content into custom field in Project Settings

Hi everyone!

I need some help with perfecting a script. I used Nora’s script as a starting point. My script works… sometimes. There are some problems with the sleep delays, as my computer can be slow to open the project settings, but that I can adjust.

What happens often is that the CTRL + V step is sent too soon/late (not quite sure), so I can see the script play out, but nothing is copied into the custom field. 

I tried using super long sleep times to see if it was just a matter of speed, but it didn’t seem to prevent the problem.

Any idea? Maybe using Clipboard commands instead of the ctrl + v one? I’m an (enthusiastic) ahk beginner so I’m not yet familiar with the Clipboard commands! 

Here’s a Screenshot of the custom field and my current script:



Trados Studio Project Settings window with a custom field open for text entry, but no text is pasted into the field.


^+t::
Send ^+p ;custom Studio Shortcut to open the Project settings
Sleep 999
Send Proj
Sleep 999
Send Lang
Sleep 999
Send All
Sleep 999
Send TR
Sleep 999
Send U
Sleep 999
Send {Tab 2}
Sleep 999
Send {F2}
Sleep 999
Send ^v
Sleep 999
Send {F2}
Sleep 999
Send {Enter}

When in the Project screen with a project selected, the hotkey should open Project settings, navigate to the Update screen, open the custom field and copy the content of the clipboard, then close the text box and move selection to the OK button without clicking it, allowing me to double check the copied text before clicking ok.

Thanks in advance! 



Generated Image Alt-Text
[edited by: Trados AI at 4:24 AM (GMT 0) on 5 Mar 2024]
emoji
  • Good to know!

    I often use the mouse coordinates, but in this case I need to share the script with several project managers who work on different monitor setups, so it’s not an option.

    I’ll have a deeper look at Raphaêl Toussaint’s suggestion for the clipboard in this thread and see if I can integrate some of that to resolve the clipboard issue.

  • Hi

    I tried alternate ways of using the keyboard, then checked them in my Dragon commands until I found something that worked.

    In the case where Alt-m suddenly stopped moving the focus to an entry field, I eventually found that a simple right arrow key would also move the focus to the field. I then tried changing the Alt-m to a right arrow key in the Dragon command and found that it worked reliably.

    I don't remember what I did when an Enter button stopped responding to an Enter key sent by the Dragon command, but it was essentially the same thing. I found an alternate way to use the keyboard to activate the button, tried it in the Dragon command and found that it worked.

    Of course, the nasty thing is that parts of the decades-old Studio user interface now appear to depart so much from Windows standards that you can no longer assume that if it works using the keyboard in Windows then it will also work using AutoHotKey or other keyboard simulators.

    I was definitely not expecting that when I was debugging my Dragon commands.

    So, when writing a Dragon command, I now also have to keep in mind the possibility that the command might not work even if it has been written correctly. That makes life with Studio a bit more complicated.

    Let's hope the situation doesn't deteriorate further.