TESTERS NEEDED - Low End Machines

[diafero]

I found the reason why the button is not enabled when linking in first
Your SDL files says:
" VAR BOOL Hut3doorbutton2Func[1] DEFAULT=0 DEFAULTOPTION=VAULT"
that's what the tutorial says, but of course this means that per default, the button is NOT clickable. Changing it to "DEFAULT=1" should fix the problem.

[D'Lanor]

I thought the idea of the puzzle was that the buttons should not be clickable initially. That is the way I set it up when I gave the code to boblishman (that was before I wrote the quickscript and put the instructions on the wiki).

But perhaps for that particular button the IntActEnabler should not be used at all?

[diafero]

IMHO it should be clickable from the beginning on, that's the way it used to be, isn't it?
From how I see it, an IntActEnabler is just perfect, but it must be a custom one (not a quickscript) and should be tied to the SDL which controls the state of he door. When the door is opened, it should be enabled, otherwise not. That would avoid a superfluous SDL value and the risk of having it out of synch.
In the end, it's boblishman who will have to decide how it should behave

[D'Lanor]

Yes, he has to decide. Like I said, this isn't the quickscript. That didn't exist yet. This is the full alcscript so it can be configured any way he wants it.

But it isn't really out of sync, is it? It is working consistently: no power, no hotspot. Or am I misunderstanding the problem again?

You see, sometimes people PM me to code something for them but I often have a hard time understanding what they want or how it should fit into the big picture they have in mind. So I could come up with something totally unexpected. You have been warned.

[diafero]

Of course that happens when someone who doesn't know the whole project does a very small sub-part of it. I don't expect him to be angry at you for that

Power? Actually, I did not speak of the power... and besides, I have it switched on.
But in the case of this door, the problem is that when the door is opened, the button is covered by the door and so it should not be clickable. And when the door is closed, the button is visible and should be clickable. If the door actually opens after clicking, that again should depend on the power.

[D'Lanor]

Oops... Right, this wasn't for the power. I confused it with my own project.

You are right about the SDL default of 1. That should fix it, with the current Python code that is.


Ok, I will shut up now and get some sleep. My mind is not functioning properly when I am only half awake. Which is currently my normal state of mind after I get home from work. I so need a vacation but that isn't going to happen until September.

[boblishman]

sorry to take so long to reply ... but you seem have worked it out between you ...

Yes, I think the change should sort it out ...I'll try it and report back!

[boblishman]

yes ... you'll be pleased to know that it works correctly now !

(just uploaded the "fixed" version if you want to check it ) ... Thanks Guys!!

[diafero]

Where can I download it?

Which way did you choose, to change the default value or to completely eliminate the superfluous SDL var (superfluous because Hut3doorbutton2Func must always be 0 when HutThreeactivedoorOpen is 1 and vice versa, so one of them is unnecessary - and there's the danger of having them out of synch)? Since you plan to change the doors to use the "new" method as well, in the long run it would be better (and less work) to change the alcscript to use a different variable.

[boblishman]

All the links lead to the same download ...

1) The first post of this thread
2) The Inspection Sub-forum (Sonavio) at the Maintainers (Testers Wanted - 1st Post of the thread)

or you can use THIS link

I chose the "simple" method ... changing the DEFAULT=1 in the SDL (The SDL now has Version 3)