Products > Test Equipment

Open source EEZ Studio for accessing your (SCPI) instruments

<< < (22/32) > >>

mvladic:
I can't reproduce what you are experiencing. For me it works as expected. If I press Cancel button then script execution is done and nothing is stored inside local storage. If I press OK button then selected parameters are stored in local storage and script proceeds with the execution using selected parameters.

You can check what is stored in local storage here:



Knowing the true name of the "Key" you can remove from storage like this (by accessing "localStorage" object directly):


--- Code: ---localStorage.removeItem("instrument/166/scripts-storage/LiPoChargeValues")

--- End code ---

Pjoms:
I use EEZ Studio 0.9.3
Thanks for that guide to find the stored data!
If I delete it there it's possible to run the script again with the new values.


https://imgur.com/a/kYVdPvk
Edit: I tried to insert a picture, but it doesn't show up...

mvladic:
Can you try with the latest version (nightly-build)?

Pjoms:

--- Quote from: mvladic on April 29, 2020, 01:29:40 pm ---Can you try with the latest version (nightly-build)?

--- End quote ---
I can try it later, hopefully tonight. Can the nightly-build and 0.9.3 be installed at the same time?

The more I (hope) I understand how this works and hangs together, the more I'm starting to imagine that the behavior I experiencing maybe is just the right thing.
If I set up a storage with some variables in "Script1", and then if some other "Script2" is able to change the names of the variables, some funny things will surely occur in "Script1".
Am I thinking the right way here?

mvladic:

--- Quote ---I can try it later, hopefully tonight. Can the nightly-build and 0.9.3 be installed at the same time?
--- End quote ---

No. Also, after you install nightly-build it is not safe to go back to version 0.9.3, unless you make a backup of settings and database which are stored here: C:\Users\<your_user_name>\AppData\Roaming\eezstudio. This is because newer version of Studio can automatically change format of settings and database which could be problematic if you decide later to start older version.


--- Quote ---The more I (hope) I understand how this works and hangs together, the more I'm starting to imagine that the behavior I experiencing maybe is just the right thing.
If I set up a storage with some variables in "Script1", and then if some other "Script2" is able to change the names of the variables, some funny things will surely occur in "Script1".
Am I thinking the right way here?
--- End quote ---

Yes, use different names for local storage items in different scripts, unless you deliberately want to access same local storage item from different scripts.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod