Author Topic: Event handling for inline functions  (Read 132 times)

Exergist

  • Sr. Member
  • ****
  • Posts: 281
  • Can you dig it?
Event handling for inline functions
« on: May 09, 2018, 12:29:12 pm »
It would be great if there could be some event handling built into the VAProxy so that a 'Stop Commands,' profile switch, and/or maybe even setting a VA variable could trigger an event in an inline function. Would be particularly useful for cleaning up, especially when running async tasks from within the function that keep running even after a 'Stop Commands' is issued.

Thanks!

Gary

  • Administrator
  • Hero Member
  • *****
  • Posts: 1482
Re: Event handling for inline functions
« Reply #1 on: May 10, 2018, 08:07:15 am »
I'm thinking this will be good.

SemlerPDX

  • Newbie
  • *
  • Posts: 13
  • Upstanding Lunatic
    • VETERANS-GAMING
Re: Event handling for inline functions
« Reply #2 on: May 11, 2018, 01:53:55 pm »
If they were also in tokens, it would be great to have "VA Program State" variables, i.e. current profile, log file text direction (new entries top/bottom), key/mouse/joy input on/off, etc. so basic conditions could evaluate that.
Good People - Great Teamplay - VETERANS-GAMING

Pfeil

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1346
  • RTFM
Re: Event handling for inline functions
« Reply #3 on: May 11, 2018, 02:20:45 pm »
If they were also in tokens, it would be great to have "VA Program State" variables, i.e. current profile
"{PROFILE}" is already implemented.

, log file text direction (new entries top/bottom),
Agreed.

key
"{STATE_SHORTCUTS}" is already implemented.

/mouse
"{STATE_MOUSESHORTCUTS}" is already implemented.

/joy input on/off, etc. so basic conditions could evaluate that.
"{STATE_JOYSTICKBUTTONS}" is already implemented.