.

Thanks for bumping this video, Paul . I hadn't spotted it before.

Definitely worth watching. I'm still running V1, so I was particularly interested to learn more about V2. It seems Jesús Prieto runs V1 and V2 side by side. Are there disadvantages of doing that? Are the icons identical? How would I associate a script with one or the other version? 

Thanks,

Emma    

Emma Goldsmith 

Emma Goldsmith said:

I was particularly interested to learn more about V2. It seems Jesús Prieto runs V1 and V2 side by side. Are there disadvantages of doing that?

For me the disadvantage was confusion :-|

So I took the leap and have tried to work only with the latest version as I think the old one will at some point not be supported at all any more, and because I think the new one does offer more capability.

I know Jesús Prieto has a lot more scripts than I do so moving is a significant effort so I think he runs both while he's transitioning... but he can best answer that one!!

Hola, Emma Goldsmith

Emma Goldsmith said:

Are there disadvantages of doing that?

Yeah, as Paul said, confusion is the main disadvantage. I haven’t started really to migrate my V1 code, because I’m afraid some parts will be tough to convert to V2. Hotstrings are not an issue, but complex code grabbed from Internet will be a nigthmare, and I still haven’t decided when to start, not in the short term.

Emma Goldsmith said:

Are the icons identical?

They are slightly different icons:

Emma Goldsmith said:

How would I associate a script with one or the other version? 

We need the new directive #Requires, for example: #Requires AutoHotkey v2 (https://www.autohotkey.com/docs/v2/lib/_Requires.htm)
Also, if you use Scite4AutoHotkey, you can decide which version to run the script by using this button in the toolbar:

Thank you, Jesús Prieto . Almost all my scripts are copied from the Internet (including this forum) and are randomly pooled in a single 700-line AHK file that loads at Windows start-up. The idea of converting it and troubleshooting the errors is a nightmare, as you say. But worse for me as I have a very limited understanding of what each line does!

I will stick to V1 for the moment. 

I have a few questions about things mentioned in the webinar and will (re)open threads to ask them.

But just one more question here, if you don't mind:
Is the pop-up menu you used in Trados (with "copy project filename" at the top) created with Quick Access Popup? If so, is it an alternative menu in QAP that you call up with a dedicated shortcut?

Many thanks,

Emma

Thank you, Jesús Prieto . Almost all my scripts are copied from the Internet (including this forum) and are randomly pooled in a single 700-line AHK file that loads at Windows start-up. The idea of converting it and troubleshooting the errors is a nightmare, as you say. But worse for me as I have a very limited understanding of what each line does!

I will stick to V1 for the moment. 

I have a few questions about things mentioned in the webinar and will (re)open threads to ask them.

But just one more question here, if you don't mind:
Is the pop-up menu you used in Trados (with "copy project filename" at the top) created with Quick Access Popup? If so, is it an alternative menu in QAP that you call up with a dedicated shortcut?

Many thanks,

Emma

 Emma Goldsmith 

Emma Goldsmith said:

Is the pop-up menu you used in Trados (with "copy project filename" at the top) created with Quick Access Popup?

No, it’s not, but it could have been done with QAP. The pop-up menus is created directly with AutoHotkey code. Quick Access Popup is a really easy way to do the same thing.

The menu pops up when I press the CTRL+Ñ hotkey and the actual menu depends on the application. I mean, the pop-up menu in Trados Studio is different than the one popping-up in Word or Excel or….

Thanks, Jesús. Very interesting. I'll have a play with QAP when I have time.