Advanced Script Help

from WinCustomize Forums
Trying to slim down some scripts and/or put everything into one base script. I've encounter somewhat of a little block.
Instead of using a dozen timers that essentially do the same thing I'm trying to pass the object down through the function call into the sub's but for some reason I can't pass the object name from the function into the respective timer. Any Ideas?

Code: vbscript
  2. Const mskT1="mskTab1"
  3. Const objT1="objTab1"
  5. Dim speed
  6. speed=50
  8. '--Begin Universal Button Functions
  9. '--Left Click Mouse Selection
  10. Function Object_OnLbuttonupEx(obj,x,y,dragged)
  11. With DesktopX
  12.     If Not dragged Then
  13.     Select Case obj.name
  14.         Case objT1
  15.         tBarSlide(mskT1)
  16.     End Select
  17.     End If
  18. End With
  19. End Function
  21. Function tBarSlide(obj)
  22. With DesktopX   
  23.         If .Object(obj).Left >= 0 Then
  24.           object.KillTimer 100
  25.       object.SetTimer 200,speed
  26.     Else
  27.       object.KillTimer 200
  28.       object.SetTimer 100,speed
  29.         End If
  30. End With
  31. End Function
  32. '--Timers
  33. Sub object_ontimer100
  34. With DesktopX.Object(obj)
  35.     If .Left < 0 Then
  36.     .Left = .Left + 5
  37.     Else
  38.     object.KillTimer 100
  39. End If 
  40. End With
  41. End Sub
  43. Sub object_ontimer200
  44. With DesktopX.Object(obj)
  45.   If .Left >=0 Then
  46.     .Left = .Left - 5
  47.   Else
  48.     object.KillTimer 200
  49. End If
  50. End With
  51. End Sub

desktopx
1,740 views 3 replies
Reply #1 from WinCustomize Forums Top
Never mind I found a dirty work-a-round.

Code: vbscript
  2. Const mskT1="mskTab1"
  3. Const objT1="objTab1"
  5. Dim speed,objX
  6. speed=50
  8. '--Begin Universal Button Functions
  9. '--Left Click Mouse Selection
  10. Function Object_OnLbuttonupEx(obj,x,y,dragged)
  11. With DesktopX
  12. If Not dragged Then
  13. Select Case obj.name
  14. Case objT1
  15. tBarSlide(mskT1)
  16. objX=mskT1
  17. End Select
  18. End If
  19. End With
  20. End Function
  21. Function tBarSlide(obj)
  22. With DesktopX
  23. If .Object(obj).Left >= 0 Then
  24. object.KillTimer 100
  25. object.SetTimer 200,speed
  26. Else
  27. object.KillTimer 200
  28. object.SetTimer 100,speed
  29. End If
  30. End With
  31. End Function
  32. '--Timers
  33. Sub object_ontimer100
  34. With DesktopX.Object(objX)
  35. If .Left
  36. .Left = .Left + 5 Else
  37. object.KillTimer 100
  38. End If
  39. End With
  40. End Sub
  41. Sub object_ontimer200
  42. With DesktopX.Object(objX)
  43. If .Left >=0 Then
  44. .Left = .Left - 5
  45. Else
  46. object.KillTimer 200
  47. End If
  48. End With
  49. End Sub
Reply #2 from WinCustomize Forums Top
It's because obj is only created within the Object_OnLbuttonupEx and passed on to the function tBarSlide. You need to store the object in a variable in the global script space. Though the problem with that is what happends if the timer get called simultaneously from several objects. They'd then overwrite themself.
Siege of Centauri
Reply #3 from WinCustomize Forums Top
They'd then overwrite themself


Yeah, discovered that. So, it would only be acceptable within limited use. Wonder if there is a way to block the call until the previous call is completed?

Edit: I'm wondering if there's a way to set the other objects to inactive. Like a separate sub?