Wrecked Games

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're just that awesome.

Author Topic: Why setEventCallback ?  (Read 554 times)

kingIZZZY

  • Newbie
  • *
  • Karma: +0/-0
  • Posts: 4
    • View Profile
Why setEventCallback ?
« on: November 13, 2009, 12:40:57 PM »
Why is setEventCallback a seperate function needed to be called?

Why can't the effects of setEventCallback (which is just "mListener = mouseListener" anyway) be taken care of in createInputObject ?
Logged

pjcast

  • Administrator
  • Veteran
  • *****
  • Karma: +0/-0
  • Posts: 2653
    • View Profile
    • http://www.wreckedgames.com
Re: Why setEventCallback ?
« Reply #1 on: November 15, 2009, 06:58:43 PM »
Mainly because it doesn't need to set unless one is using buffer. Also, the interface differs based on the type of device, and the createInputDevice creates different kinds of devices.
Logged

kingIZZZY

  • Newbie
  • *
  • Karma: +0/-0
  • Posts: 4
    • View Profile
Re: Why setEventCallback ?
« Reply #2 on: November 16, 2009, 03:30:19 PM »
I see

thanks
Logged