|
|
#1 | |
|
Junior Member
Join Date: Nov 2000
Location: Nova Scotia
Posts: 16
|
Well, here I am again asking some more stupid questions I guess.
Question 1:- Would it speed up my scripts any if I created timers and stated them when they are needed? and then delete them out when they are no longer reqiured? ex: Button.onEnterArea(){ Timer = newTimer; Timer.setDelay(5000); Timer.start(); } Button.onLeaveArea(){ delete Timer; } Question 2:- I have my skin with two modes....normal and remote (shade) modes. Part of my "normal" mode background is an alpha channel and is invisible. When I switch to "remote" mode, the "remote" background snaps to the left and top of the now unseen "normal" background. My problem is, when you move the "remote" background close to the right edge of the scrren to far, when you switch back to "normal" mode, the normal background is off the darn edge of the screen and can't be moved. I tried changing the x, y and default x, y values for both the skins.--NO GO. I tried useing script to realign, or remember the two different layout positions, but I got GURU errors....WHAT DO I DO TO FIX THIS ANNOYING DELIMEA?????????? Quote:
|
|
|
|
|
|
|
#2 | |
|
Major Dude
Join Date: Sep 2002
Location: ?
Posts: 1,473
|
Re: Timers on the fly and wierd shade problem
Quote:
if delay is 0 then timer.stop(); would speed up the skin a bit... but if the delay is 5000 then its no big deal. |
|
|
|
|
|
|
#3 |
|
Senior Member
|
i have run into the same problem, if you rename your main window like this it solves the problem: <container id="main" name="whatever" default_visible="1">
i don't know exactly what the problem is but here is a fix. Blah! |
|
|
|
|
|
#4 |
|
Major Dude
|
Just stop the timer. An 'ideal' timer would take 0 cpu when stopped. Winamps are ideal but they're close. Just stopping them should be enough.
I wouldn't delete them like that. I would be concerned about the timer not matching up with the proper ontimer. |
|
|
|
![]() |
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|