(1/3) Mission im_possible

How can I know where I am now using AutoHotkey ? Editor View ? Files View ?
How can I know where I am now using AutoHotkey ? Editor area ? ViewPart area ?
How can I know where I am now using AutoHotkey ? Source ? Target ?
How can I know active file's full path ?
How can I know active segment's number ?

Parents
  • When Studio was designed, they gave absolutely no thought to the idea that someone might want to use scripting, or might not want to use the mouse.

    I have no idea why they designed it that way. Scripting languages have been around for decades and if Studio had been designed for coders, then it would have been designed completely differently. Voice recognition has also been around for decades. Everyone knew it was going to be big.

    Clearly the UI is not Studio's strong side, and clearly SDL does not have the resources to redesign it.

    Maybe SDL should think about making the UI open source.

    There might be enough users with programming background interested in redesigning the UI as an open-source project.

    Some of the information you mention might even be accessible to a redesigned UI.

    Just saying...

    Best regards,
    Bruce Campbell
    ASAP Language Services

  • Unknown said:
    When Studio was designed, they gave absolutely no thought to the idea that someone might want to use scripting, or might not want to use the mouse.

    I have no idea why they designed it that way. Scripting languages have been around for decades and if Studio had been designed for coders, then it would have been designed completely differently.

    It's apparently a result of very short-sighted idea that "Windows + coding = NET Framework".
    Good old Trados was accesible for scripting via COM interface for years, but SDL decided to "open" Studio for developers by providing NET interface only :(

    MultiTerm can be still automated via COM interface... apparently SDL has not given priority to crippling it to .NET yet... but I'm afraid it's just a question of time...

Reply
  • Unknown said:
    When Studio was designed, they gave absolutely no thought to the idea that someone might want to use scripting, or might not want to use the mouse.

    I have no idea why they designed it that way. Scripting languages have been around for decades and if Studio had been designed for coders, then it would have been designed completely differently.

    It's apparently a result of very short-sighted idea that "Windows + coding = NET Framework".
    Good old Trados was accesible for scripting via COM interface for years, but SDL decided to "open" Studio for developers by providing NET interface only :(

    MultiTerm can be still automated via COM interface... apparently SDL has not given priority to crippling it to .NET yet... but I'm afraid it's just a question of time...

Children
No Data