[Cheiron]

Hullo

we have a bounce room thing at MP... you type sr and it kicks you to a bounce room and you pop back to room you came from... here it is:

In room you are currently in... there is following spotscript that holds the globals:

[Scotsman]

To avoid some nasty race conditions, I would create a seperate routine to call the gotoRoom, and then instantiate that routine from the timer call.

In general it's a bad idea to call any of the manor api routines directly from a timer. It may work fine for you, but I can virtually guarentee it will break for somebody.

[Cheiron]

OK...well a lot of manors ...if not all, use the manor.setTimer(... then functions inside).. so I guess we are all screwed then?? ... if I understand you right

could you elaborate on that in above example, please?
_________________
Cheiron
______________________________
"Any scientist with respect for himself should start
the day by rejecting his own pet hypotheses".
(Konrad Lorenz)

"Wir müssen wissen
Wir werden wissen"
(David Hilbert)

[mimee]

Here is the script i used for my bounce room ....... the timer is nested .........and it works...

the sr for each room:

[code]

import manor
import string

roomnumber = 100

def find(str, ch):
index = 0
while index < len(str):
if str[index] == ch:
return index
index = index +1
return -1

def setPos(userpos):
global index
try:
xpos = int(userpos[0:index])
ypos = int(userpos[index + 1:len(userpos)])
manor.setPos(xpos, ypos)
except:
pass
return

def mnr_inchat(userID, chatText):
global roomnumber
if chatText == "sr":
if userID == manor.myID():
chatText = ""
userpos = manor.getUserPos(manor.myID())
userpos = str(userpos)

#write cookie
f=open('WM-subret.txt', 'w')
f.write(str(roomnumber)+chr(10))
f.write(str(userpos))
f.close
manor.gotoRoom(500)
return chatText

def mnr_enter(userID):
global index
if userID == manor.myID():
try:
f=open('WM-subret.txt', 'r')
f.readline()
userpos = f.readline()
f.close()
f=open('WM-subret.txt', 'w')
f.write("" + chr(10))
f.write("" + chr(10))
f.close()
userpos = userpos[1:len(userpos) - 1]
index = find(userpos, ",")
manor.setTimer(manor.tickcount() + 15, setPos, userpos)
except:
pass
return





Bounceroom script:

import manor

go = 1

def mnr_inchat(userID, chatText):

global go
if chatText == "reset":
go = 0
return chatText



def mnr_enter(userID):

global go
f=open('WM-subret.txt', 'r')
roomnumber = int(f.readline())
f.close
if go == 1:
manor.setTimer(manor.tickcount() + 30, manor.gotoRoom, roomnumber)

return

Scots, now does this have the same "issues" as the suggestion Cheiron made ???

Mine has a timer and somewhat the same structure as setTimer.
It has never caused me any problems.

Mimee

[Scotsman]

Not saying it is going to cause everyone problems right away, it may even be a minority of users.

What I am saying is it's not a good idea. The only reason that works today with some API calls is just a coincidence. Future versions the specifics of the internal parameter passing may change. Not to mention timers are implemented in threads, and threads have different subtleties between Windows, OS X, and Mac Classic.

The developer recommended way to do this (meaning the one I am sure to test and make sure works in future versions) is to have your own python routine that you give to the timer to call that then takes the desired action.

[Bri]

I seem to remember the SR script was in the ‘manor command’ candidate list. Years ago, about every other room was using it so the total python lines to just “Front my Avatar“ was huge.
Front as in change Z.
_________________
RL..now with 100% less lag!

[Lisa]

[mimee]

hey Lisa hugss

as u see not much has changed in manor... no answers !! the sr i posted , you wrote and worked fine....... why make things so damn complicated ??

Mimee

[Scotsman]

Pardon my feeble memory, SR script? Wuz Dat?

[Cheiron]

hmmm....
_________________
Cheiron
______________________________
"Any scientist with respect for himself should start
the day by rejecting his own pet hypotheses".
(Konrad Lorenz)

"Wir müssen wissen
Wir werden wissen"
(David Hilbert)

[Lisa]

[Scotsman]

oh duh. No just have a cold making it hard to keep things straight.

Will look at this a bit, I question the need for the timer function at all unless it's trying to work around an issue in the software.

If so relying on timers is something that is normally avoided if possible (you don't even want to know how often one has to work around quirks in the OS, that change from one revision to another no less) as different machines will have different timing for the issue your trying to work around.

[Jade]

get well soon Scots, passing the tissues
Jade

[Lisa]

The timer was used to avoid a quirk in the software, I forgot what quirk because it's ages ago I wrote this lil beauty. I will think about it and maybe it will pop up.
_________________
-Lisa-