pygame / test / joystick_test.py

#################################### IMPORTS ###################################

if __name__ == '__main__':
    import sys
    import os
    pkg_dir = os.path.split(os.path.abspath(__file__))[0]
    parent_dir, pkg_name = os.path.split(pkg_dir)
    is_pygame_pkg = (pkg_name == 'tests' and
                     os.path.split(parent_dir)[1] == 'pygame')
    if not is_pygame_pkg:
        sys.path.insert(0, parent_dir)
else:
    is_pygame_pkg = __name__.startswith('pygame.tests.')

if is_pygame_pkg:
    from pygame.tests.test_utils import test_not_implemented, unittest
else:
    from test.test_utils import test_not_implemented, unittest

################################################################################

class JoystickTypeTest(unittest.TestCase):
    def todo_test_Joystick(self):

        # __doc__ (as of 2008-08-02) for pygame.joystick.Joystick:

          # pygame.joystick.Joystick(id): return Joystick
          # create a new Joystick object
          # 
          # Create a new joystick to access a physical device. The id argument
          # must be a value from 0 to pygame.joystick.get_count()-1.
          # 
          # To access most of the Joystick methods, you'll need to init() the
          # Joystick. This is separate from making sure the joystick module is
          # initialized. When multiple Joysticks objects are created for the
          # same physical joystick device (i.e., they have the same ID number),
          # the state and values for those Joystick objects will be shared.
          # 
          # The Joystick object allows you to get information about the types of
          # controls on a joystick device. Once the device is initialized the
          # Pygame event queue will start receiving events about its input.
          # 
          # You can call the Joystick.get_name() and Joystick.get_id() functions
          # without initializing the Joystick object.
          # 

        self.fail() 
    
class JoytickModuleTest(unittest.TestCase):
    def todo_test_get_count(self):

        # __doc__ (as of 2008-08-02) for pygame.joystick.get_count:

          # pygame.joystick.get_count(): return count
          # number of joysticks on the system
          # 
          # Return the number of joystick devices on the system. The count will
          # be 0 if there are no joysticks on the system.
          # 
          # When you create Joystick objects using Joystick(id), you pass an
          # integer that must be lower than this count.
          # 

        self.fail() 

    def todo_test_get_init(self):

        # __doc__ (as of 2008-08-02) for pygame.joystick.get_init:

          # pygame.joystick.get_init(): return bool
          # true if the joystick module is initialized
          # 
          # Test if the pygame.joystick.init() function has been called. 

        self.fail() 

    def todo_test_init(self):

        # __doc__ (as of 2008-08-02) for pygame.joystick.init:

          # pygame.joystick.init(): return None
          # initialize the joystick module
          # 
          # This function is called automatically by pygame.init(). 
          # It initializes the joystick module. This will scan the system for
          # all joystick devices. The module must be initialized before any
          # other functions will work.
          # 
          # It is safe to call this function more than once. 

        self.fail() 

    def todo_test_quit(self):

        # __doc__ (as of 2008-08-02) for pygame.joystick.quit:

          # pygame.joystick.quit(): return None
          # uninitialize the joystick module
          # 
          # Uninitialize the joystick module. After you call this any existing
          # joystick objects will no longer work.
          # 
          # It is safe to call this function more than once. 

        self.fail() 
    
################################################################################

if __name__ == '__main__':
    unittest.main()
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.