xboxscene.org forums

Author Topic: This Would Be Helpful  (Read 338 times)

flattspott

  • Archived User
  • Hero Member
  • *
  • Posts: 1220
This Would Be Helpful
« on: February 22, 2004, 07:13:00 AM »
Like the $ActualPath$, only this would be for ActionScripts.

This post has been edited by flattspott: Feb 22 2004, 03:15 PM
Logged

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
This Would Be Helpful
« Reply #1 on: February 22, 2004, 07:15:00 AM »
Well, list any other specials you want, too...

when I hit that code, I'll look at adding them.
Logged

flattspott

  • Archived User
  • Hero Member
  • *
  • Posts: 1220
This Would Be Helpful
« Reply #2 on: February 22, 2004, 07:55:00 AM »
Aside from that, all I'd really like is a bit more info in the ActionScriptReadMe.txt file. For the odd stuff that I have no idea what it's for or even how or why I should use them.

Specifically these one

CODE

    - FNMERGE []
-- IQGetMsgID  []
-- IQPeekMsgID
-- IQPeekStrength
-- IQPeekShiftStrength
-- IQPeekCtrlStrength
-- IQPeekAltStrength
-- IQGetMsgCount
-- UIGetEvtCount
IQClear
IQTable
IQPushMsg
IQWaitMsg [ [...]]
ReconfigUIObject
UIQClear
UIQGetEvent
UIQPeekEvent
Logged

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
This Would Be Helpful
« Reply #3 on: February 22, 2004, 08:31:00 AM »
QUOTE (flattspott @ Feb 22 2004, 12:48 PM)
Aside from that, all I'd really like is a bit more info in the ActionScriptReadMe.txt file. For the odd stuff that I have no idea what it's for or even how or why I should use them.

Specifically these one

CODE

    - FNMERGE []
-- IQGetMsgID  []
-- IQPeekMsgID
-- IQPeekStrength
-- IQPeekShiftStrength
-- IQPeekCtrlStrength
-- IQPeekAltStrength
-- IQGetMsgCount
-- UIGetEvtCount
IQClear
IQTable
IQPushMsg
IQWaitMsg [ [...]]
ReconfigUIObject
UIQClear
UIQGetEvent
UIQPeekEvent

-- FNMERGE <Path> <Filename> [<Extension>]
.....Merges a path, base filename and extension into a single, complete file path


-- IQGetMsgID  [<ID>]
.....Pops an Input Message from the queue and loads the variable with the Msg ID
-- IQPeekMsgID
.....Peeks (doesn't remove it from the queue) at an Input Message from the queue and loads the variable with the Msg ID
-- IQPeekStrength
.....Peeks (doesn't remove it from the queue) at an Input Message from the queue and loads the variable with the Msg Strength
-- IQPeekShiftStrength
.....Peeks (doesn't remove it from the queue) at an Input Message from the queue and loads the variable with the Msg Shift Strength
-- IQPeekCtrlStrength
.....Peeks (doesn't remove it from the queue) at an Input Message from the queue and loads the variable with the Msg Ctrl Strength
-- IQPeekAltStrength
.....Peeks (doesn't remove it from the queue) at an Input Message from the queue and loads the variable with the Msg Alt Strength
-- IQGetMsgCount
.....Loads the variable with the number of input messages waiting on the Input Queue
-- UIGetEvtCount
.....Loads the variable with the number of UI Event messages waiting on the Input Queue

IQClear
....Clear the Input Queue of messages
IQTable <name>
....Sets the translation table to the named translation table (as defined in the internal.xml or MXM.xml files)
IQPushMsg <ID> <Str> <ShftStr> <CtrlStr> <AltStr>
....Allows you to push a message onto the Input Queue
IQWaitMsg [<MsgID> [...<MsgID>]]
....Waits for a message matching one or more Msg IDs

ReconfigUIObject <Handle>
....Forces the dialog with the given handle to refresh it's configuration (mostly not needed) Why is it not needed? Because if you use the dialog handle to set XML values in the dialog config, it will force the dialog to refresh anyway.

UIQClear
....Clears the UI Event Message Queue
UIQGetEvent
....Pops a UI Event Message from the UI Event Message queue
UIQPeekEvent
....Peeks (does not remove the message form the queue) at a UI Event Message on the UI Event Message queue
Logged

flattspott

  • Archived User
  • Hero Member
  • *
  • Posts: 1220
This Would Be Helpful
« Reply #4 on: February 22, 2004, 09:23:00 AM »
Thanks alot. smile.gif
Logged

geniusalz

  • Archived User
  • Hero Member
  • *
  • Posts: 1635
This Would Be Helpful
« Reply #5 on: February 22, 2004, 10:18:00 AM »
When is the UI event queue needed?  AFAIK, each event is triggered instantaneously.
Logged

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
This Would Be Helpful
« Reply #6 on: February 22, 2004, 11:01:00 AM »
QUOTE (geniusalz @ Feb 22 2004, 03:11 PM)
When is the UI event queue needed?  AFAIK, each event is triggered instantaneously.

For modeless dialogs wink.gif

You might want to monitor the queue if you were displaying a progress dialog, for example.
Logged

Kthulu

  • Archived User
  • Hero Member
  • *
  • Posts: 787
This Would Be Helpful
« Reply #7 on: February 27, 2004, 07:05:00 PM »
as far as $ScriptPath$ goes, if you are just wanting the path to the currently running script, try this...

CODE

BeginDraw
 MessageBox "Hello, i am a script.  My path is %0%"
EndDraw


This post has been edited by Kthulu: Feb 28 2004, 03:32 AM
Logged

LarryX

  • Archived User
  • Newbie
  • *
  • Posts: 26
This Would Be Helpful
« Reply #8 on: March 13, 2004, 12:46:00 PM »
QUOTE
Like the $ActualPath$, only this would be for ActionScripts.



I use a script under _autoexec in mxm.xml...

To keep MXM versital these paths would need to be editable most likely in the mxm.xml...   I don't like using $ActualPath$ because it's realative to where mxm is run from.  An absolute path edited by the user one time I think would be better...

CODE
;#
;#Set MXM Scripting Enviroment Path Variables
;#auto load in AutoExec in MXM.xml
;#


SET _scriptpath "c:\\mxm\\mxmscripts\\"
SET _gamepath "f:\\games\\"
;SET _appspatch "f:\\apps\\"
;SET _skinpath "c:\\mxm\\mxmskins\\"
;SET _mediapath "e:\\mxmmedia\\"
;SET _thumbspath "e:\\mxmmedia\\"
;SET _coverartpath "e:\\mxmmedia\\"
 
Logged

flattspott

  • Archived User
  • Hero Member
  • *
  • Posts: 1220
This Would Be Helpful
« Reply #9 on: March 13, 2004, 02:29:00 PM »
That is a badass idea, why didn't I think of that?

I'm gonna make this into a script that puts nodes just for that into the MXM xml and the use and autoexec script to get the paths.

This post has been edited by flattspott: Mar 13 2004, 10:29 PM
Logged