Re: Possible bug in system node -11
Status: Alpha
Brought to you by:
cwalther
From: James C. W. <jfc...@ya...> - 2011-10-21 20:34:09
|
Yeah, that sounds exactly right. Thanks for clarifying! One other thing: I'm not certain how the messaging system works. How do I tell pipmak which node to contact? If I just do "34:message(lightFlicker)" or "34:getid():message(lightflicker)" pipmak says "unexpected symbol near 34", both times. I'm probably making a stupid mistake but I don't know what it is. Thanks, James --- On Thu, 10/20/11, Christian Walther <cwa...@gm...> wrote: From: Christian Walther <cwa...@gm...> Subject: Re: Possible bug in system node -11 To: "Content creation for the Pipmak Game Engine" <pip...@li...> Date: Thursday, October 20, 2011, 4:13 PM > There may or may not be a bug in pipmak's system nodes-- specifically node -11. > In a few nodes in my project, there are several sounds which, while declared in node.lua are not yet placed in the project folder. Whenever I enter one of these nodes, pipmak prints the expected "The system cannot find the file specified". However, about 3 times out of 5, it also prints: > "Error running text editor keydown handler: -11/node.lua:76: calling 'selection' on bad self (texteditor expected, got userdata) > stack traceback: > [C]: in function 'selection' > -11/node.lua:76: in function <-11/node.lua:33>" Node -11 is the Lua command line. I think what you're seeing is what was fixed in revision 211 <http://pipmak.svn.sourceforge.net/viewvc/pipmak?view=revision&revision=211>. I'm not sure about the details without more information about your situation, but one way to provoke that error message (before r211) is as follows: You have node A open, and the Lua command line above it. You do pipmak.gotonode(B). The node.lua of node B has an error that prevents the node from loading (a missing sound file should not be sufficient for that). Node A has already been left, but node B could not be entered, which means that the Lua command line (node -11) is now the bottommost node in the node stack, i.e. the background node. (*) Now you do pipmak.gotonode(C). This leaves node -11 and enters node C, and the former is what triggers the error message, since node -11 is designed to work as an overlay, not as a background node that can be left in that way, so it is confused by that. Maybe you can align this explanation with your experience somehow, and if not, at least find a reliable way of reproducing the error. You should easily be able to recognize situation (*) by the fact that the Lua command line appears on top of a gray striped background rather than on top of one of your nodes. -Christian ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ Pipmak-Users mailing list Pip...@li... news://news.gmane.org/gmane.games.devel.pipmak.user https://lists.sourceforge.net/lists/listinfo/pipmak-users |