How to Post mxGraph Questions

Before posting:

\n
• \n

  The evaluation version of mxGraph comes with a readme.html file. Within this are links to the API specification, known issues and the developer user manual.

  \n
\n
• \n

  Search through the previous forum questions using the search box.

  \n
\n
• \n

  If the question is how to work within a particular JavaScript development framework, please ensure that you have understood that mxGraph requires next to no integration with any framework, see section 2 of the user manual.

  \n
\n
• \n

  If the question is a general JavaScript problem or how to develop web applications, please google it or read section 2 of the user manual for the overview of these domains.

  \n
\n
• \n

  If you want to know what the changes between two versions are look at the file named ChangeLog in your distribution.

  \n
\n
• \n

  If you need to debug your application, Google Chrome, Firebug (debugging plug-in for Firefox) and Internet Explorer 9 all provide debugging functionality similar to that you would find in a standard IDE. Double check if you have a run-time error in the debugging console before posting.

  \n
\n
• \n

  If you cannot work out how to evaluate mxGraph, read this post.

  \n
\n

If these areas do not solve your problem please provide these pieces of information when posting.

\n
• \n

  If the problem is a run time error in your browser debugger provide the stack trace ( the list of methods calls up to that execution point ) as well as the exact text of the error. If you can provide additional information about the variables states at the time of the run time error, that is useful.

  \n
\n
• \n

  Always post which version of mxGraph you are using.

  \n
\n
• \n

  Please always use the code formatting tools ( the 'preformatted text' button about the edit box ) when displaying code and try to ensure the indenting looks correct on the preview.

  \n
\n
• \n

  Please don't write 'URGENT' or "HELP!!!", the forum bot will become upset.

  \n
\n
• \n

  Do not double post. It isn't fair on other users and just creates work for us deleting them.

  \n
\n
• \n

  Please don't post huge amounts of code, focus on the important areas. A link to a small working example makes your chances of getting a bug looked at much better.

  \n
\n
• \n

  Do not write "bump" on threads, they will be deleted. If you have further information to post having analysed the problem further, that is allowed.

  \n
\n
• \n

  If you have a commercial support contract, you have a specific support route described in your purchase email. You are welcome to post on the forums if you prefer.

  \n
\n