#775 Unresolvable scripting folder setting can cause an empty Scripting window

[Dmitriy]

'Scripting' window opens empty in Omegat 3.5.2, Update 1, while on the same PC with the same project the scripting feature works well in Omegat 3.1.8.

PC Specs: Windows 10 Home, AMD Phenom II X4 905e, 4 Gb.

Java version: 1.8.0_40

Current memory usage by java VM: 494 Mb, free memory: 132 Mb, memory available: 494 Mb

[Dmitriy]

Omegat copied from the 'OmegaT_3.5.2_01_Beta_Without_JRE.zip' file.

[Didier Briel]

while on the same PC with the same project the scripting feature works well in Omegat 3.1.8.

It's not a question of project, since the script path is global.

What is the path displayed in the Scripting window in both cases?

Didier

[Dmitriy]

While in Omegat 3.5.2, Update 1, the Scripting window is completely empty (no text at all, just the title bar and the window frame).

[Aaron Madlon-Kay]

I'm unable to reproduce on Windows 10 or OS X 10.11.

It would help if you provided your log, and actually answered the questions asked of you:

What is the path displayed in the Scripting window in both cases?

[Dmitriy]

Please find attached my log

[Dmitriy]

And here is how the Scripting window looks in my case.

[Aaron Madlon-Kay]

Thank you for the log.

There is a bug that occurs when the Scripts Folder path can't be resolved and you have one or more "numbered" scripts set. The bug will be fixed in an upcoming version; in the meantime you can use OmegaT 3.1.9 to change the scripts folder path (again, it would be helpful if you told us what this was) or edit your omegat.prefs file to change the path. Either way, make sure the path is valid, and it would be best to make it an absolute path.

[Dmitriy]

Thank you for your help! I used 3.1.9 to change the path to "D:\My_Documents\Omegat Scripts" and it worked.

Initial Scrips Folder parth was "C:\Utils\Omega_T.\scripts"

[Aaron Madlon-Kay]

Fixed in r7820.

[Didier Briel]

Closed in the released version 3.5.3 of OmegaT.

Didier