(p)Reset button

Warrior of the Light · 25th March 2004, 14:33

While creating synchnonized stuff, say 2 SSC's, I often need to close/open AVS because the scope I'm working on gets reset everytime I change something in it and the other SSC does not reset. You know what I'm talking about.

Now wouldn't it be an idea to have some sort of button that resets the preset? This prevents much irritation on my side because double clicking on the classic vis also toggles oscilloscope/spectrum/off.

Downside: closing the AVS window saves the current preset (preset00.avs?) This has prevented quite some preset-losses due to WAcrashes, (although WA5 hardly crashes anymore on my PC) or perhaps this could be included in the function of the button...

hungryskull · 25th March 2004, 16:19

I could use that too.

UnConeD · 25th March 2004, 18:28

Just use global variables instead, and all your synchronization problems will be gone.

UIUC85 · 25th March 2004, 18:49

or ctrl+shift+k but global variables are the best idea.

D12 · 8th April 2004, 19:11

I did write SS, but I had problem same as you.
If next release of AVS will have this button it's pretty cool.

Warrior of the Light · 8th April 2004, 19:33

There won't, Unconed is right. At first I thought there would be situations apart from DM's and SSC's that relied on it, but for as far as I can see there aren't, so just drop this. Globvars are the best solution.

Neoavs · 13th April 2004, 12:28

I have an addon to this. Open the AVS Debug window, then enable "Clear all local variables on all code recompiles". This also clears the global values too.

TomyLobo · 13th April 2004, 12:48

neo: Activating this option is the cause of the problem, not the solution.
If you activate this option this happens:
You change a code block, it is recompiled and the variables of that one component are reset.
variables of other components and global vars are left untouched.

Deactivating it could help keeping your scopes in sync when editing, except if you change your whatever-you-want-to-sync code.
solution: as UnConeD said, use the registers to store those whatever-you-want-to-sync values

Neoavs · 13th April 2004, 14:02

o_O.... sorry for that, my mistake...

25th March 2004, 14:33	#1
Warrior of the Light Fοrum King (AVS Reviewer) Join Date: Aug 2002 Location: The Netherlands Posts: 3,785	(p)Reset button While creating synchnonized stuff, say 2 SSC's, I often need to close/open AVS because the scope I'm working on gets reset everytime I change something in it and the other SSC does not reset. You know what I'm talking about. Now wouldn't it be an idea to have some sort of button that resets the preset? This prevents much irritation on my side because double clicking on the classic vis also toggles oscilloscope/spectrum/off. Downside: closing the AVS window saves the current preset (preset00.avs?) This has prevented quite some preset-losses due to WAcrashes, (although WA5 hardly crashes anymore on my PC) or perhaps this could be included in the function of the button... Jesus loves you [yes, you] so much, he even died for you so that you will not need to die, but live forever

25th March 2004, 16:19	#2
hungryskull Major Dude Join Date: Feb 2003 Location: Somewhere in Canada Posts: 776	I could use that too. Darn, I can't think of anything to put here.

8th April 2004, 19:33	#6
Warrior of the Light Fοrum King (AVS Reviewer) Join Date: Aug 2002 Location: The Netherlands Posts: 3,785	There won't, Unconed is right. At first I thought there would be situations apart from DM's and SSC's that relied on it, but for as far as I can see there aren't, so just drop this. Globvars are the best solution. Jesus loves you [yes, you] so much, he even died for you so that you will not need to die, but live forever

13th April 2004, 12:48	#8
TomyLobo Major Dude Join Date: Feb 2004 Location: Germany Posts: 578	neo: Activating this option is the cause of the problem, not the solution. If you activate this option this happens: You change a code block, it is recompiled and the variables of that one component are reset. variables of other components and global vars are left untouched. Deactivating it could help keeping your scopes in sync when editing, except if you change your whatever-you-want-to-sync code. solution: as UnConeD said, use the registers to store those whatever-you-want-to-sync values If you can't say something nice, say something surrealistic.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

25th March 2004, 18:28	#3
UnConeD Whacked Moderator Join Date: Jun 2001 Posts: 2,104	Just use global variables instead, and all your synchronization problems will be gone.

25th March 2004, 18:49	#4
UIUC85 Senior Member Join Date: Oct 2003 Posts: 272	or ctrl+shift+k but global variables are the best idea.

8th April 2004, 19:11	#5
D12 Banned Join Date: Apr 2004 Location: Blood Posts: 42	I did write SS, but I had problem same as you. If next release of AVS will have this button it's pretty cool.

13th April 2004, 12:28	#7
Neoavs Junior Member Join Date: Jan 2004 Location: Vilnius, Lithuania Posts: 29	I have an addon to this. Open the AVS Debug window, then enable "Clear all local variables on all code recompiles". This also clears the global values too.

13th April 2004, 14:02	#9
Neoavs Junior Member Join Date: Jan 2004 Location: Vilnius, Lithuania Posts: 29	o_O.... sorry for that, my mistake...