Difference between revisions of "Talk:Move/slide an object up and down"

From the Oblivion ConstructionSet Wiki
Jump to navigation Jump to search
imported>DragoonWraith
imported>Lanceor
Line 14: Line 14:
:::PS. extra spaces between comments do make things much easier to read in the plaintext, and looks the same on the page.
:::PS. extra spaces between comments do make things much easier to read in the plaintext, and looks the same on the page.
:::[[User:DragoonWraith|<span style="font-family: Oblivion, Daedric Runes; size=2;">D</span>ragoon <span style="font-family: Oblivion, Daedric Runes; size=2;">W</span>raith]] [[User_talk:DragoonWraith|<span style="font-family: Oblivion, Daedric Runes; size=2;">TALK</span>]] 00:18, 15 December 2010 (EST)
:::[[User:DragoonWraith|<span style="font-family: Oblivion, Daedric Runes; size=2;">D</span>ragoon <span style="font-family: Oblivion, Daedric Runes; size=2;">W</span>raith]] [[User_talk:DragoonWraith|<span style="font-family: Oblivion, Daedric Runes; size=2;">TALK</span>]] 00:18, 15 December 2010 (EST)
::::Problem resolved - turns out to be a newbie syntax error not related to setting XObject. In the line:
set xStdSpeed to -5 ; <<< Change to your liking  (units per second)
::::changing the variable to "+5" will compile but the script will not run as intended. I propose that we change the number in sample script to "5" instead of "-5". Clueless n00b's like myself will easily figure out using a minus sign for down movement, but won't make the mistake of using a plus sign for up movement.--[[User:Lanceor|Lanceor]] 01:30, 15 December 2010 (EST)

Revision as of 01:30, 15 December 2010

I found that the script failed to work as-is. The condition in the onactivate block:

if xObject == 0

wasn't firing so the initial variables weren't set. I rectified it by changing the line to checking a DoOnce condition. Could someone else confirm that the original script doesn't work for them as well before I update the script? --Lanceor 10:31, 14 December 2010 (EST)

Since the very next line of code sets xObject to something not-zero, the "if xObject == 0" acts exactly the same as a DoOnce, with the advantage (??) of not using an extra variable. Can't see how this could not work.QQuix 16:12, 14 December 2010 (EST)
It should work as-is, and it makes no sense to me why it doesn't. All I can think of is the until a reference is set, xObject takes some sort of null value, but not a numerical "0" which the script may be checking for.--Lanceor 23:28, 14 December 2010 (EST)
References are initialized to a null value, but that value is zero (thus if ( refVar ) is an effective way to test if a variable has been set). What is your modified code?
PS. extra spaces between comments do make things much easier to read in the plaintext, and looks the same on the page.
Dragoon Wraith TALK 00:18, 15 December 2010 (EST)
Problem resolved - turns out to be a newbie syntax error not related to setting XObject. In the line:
set xStdSpeed to -5 ; <<< Change to your liking  (units per second)
changing the variable to "+5" will compile but the script will not run as intended. I propose that we change the number in sample script to "5" instead of "-5". Clueless n00b's like myself will easily figure out using a minus sign for down movement, but won't make the mistake of using a plus sign for up movement.--Lanceor 01:30, 15 December 2010 (EST)