PyCEGUI - Revision history

Crond: /* Listbox */ specificity

2011-05-22T18:19:42Z

‎Listbox: specificity

Crond: /* Caveats */ listbox caveat

2011-05-22T18:19:01Z

‎Caveats: listbox caveat

Crond: /* Subscriptions */ add link to multiclass example

2011-05-21T19:31:37Z

‎Subscriptions: add link to multiclass example

Crond: /* Example */ ce

2011-05-21T17:21:06Z

‎Example: ce

Crond: /* Example */

2011-05-21T16:55:56Z

‎Example

Crond: /* Example */ ce

2011-05-21T16:52:25Z

‎Example: ce

Crond: /* Example */ clarity

2011-05-21T16:46:28Z

‎Example: clarity

Crond: /* Subscriptions */ add longwinded example

2011-05-21T16:42:16Z

‎Subscriptions: add longwinded example

Crond: /* Base app */ note about resource location; modified CEGUI_PATH in script to make it work

2011-05-15T16:09:48Z

‎Base app: note about resource location; modified CEGUI_PATH in script to make it work

Capek: Robot: Cosmetic changes

2011-03-13T13:33:55Z

Robot: Cosmetic changes

@@ Line 264: / Line 264: @@
 </source>
-This code will produce a segmentation fault because when the local variable `item` goes out of scope, Python will garbage collect it. A possible solution to this problem is to bind it to an object, such as the following:
+This code will produce a segmentation fault because when the local variable `item` goes out of scope, Python will garbage collect it - more specifically, the listbox will reference a listbox item which no longer exists. A possible solution to this problem is to bind it to an object, such as the following:
 <source lang="python">

@@ Line 252: / Line 252: @@
 == Caveats ==
 C++ allows you to shoot yourself in a lot of ways whilst python is very limited in this area. For example if you create a window, get it and store the reference in python variable, then destroy the window, the python variable will hold a dangling pointer. This is something you have to take care of unfortunately, there is no way for us to handle this unless we affect the C++ interface which would hinder performance for C++ users. It's not that hard to handle this and unless you do something really unusual, you probably aren't going to trigger it.
 == Panda3D integration ==

@@ Line 232: / Line 232: @@
 # Enter rendering loop goes here
 </source>
 == User Data ==

@@ Line 229: / Line 229: @@
 gui = SingleClassGUI()
 gui.setupMenu()
 </source>

@@ Line 181: / Line 181: @@
      # Handler
-     # - `args` is context sensitive; which is to say that its value depends on the type of event. See `EventArgs` for details.
+     # - `args` is context sensitive; which is to say that its value depends on the type of event. See the EventArgs class for details.
      def buttonClicked(self, args):
          print('buttonClicked')
@@ Line 219: / Line 219: @@
 On a final note, this example assumes that some renderer has been setup - via OpenGL, Ogre, etc. Out of the box, this example will '''not''' work, because [Py]CEGUI has no renderer setup; once a system has been bootstrapped, this example will display a frame with a button, which when clicked, will print 'buttonClicked' to the console.
 == User Data ==

@@ Line 165: / Line 165: @@
          # the event we are listening for (in this case, the clicking of a push button) ...
          # and the method we want to call when the aforementioned event takes place.
          menu.getChild('Menu/Button').subscribeEvent(PyCEGUI.PushButton.EventClicked, self, 'buttonClicked')

@@ Line 8: / Line 8: @@
 == Base app ==
 I will provide a little base application below so you know the basics of how to use CEGUI in python environment. OpenGL is used in the base app.
 <source lang="python">
@@ Line 21: / Line 23: @@
 import PyCEGUIOpenGLRenderer
-CEGUI_PATH = ""
+CEGUI_PATH = "./"
 class BaseApp(object):
@@ Line 46: / Line 48: @@
          rp = PyCEGUI.System.getSingleton().getResourceProvider()
-         rp.setResourceGroupDirectory("schemes", CEGUI_PATH + "/datafiles/schemes")
+         rp.setResourceGroupDirectory("schemes", CEGUI_PATH + "datafiles/schemes")
-         rp.setResourceGroupDirectory("imagesets", CEGUI_PATH + "/datafiles/imagesets")
+         rp.setResourceGroupDirectory("imagesets", CEGUI_PATH + "datafiles/imagesets")
-         rp.setResourceGroupDirectory("fonts", CEGUI_PATH + "/datafiles/fonts")
+         rp.setResourceGroupDirectory("fonts", CEGUI_PATH + "datafiles/fonts")
-         rp.setResourceGroupDirectory("layouts", CEGUI_PATH + "/datafiles/layouts")
+         rp.setResourceGroupDirectory("layouts", CEGUI_PATH + "datafiles/layouts")
-         rp.setResourceGroupDirectory("looknfeels", CEGUI_PATH + "/datafiles/looknfeel")
+         rp.setResourceGroupDirectory("looknfeels", CEGUI_PATH + "datafiles/looknfeel")
-         rp.setResourceGroupDirectory("schemas", CEGUI_PATH + "/datafiles/xml_schemas")
+         rp.setResourceGroupDirectory("schemas", CEGUI_PATH + "datafiles/xml_schemas")
          PyCEGUI.Imageset.setDefaultResourceGroup("imagesets")

@@ Line 152: / Line 152: @@
 # you can ofcourse have more of these user data custom attributes
 </source>
-<strong>These do NOT persist when you pass them to C++ and back, I have to figure out a way to make them persist :-/ --[[User:Kulik]]</strong>
+'''These do NOT persist when you pass them to C++ and back, I have to figure out a way to make them persist :-/ --[[User:Kulik]]'''
 == Implementation ==