QuantumATK Forum

QuantumATK => General Questions and Answers => Topic started by: Subhban15 on November 24, 2015, 22:17

Title: Problem with save as option in 2015 version
Post by: Subhban15 on November 24, 2015, 22:17: Is there some problem with the "save as" option in the new version or must I reinstall? I am unable to save scripts (or anything for that matter) directly.

Please look into it.

Thanks! :)
Title: Re: Problem with save as option in 2015 version
Post by: Jess Wellendorff on November 25, 2015, 08:44: There should be no problems with the "save as" functionality. In which part of VNL do you experience a problem (Builder, Scripter, Editor, etc)? You are running VNL-ATK 2015.0, but on which OS (Win, Linux, 32 bit, 64 bit)?
Title: Re: Problem with save as option in 2015 version
Post by: Subhban15 on November 25, 2015, 09:04: I am using VNL-ATK 2015 on Windows 7 - 64 bit

The problem exists in Editer as well as Scripter. On opening the editer to write script a directly the "save as" option doesn't activate. Through "file" menu only "save" option seems to be available and thus there's no option of changing the name of the file or it's location.

The only way to save any script (through Editer or Scripter), is to send the job to job manage and then save it when the dialog box appears.
Title: Re: Problem with save as option in 2015 version
Post by: Jess Wellendorff on November 26, 2015, 11:14: We have tried to reproduce the issue, but we cannot. Could you attach an image that shows what the Editor file menu looks like during the issue? Thanks!
Title: Re: Problem with save as option in 2015 version
Post by: Subhban15 on November 30, 2015, 07:33: Attaching the snapshot will not be valuable, I suppose :-\
I tried reinstalling the software to see if it was not installed correctly, but the problem persists.

Please try it this way:
1. Write few lines of codes in the Editor and then click "save as"
or
2. Send an object from builder to Scripter and then try clicking "save as"
Title: Re: Problem with save as option in 2015 version
Post by: Jess Wellendorff on December 1, 2015, 09:12: Snapshot would be helpful. I followed steps 1 and 2 on a Win10 64bit machine, and I cannot reproduce the problem.