<?xml version="1.0" encoding="UTF-8"?>
<tickets type="array">
<ticket>
  <assigned-to-id>aDT-g05xer3lYaabIlDkbG</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-07-13T00:05:17Z</created-on>
  <description>This is to Map out the support and Dependencies that OpenRPG works with. And to establish proper testing procedures before a release can be made. If you have additional tests or tests you would like to modify post them here. Once all is in agreement we will start utilizing these methods to verify any given release meets quality standards before it gets pushed to the release tree and out to end users.

|_. Legend |{background:#ffaa99}. Failed |{background:#ffdd99}. Untested |{background:#ddff99}. Passed |

|_. System |_. py2.5.x, wx2.7.2 |_. py2.5.x, wx2.8.(1 to 7) |_. py2.5.x, wx2.8.8+ |_. py2.6.2, wx2.8.10+ |
|_. winXP |{background:#ffdd99}. Untested |{background:#ffdd99}. Untested |{background:#ffdd99}. Untested |{background:#ffdd99}. Untested |
|_. msVista |{background:#ffdd99}. Untested |{background:#ffdd99}. Untested |{background:#ffdd99}. Untested |{background:#ffdd99}. Untested |
|_. Mac |{background:#ffdd99}. Untested |{background:#ffdd99}. Untested |{background:#ffdd99}. Untested |{background:#ffdd99}. Untested |
|_. Debian |{background:#ffdd99}. Untested |{background:#ffdd99}. Untested |{background:#ffdd99}. Untested |{background:#ffdd99}. Untested |
|_. *nix |{background:#ffdd99}. Untested |{background:#ffdd99}. Untested |{background:#ffdd99}. Untested |{background:#ffdd99}. Untested |</description>
  <from-support type="integer">0</from-support>
  <id type="integer">434493</id>
  <importance type="integer">47</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>aDT-g05xer3lYaabIlDkbG</notification-list>
  <number type="integer">47</number>
  <priority type="integer">3</priority>
  <reporter-id>aDT-g05xer3lYaabIlDkbG</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Testing] Platform and Dependency</summary>
  <updated-at type="datetime">2010-08-24T10:55:17Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></assigned-to>
  <reporter><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>aDT-g05xer3lYaabIlDkbG</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-08-01T00:53:20Z</created-on>
  <description>OpenRPG currently uses 2 different XML parsers, 1 for general and 1 for the plugindb. The general parser is a custom implementation of the xml.dom.minidom that comes with python since at the time it was not included. I propose we convert all internal use to xml.etree.cElementTree and have the old code raise a DepreciationWarning, This will let people who are using the old code still use it but it will print a warning to the console that it will be removed in a future version.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">458573</id>
  <importance type="integer">63</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>aDT-g05xer3lYaabIlDkbG</notification-list>
  <number type="integer">63</number>
  <priority type="integer">1</priority>
  <reporter-id>aDT-g05xer3lYaabIlDkbG</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Feature] Depreciate orpg.orpg_xml &amp; the custom minidom</summary>
  <updated-at type="datetime">2010-08-24T11:05:38Z</updated-at>
  <working-hours type="float">30.0</working-hours>
  <working-hour type="float" warning="deprecated">30.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></assigned-to>
  <reporter><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>aDT-g05xer3lYaabIlDkbG</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-08-08T21:39:01Z</created-on>
  <description>I would like to get rid of this mess of code and break it out into a package where each window or related windows have thier own file. This will be a major cleanup and help in bug fixing in the future</description>
  <from-support type="integer">0</from-support>
  <id type="integer">467232</id>
  <importance type="integer">79</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>aDT-g05xer3lYaabIlDkbG</notification-list>
  <number type="integer">79</number>
  <priority type="integer">1</priority>
  <reporter-id>aDT-g05xer3lYaabIlDkbG</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Feature] Depreciate orpg_windows</summary>
  <updated-at type="datetime">2010-08-24T11:09:43Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></assigned-to>
  <reporter><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>aDT-g05xer3lYaabIlDkbG</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-08-08T21:53:23Z</created-on>
  <description>this modules only reason for existing is to work around some bugs in wxPython, it should be depreciated when we eliminate wx2.7 from out supported versions</description>
  <from-support type="integer">0</from-support>
  <id type="integer">467240</id>
  <importance type="integer">81</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>aDT-g05xer3lYaabIlDkbG</notification-list>
  <number type="integer">81</number>
  <priority type="integer">1</priority>
  <reporter-id>aDT-g05xer3lYaabIlDkbG</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Feature] Depreciate the orpg_wx module</summary>
  <updated-at type="datetime">2010-08-24T11:09:44Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></assigned-to>
  <reporter><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-11-06T04:27:12Z</created-on>
  <description>The code for booting someone from a room is buggy in the openrpg_dev default branch.  Since I've never messed with that stuff I assume it might be in the released 1.8.0.3 too.  It seems partially due to the change over from minidom.  In def boot_player in mplay_client.py  the element passed to send() is in xml node form not a string.  However even after fixing this I still couldn't boot a dead player from the room so there's something else going on.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">605429</id>
  <importance type="integer">104</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">104</number>
  <priority type="integer">1</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Can't boot player from room</summary>
  <updated-at type="datetime">2010-08-24T12:05:24Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-11-15T19:22:43Z</created-on>
  <description>Messages seem to be malformed from the openrpg_dev to older (ie all) released OpenRPG clients.  Not sure how many are effected but I know the chat message is bust (have a fix), the map load message is bust, and I suspect something similar is behind the existing bug that openrpg_dev can't boot people and a new one I noticed that when you change name in openrpg-dev it doesn't display the name change in your player list (although oddly other users do see the name change).

OK so maybe these are not related but they seem message issues.  (message system probably should be a ticket component btw)

In the case I have fixed, the chat message the bug was part of the transfer to ElementTree.  The XML was &quot;improved&quot; so that it fails for older clients.

the code fix:
http://trac-hg.assembla.com/openrpg_dev/changeset/477%3Aa50ad92e81b6

The old code was wrongly issuing &quot;correct&quot; XML and inserting the chat element inside the msg element as a child instead of adding it afterwards as a sybling.  This resulted in older clients BUT NOT openrpg_dev ITSELF chocking on the message.  You need to run with an older client to see that bug and some of the others perhaps (the failed map message probably). 1.8.0.X will do as &quot;older&quot;.  Anything prior to the Element Tree code.

I think i one day noticed that the data sent to plugins is similarly screwed up as XML but again backwards compatibility issues make it hard to fix.  i'll try to pin down some better bug repro / descriptions.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">632687</id>
  <importance type="integer">109</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">109</number>
  <priority type="integer">1</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Various problems with mplay_client.py messages?</summary>
  <updated-at type="datetime">2010-08-24T12:11:19Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>dYtGZ-kC4r3BfFab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">5</component-id>
  <created-on type="datetime">2009-11-20T03:33:48Z</created-on>
  <description>Including the list that saves the auto-started plugins.
Already fixed in this changeset:
http://trac-hg.assembla.com/openrpg_dev/changeset/489%3A0549a94f6731

Bug was caused by the change-over to ElementTree again.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">652431</id>
  <importance type="integer">113</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">113</number>
  <priority type="integer">1</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Plugin database can't retrieve lists or dictionaries</summary>
  <updated-at type="datetime">2010-08-24T12:15:34Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-11-29T06:28:48Z</created-on>
  <description>This is already fixed but I am concerned about the way I fixed it so I am logging a ticket.

Here's the fix:
http://trac-hg.assembla.com/openrpg_dev/changeset/506%3Aafeaa94e4efc

The help was broken due to the self.settings having been altered (probably around the time the ElementTree code was added) to simply settings which is now the global name of the settings object.  Reverting to the 1.8.0 code here.

The other bug prevented any edit of the settings.  I traced it to the fact that suddenly the cell values returned by the Grid were unicode strings.  It turns out that if you search a ElementTree with a tag name in unicode it will always fail due to a line in the Path object's __init__ that checks for type str not unicode.  Actually it checks that the string is the same type as &quot;&quot;.

So why did the Grid suddenly start reporting its cell contents as unicode strings?  I have no idea.  The fix simply casts the value it gets from the cell into a string before doing the ElementTree tag search.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">702811</id>
  <importance type="integer">115</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">115</number>
  <priority type="integer">1</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Settings dialog messed up (help and editing fail)</summary>
  <updated-at type="datetime">2010-08-24T12:22:23Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-11-29T17:34:46Z</created-on>
  <description>This is a bug in the active current release out there, 1.8.0

http://www.rpgobjects.com/forum/index.php?action=vthread&amp;forum=1&amp;topic=722&amp;page=0#msg9361

As the title says but the reproduction is so far only on Linux.  Select a background image and then try zooming in.  Apparently the display is screwed up.  this would prevent people who create custom background images playing on Linux machines with 1.8.0  I'm surprised we have not heard about this bug before now.  </description>
  <from-support type="integer">0</from-support>
  <id type="integer">703313</id>
  <importance type="integer">116</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">116</number>
  <priority type="integer">1</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>background image and zoom don't work in 1.8.0</summary>
  <updated-at type="datetime">2010-08-24T12:22:31Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>aDT-g05xer3lYaabIlDkbG</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-04-02T03:53:24Z</created-on>
  <description>refers to recently altered openrpg_dev std die roller

[q1d20+4] used to look like rg. [11+4] = (15) but now the add is missing and it looks like eg. [11] = (15) which looks very odd.
The quiet roll is also produced as part of the normal roll display.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1202425</id>
  <importance type="integer">124</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ,aDT-g05xer3lYaabIlDkbG</notification-list>
  <number type="integer">124</number>
  <priority type="integer">1</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>New die roller's quiet roll misses out adds</summary>
  <updated-at type="datetime">2010-08-24T14:12:03Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-06-29T02:44:52Z</created-on>
  <description>Another ticket with no clear component.

Many features have no documentation and often what there is is years old and possibly plain wrong or point at web sites that are permanently down now.  Several broad categories need attention:

(1) the user wiki
(2) the example nodes and (lack of) example map / minis that come with a fresh install
(3) developer wiki
(4) something like a tip of the day and/or F1 help system would be nice

This is a big rambling vague low priority task but it needs doing.  The 2nd most frequent query I get (after installer problems) is &quot;How do I get started?&quot;  </description>
  <from-support type="integer">0</from-support>
  <id type="integer">420105</id>
  <importance type="integer">32</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">32</number>
  <priority type="integer">2</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Documentation] Improve and update documentation / help</summary>
  <updated-at type="datetime">2010-08-24T10:49:36Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>aDT-g05xer3lYaabIlDkbG</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-08-08T21:44:40Z</created-on>
  <description>ButtonPanel.py (Depreciate this module)
FlatNotebook.py (I think this is included in all versions of wx2.8 now)
metamenus.py (Depreciate this module)
NotebookCtrl.py (Depreciate this module)
PyAUI.py (Depreciate this module)

And any future 3rd party packages we decide to use should be added there so it is clear they were not originally written by us. It will also make it easier to depreciate them in the future if we decide to change or they are included in python or wx by default some time  later</description>
  <from-support type="integer">0</from-support>
  <id type="integer">467237</id>
  <importance type="integer">80</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>aDT-g05xer3lYaabIlDkbG</notification-list>
  <number type="integer">80</number>
  <priority type="integer">2</priority>
  <reporter-id>aDT-g05xer3lYaabIlDkbG</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Feature] Move all 3rd party code to the external package</summary>
  <updated-at type="datetime">2010-08-24T11:09:44Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></assigned-to>
  <reporter><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>aDT-g05xer3lYaabIlDkbG</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-08-08T22:07:02Z</created-on>
  <description>Any class that can actually be made into a singleton in it's own right should be removed from this container class and just imported where needed.

settings *
Validate *
orpgLog *
dir_struct * 

* These are already singletons but still exist in the open_rpg container for now</description>
  <from-support type="integer">0</from-support>
  <id type="integer">467250</id>
  <importance type="integer">82</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>aDT-g05xer3lYaabIlDkbG</notification-list>
  <number type="integer">82</number>
  <priority type="integer">2</priority>
  <reporter-id>aDT-g05xer3lYaabIlDkbG</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Feature] Move any class that can be made a singleton out of the open_rpg singleton container</summary>
  <updated-at type="datetime">2010-08-24T11:09:44Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></assigned-to>
  <reporter><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-04-25T04:16:09Z</created-on>
  <description>Looks like some of the recent refactoring messed up whispering.  whispering doesn't open new chat tabs when it should and the /gm command is broken.  I also wonder at how the feature is intended to work, especially with multiple GMs and so on. A to GM message with 2 GMs to receive the whisper seems to have been buggy even in earlier versions.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1341829</id>
  <importance type="integer">126</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">126</number>
  <priority type="integer">2</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Whisper feature broken in developer version</summary>
  <updated-at type="datetime">2010-08-24T14:43:14Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-07-12T03:49:17Z</created-on>
  <description>http://z9.invisionfree.com/Mayhem_Gaming/index.php?showtopic=2933&amp;st=0&amp;#entry2983523

With large maps lines sometimes disappear.  I am thinking it might be a threading issue between local changes and other user changes to the whiteboard.  Might be solved with a lock on the whiteboard layer's lines.append().

Hard to reproduce the bug but I have seen it repeatedly in real play.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">434116</id>
  <importance type="integer">45</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">45</number>
  <priority type="integer">3</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Bug] Disappearing lines in whiteboard</summary>
  <updated-at type="datetime">2010-08-24T10:55:08Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-07-21T02:34:57Z</created-on>
  <description>There is a minor issue with the image cache that people will probably not even notice.  

&lt;pre&gt;&lt;code&gt;
  File &quot;/home/sirebral/Programs/Traipse/System/orpg/mapper/images.py&quot;, line 142, in __loadCacheThread
  File &quot;/home/sirebral/Programs/Traipse/System/orpg/mapper/images.py&quot;, line 142, in __loadCacheThread
    open_rpg.get_component('log').log(&quot;Adding Image to Queue from Cache: &quot; + str(self.__cache[path]), ORPG_DEBUG)
KeyError: 'http://www.geocities.com/danjnm_2000/goblin1.gif'
    open_rpg.get_component('log').log(&quot;Adding Image to Queue from Cache: &quot; + str(self.__cache[path]), ORPG_DEBUG)
KeyError: 'http://www.geocities.com/danjnm_2000/goblin1.gif'
&lt;/code&gt;&lt;/pre&gt;

</description>
  <from-support type="integer">0</from-support>
  <id type="integer">444155</id>
  <importance type="integer">55</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>c2Q8uOewur3BXsab7jnrAJ</notification-list>
  <number type="integer">55</number>
  <priority type="integer">3</priority>
  <reporter-id>c2Q8uOewur3BXsab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Bug] Minor issue with Image cache</summary>
  <updated-at type="datetime">2010-08-24T10:59:17Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>c2Q8uOewur3BXsab7jnrAJ</id><login>sirebral</login><login_name warning="deprecated">sirebral</login_name><name>sirebral</name><website>http://www.knowledgearcana.com</website></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-08-01T22:16:16Z</created-on>
  <description>Map-&gt;Fog: When user role is changed between GM and Player/Lurker (or Player/Lurker to GM) fog is incorrectly displayed until next map refresh</description>
  <from-support type="integer">0</from-support>
  <id type="integer">458937</id>
  <importance type="integer">67</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>aDT-g05xer3lYaabIlDkbG</notification-list>
  <number type="integer">67</number>
  <priority type="integer">3</priority>
  <reporter-id>aDT-g05xer3lYaabIlDkbG</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[BUG] When user role is changed fog is incorrectly displayed</summary>
  <updated-at type="datetime">2010-08-24T11:05:47Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">1</component-id>
  <created-on type="datetime">2009-08-01T22:17:33Z</created-on>
  <description>Gametree: Template-&gt;Nodes-&gt;Create New Resource tool has gear icon&#8230; new resource node has book icon. Should be unified icon.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">458939</id>
  <importance type="integer">69</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>aDT-g05xer3lYaabIlDkbG</notification-list>
  <number type="integer">69</number>
  <priority type="integer">3</priority>
  <reporter-id>aDT-g05xer3lYaabIlDkbG</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[BUG] Icon inconsitency with New Resource Node</summary>
  <updated-at type="datetime">2010-08-24T11:05:47Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>dYtGZ-kC4r3BfFab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-09-07T03:37:47Z</created-on>
  <description>Partial implementation of this ticket: https://www.assembla.com/spaces/openrpg/tickets/70-%5BFeature%5D-Visibility-and-Data-Type--new-node-attributes

I'm going to check this in and see what you all think.  I imagine there will still be some bugs in it but hopefully not too obvious or many.  Sadly my problems with getting unit tests to work mean there are no tests for this feature.  Most of the code overrides wx.TreeCtrl functions to catch events and fill out and keep up to date three maps which help translate from a tree item path (or leaf name, or namespace name) to a node handler.  

(1) referenceable nodes are marked as normal in black.  unreferenceable nodes are in red text.
(2) referenceable status is taken from the xml or defaults to true, however if a validation check fails it is set to false and saved that way in the xml.
(3) validation fails for illegal names, for nodes with identical full path names and for identical names within a namespace
(4) you can toggle referenceable status from the context menu (fails if validation fails)
(5) namespace nodes are marked in bold text.
(6) namespace status is taken from the xml or defaults to false. you cannot nest a namespace (hmm, don't think I check for this yet)
(7) you can toggle namespace status from context menu.  this may cause child nodes to become unreferenceable
(8) changing the name of a node may cause it to become unreferenceable, as can moving it or changing the namespace it is inside.
(9) unreferenced nodes will not be translated by !@foo::bar@! full path references in chat or in text of nodes
(10) nodes in namespaces can be referenced with only !@namespace_name::name_of_the_node@! (ie just two parts of the full path)
(11) leaf nodes that have a name that is unique can be referenced with simply !@name@!</description>
  <from-support type="integer">0</from-support>
  <id type="integer">505302</id>
  <importance type="integer">92</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">92</number>
  <priority type="integer">3</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Feature] New node/path reference system</summary>
  <updated-at type="datetime">2010-08-24T11:25:55Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-10-06T04:38:53Z</created-on>
  <description>node handlers that have a &quot;use&quot; dialog that displays text that may include a reference (ie text, grid rows and lists) should translate the reference before displaying it and if that text is normally editable through the &quot;use&quot; dialog (text and grid row's 2nd column) then it should be read-only.  

(If the text that is read only is a die roller it might be nice to clean it up even further, eventually)

The &quot;use&quot; dialog is not the place to show a lot of programmer crap like &quot;((!@abilities::stength@!+!@temp_ability_adds::strength@!-10)/2)&quot; and as such should not be editable either.  Instead at the least show something like &quot;((16+4-10)/2)&quot; and at best just &quot;5&quot;, but with no edit except through the design dialog.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">546935</id>
  <importance type="integer">101</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">101</number>
  <priority type="integer">3</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>&quot;use&quot; dialogs should translate references before displaying them as read-only</summary>
  <updated-at type="datetime">2010-08-24T11:44:06Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>dYtGZ-kC4r3BfFab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-11-08T23:31:13Z</created-on>
  <description>I added a option to make the grid calculate a total across each row.  ie the second column of the grid is the total of all cells to the right for that row.  (any value the 2nd column used to have is ignored).  The first row doesn't behave that way so it can be a header row.  This should be working now.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">611621</id>
  <importance type="integer">105</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">105</number>
  <priority type="integer">3</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Limited spread sheet ability for grid</summary>
  <updated-at type="datetime">2010-08-24T12:06:46Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-11-08T23:42:04Z</created-on>
  <description>I have removed the options for the macro on the text handler and alias lib as now all text is a &quot;macro&quot; in that it is all handled one line (separated by \n) at a time and if any line begins with a forward slash it is assumed to be a /command and handled.  I'm not sure what to do with the special &quot;macro&quot; handler that now seems obsolete and just confusing.  (Frankly the behaviour was a little buggy anyway eg the text node didn't &quot;macro&quot; id you selected &quot;send to chat&quot; but did if you used &quot;use&quot; and then hit a send button).

Each time a /command is encountered it is sent a context object which is able to tell it about the other lines of multi-line text being sent.  At least one /command, /input, edits these lines as the parser is going.  So the ordering is quite important now and in theory at least, the way it works is that each time you grab a new piece of text from a reference or from being typed in, each line in turn is parsed for /commands or references and dealt with before the next line.  /commands are now fully part of the reference system therefore.  This is unlike the die rollers and filters which are still run afterwards over the entire text.  The \n is not replaced by HTML compliantt &lt;br /&gt; until after the filters run (so you can test for end of line / begin of line int heir regex).

Currently /commands that send to chat (including the /me command) are still shooting off out of turn as they always did.  This will take a bit of work to fix for the non ParsePost printing.  For ParsePost printing simply add the new text to the context's list of lines about to be / being parsed.

At any rate for this ticket the feature is: /commands work from anywhere that sends chat.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">611657</id>
  <importance type="integer">106</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">106</number>
  <priority type="integer">3</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>All text is now &quot;macro&quot; text (better multi-line support)</summary>
  <updated-at type="datetime">2010-08-24T12:06:46Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-11-11T06:27:55Z</created-on>
  <description>This is presumably just in the default branch of openrpg_dev but as it is an Ubuntu only bug I can't just fix it, hence the ticket.

http://www.rpgobjects.com/forum/index.php?action=vthread&amp;forum=1&amp;topic=671&amp;page=0#msg7281

Tried &quot;/version&quot; command. Got &quot;Sorry I don't know what /versio is!&quot;. Note the lack of &quot;n&quot; there.

sirebral has also reported the bug on Ubuntu.  I am wondering if the expandoTextCtrl behaves differently on Ubuntu.  Perhaps it does NOT add the newline which submits the text to the value submitted, as Windows Vista does.

</description>
  <from-support type="integer">0</from-support>
  <id type="integer">619563</id>
  <importance type="integer">107</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">107</number>
  <priority type="integer">3</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Ubuntu seeing last line of chat expando text control disappear </summary>
  <updated-at type="datetime">2010-08-24T12:08:41Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>aDT-g05xer3lYaabIlDkbG</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2010-04-08T17:47:21Z</created-on>
  <description>Refactor the chat system to seperate commands into individual files, message handling into it's own package and the chat interface. Decoupling these systems will make it easier to maintain and enhance over time.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1233157</id>
  <importance type="integer">125</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>aDT-g05xer3lYaabIlDkbG</notification-list>
  <number type="integer">125</number>
  <priority type="integer">3</priority>
  <reporter-id>aDT-g05xer3lYaabIlDkbG</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Feature] Chat Refactor</summary>
  <updated-at type="datetime">2010-08-24T14:19:59Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></assigned-to>
  <reporter><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-04-27T03:26:32Z</created-on>
  <description>Text View (of chat) search feature doesn't highlight the found text or scroll to where it is properly.  it scrolls to about a line above the line of the found text.  TextCtrl.SetSelection(from, to) doesn't seem to work for some reason -- hasn't worked going back to 1.7.1 as far as i can see.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1349127</id>
  <importance type="integer">127</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">127</number>
  <priority type="integer">3</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Text View (of chat) search feature doesn't highlight</summary>
  <updated-at type="datetime">2010-08-24T14:44:59Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>aDT-g05xer3lYaabIlDkbG</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-05-06T02:00:43Z</created-on>
  <description>Not sure if I have this down elsewhere but just to say again that the server browse dialog and the alias lib dialog don't display correctly currently (in the dev version).

Server Browse Dlg:
Sometimes is initially displayed locked to the map layout instead of floating.  As a result its often impossible or hard to use initiially.
Sometimes appears without an X for exiting in top right (this isn't a big deal).
Sometimes the list of servers is blank initially (but is fine upon a refresh so seems more a display issue than a connection issue).

Alias Lib:
Sometimes is initially displayed locked to the map layout instead of floating.  As a result its often impossible or hard to use initiially.
The vertical divider is initially displayed too far to the left so the dialog is hard to use at first.
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1390943</id>
  <importance type="integer">130</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ,aDT-g05xer3lYaabIlDkbG</notification-list>
  <number type="integer">130</number>
  <priority type="integer">3</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>ugly Server Browse &amp; AliasLib dialogs</summary>
  <updated-at type="datetime">2010-08-24T14:54:30Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2009-11-16T14:58:06Z</created-on>
  <description>this is for the openrpg_dev default branch.
As title says change your name and it doesn't update in the player list view.  Other users in same room see the change.  Possibly a change to ElementTree issue.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">635113</id>
  <importance type="integer">110</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8907</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">110</number>
  <priority type="integer">4</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>upon /name change player list doesn't update</summary>
  <updated-at type="datetime">2010-08-24T12:11:54Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>aDT-g05xer3lYaabIlDkbG</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-09-06T22:57:27Z</created-on>
  <description>reconfigure openrpg to support stanalone install for windows and OSX

The basics would be we'd need to split out...
1) Resource dir (all the non-py files, images, sounds, etc)
2) Myfile dir (user settings, save-load point for maps, logs, etc)
3) Plugins dir --- this is the only thing that would be a potential problem with a standalone app, while using a python interpereter you can dynamically load user plugins as long as they don't import anything :P (remember, paths are all screwy thus the imports are too)</description>
  <from-support type="integer">0</from-support>
  <id type="integer">505214</id>
  <importance type="integer">90</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">101265</milestone-id>
  <notification-list>aDT-g05xer3lYaabIlDkbG</notification-list>
  <number type="integer">90</number>
  <priority type="integer">3</priority>
  <reporter-id>aDT-g05xer3lYaabIlDkbG</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Feature] Standalone install</summary>
  <updated-at type="datetime">2010-08-24T11:25:53Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></assigned-to>
  <reporter><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>dYtGZ-kC4r3BfFab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-01-04T21:24:41Z</created-on>
  <description>My group and I were loading a map to start our first session with OpenRpg.  Everything worked fine until our GM moved one of his miniatures and the entire screen went blank.  All of the grid and map was gone except for the miniatures.  We've tried for other people to load the map, and as soon as a miniature is added/moved/removed, the entire screen goes blank.</description>
  <from-support type="integer">1</from-support>
  <id type="integer">799387</id>
  <importance type="integer">118</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">101265</milestone-id>
  <notification-list>duPWu4-xyr3OA7eJe5afGb,dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">118</number>
  <priority type="integer">3</priority>
  <reporter-id>duPWu4-xyr3OA7eJe5afGb</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Map loading trouble.</summary>
  <updated-at type="datetime">2010-08-24T12:45:09Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></assigned-to>
  <reporter><id>duPWu4-xyr3OA7eJe5afGb</id><login>Mosaicbass13</login><login_name warning="deprecated">Mosaicbass13</login_name><name>Mosaicbass13</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-04-28T02:41:34Z</created-on>
  <description>Since the change of the style of these two dialogs they initially display in such a way that you cannot see most of the data on them.  In both cases they start off attached to the map which makes them smaller vertically than they need to be if the map is small vertically.  The alias lib is also displayed with the vertical splitter to the extreme left hand side so that the list of alias names cannot be seen initially.

It's very annoying with the server browser as you use that dialog so often.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1354641</id>
  <importance type="integer">128</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">128</number>
  <priority type="integer">1</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Alias Lib and Browse Server dialogs display badly</summary>
  <updated-at type="datetime">2010-08-24T14:46:21Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>dYtGZ-kC4r3BfFab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-07-11T14:20:07Z</created-on>
  <description>New feature.  Currently OpenRPG has no concept of a character - something which all its competitors have.  A character sheet is currently a container node like any other.  It is not linked to similarly named minis on the map which means there's no context data available when you right-click or double-click on a mini.  It is not linked to similarly named aliases in the alias lib which means there's no ability to sense that you are in the context of a certain PC or NPC as you type in their &quot;voice&quot; (this could be used to reference nodes by shorter pathways, eg type &quot;Search&quot; and OpenRPG looks up the node 'Search&quot; within that character sheet matching the selected alias).  Similarly minis don't link to the alias so you can't do things like select the right alias when you select the mini, or scroll the map to show the mini when you select the corresponding alias. Sharing character data is only through sending the node to all other players and even that does not allow editing of the node by multiple users (eg both player and DM altering HP amount).  Operations on nodes within the context of a character sheet (eg referencing a PC's strength when calculating a damage roll) have to specify a full path to the node instead of a local path, which makes it hard to copy a character sheet and still have it work.  These are examples; many features are possible once you have the concept of a character well defined.

Many users also identify their user/player id in the player list with their (one) character.  Obviously that method doesn't allow for multiple PCs or eg a PC and a companion or a DM playing many NPCs but since a lot of people use it that is another place to link.  We might want to have two settings, one where the player is assumed to have one character only (no alias lib, your player name is assumed to be your character name) and one where the player has a different OOC voice than any of several characters that they run.

In the multiple PC case I have a lot of this stuff working in a plugin but the method is informal.  Basically the plugin looks for matches between the names of the minis, alias lib voices and container nodes in the gametree and assumes that anything that matches up is a character.  It takes a guess.  Also the three areas remain separate; if you edit the name in one place it doesn't edit it elsewhere and would in fact break the linkage.  Because the match is purely based on the names you can't eg run ten minis called bugbear1 thru bugbear10 and have them all map to a single character sheet (apart from HP).

Like I say, all the competitors have something like this and have it as a central part of the program so I'm putting this as priority 2.  
Discussion of this feature at Mahyem:
http://z9.invisionfree.com/Mayhem_Gaming/index.php?showtopic=2932</description>
  <from-support type="integer">0</from-support>
  <id type="integer">433892</id>
  <importance type="integer">40</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">40</number>
  <priority type="integer">2</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Feature] Create the concept of a character in OpenRPG</summary>
  <updated-at type="datetime">2010-08-24T10:55:04Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">7</component-id>
  <created-on type="datetime">2009-06-26T05:41:41Z</created-on>
  <description>A user wants a die roller that fits this description. 

3k2 = 3d10.takeHighest(2).open(10)
7k5 = 7d10.takeHighest(5).open(10)

It would be easy to add, by creating a new die type. Instead of [1d4] we make a function that takes advantage of the k, then apply the same features as takeHighest and open.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">418139</id>
  <importance type="integer">28</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>c2Q8uOewur3BXsab7jnrAJ</notification-list>
  <number type="integer">28</number>
  <priority type="integer">3</priority>
  <reporter-id>c2Q8uOewur3BXsab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Feature] L5R and &amp;th Sea die roller.</summary>
  <updated-at type="datetime">2010-08-24T10:48:50Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>c2Q8uOewur3BXsab7jnrAJ</id><login>sirebral</login><login_name warning="deprecated">sirebral</login_name><name>sirebral</name><website>http://www.knowledgearcana.com</website></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">1</component-id>
  <created-on type="datetime">2009-07-14T03:01:16Z</created-on>
  <description>Part of the ticket about a character concept (https://www.assembla.com/spaces/openrpg/tickets/40-Create-the-concept-of-a-character-in-OpenRPG) involves having shared data, so this is a sort of prerequisite.  

One way to implement shared data is to copy the data to the other players and then have a system to forward local edits to the other users nodes. That seems like a problem if one of the users is seen as &quot;owning&quot; the data and is updating it between sessions.  Another way to share the data would be to store it only on one users gametree and have all other users request that data when they use it.  The problem with that would be that if that user exits then their data goes too which would make it hard to continue a session they left early NPC-ing their character.  Perhaps there is a middle route.  I'd like to see how competitor systems handle this sort of stuff.  </description>
  <from-support type="integer">0</from-support>
  <id type="integer">436185</id>
  <importance type="integer">48</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">48</number>
  <priority type="integer">3</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Feature] Create the concept of shared data in OpenRPG</summary>
  <updated-at type="datetime">2010-08-24T10:56:01Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-08-01T22:48:07Z</created-on>
  <description>As a prerequisite to this ticket: https://www.assembla.com/spaces/openrpg/tickets/70-%5BFeature%5D-Visibility-and-Data-Type--new-node-attributes

To get any sort of validation or shared ownership stuff going we need to react any time a node is edited or has its name changed (which is a sort of edit even if it just changed location within the tree).  Python being what it is there's a whole lot of ways of going about editing a node beyond the obvious.  What we need is a promise by developers that these functions will get called after any kind of edit so that we can make guarantees about the quality and validity of the data no matter how it is changed.

Ideally need some way to avoid infinite looping of these triggers.

</description>
  <from-support type="integer">0</from-support>
  <id type="integer">458946</id>
  <importance type="integer">71</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">71</number>
  <priority type="integer">3</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Feature] OnFinishEdit, OnNameChange: functions for nodes</summary>
  <updated-at type="datetime">2010-08-24T11:05:47Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-08-06T07:14:56Z</created-on>
  <description>I want to clean up the code and make it less memory resident.  While working on the Update Manager for Traipse (almost done, I think you will like it too), I noticed that in some portions of the code entire modules are imported when only one piece of the module is used.  For example, import os and os.sep.  It would be less memory resident if we from os import sep, then called sep instead of os.sep.  

A task like this would be extensive and it should be done file by file, but I want to accomplish this so the code is cleaner.  Of course after this Update Manager is done I am going to be sick of looking at code for awhile. O_o</description>
  <from-support type="integer">0</from-support>
  <id type="integer">463853</id>
  <importance type="integer">73</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>c2Q8uOewur3BXsab7jnrAJ</notification-list>
  <number type="integer">73</number>
  <priority type="integer">3</priority>
  <reporter-id>c2Q8uOewur3BXsab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Feature] Code Clean-Up</summary>
  <updated-at type="datetime">2010-08-24T11:08:06Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>c2Q8uOewur3BXsab7jnrAJ</id><login>sirebral</login><login_name warning="deprecated">sirebral</login_name><name>sirebral</name><website>http://www.knowledgearcana.com</website></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-08-09T06:28:28Z</created-on>
  <description>The sound bar uses wx.media.MediaCtrl to play MP3's and such type files. This seems to be bugged when it in embedded in a wx.aui.ToolPanel and that panel is undocked on *nix platforms.

I have a bug report in with the wxPython team so when it is fixed I'll update this ticket</description>
  <from-support type="integer">0</from-support>
  <id type="integer">467342</id>
  <importance type="integer">83</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>aDT-g05xer3lYaabIlDkbG</notification-list>
  <number type="integer">83</number>
  <priority type="integer">3</priority>
  <reporter-id>aDT-g05xer3lYaabIlDkbG</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Bug] (*nix) OpenRPG crash when SoundToolbar is undocked</summary>
  <updated-at type="datetime">2010-08-24T11:09:46Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>bjbTp6ETCr3RMjeJe5aVNr</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-09-06T22:59:14Z</created-on>
  <description>Redesign the map to be faster and more extensible in the future. This may or may not be backwards compatible</description>
  <from-support type="integer">0</from-support>
  <id type="integer">505216</id>
  <importance type="integer">91</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>aDT-g05xer3lYaabIlDkbG,bjbTp6ETCr3RMjeJe5aVNr</notification-list>
  <number type="integer">91</number>
  <priority type="integer">3</priority>
  <reporter-id>aDT-g05xer3lYaabIlDkbG</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Feature] Map Update</summary>
  <updated-at type="datetime">2010-08-24T11:25:53Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>bjbTp6ETCr3RMjeJe5aVNr</id><login>snowdog</login><login_name warning="deprecated">snowdog</login_name><name>snowdog</name></assigned-to>
  <reporter><id>aDT-g05xer3lYaabIlDkbG</id><login>Digitalxero</login><login_name warning="deprecated">Digitalxero</login_name><name>Digitalxero</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-11-16T17:07:47Z</created-on>
  <description>OpenRPG needs some way to avoid accidentally losing a lot of data while editing a node that has a lot of data in it.  For example accidentally deleting a column from a big grid.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">635587</id>
  <importance type="integer">111</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">111</number>
  <priority type="integer">3</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Cancel or undo feature for larger node edits</summary>
  <updated-at type="datetime">2010-08-24T12:12:00Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">7</component-id>
  <created-on type="datetime">2010-03-22T13:44:59Z</created-on>
  <description>This isn't really a problem I'm having but as I don't see any other way to get a hold of all of you I apologize for resorting to a ticket.
I have been working on some tutorials with Ebral and a couple of my other friends assisting in their writing. Right now I have most of them up on my site and some in progress using wave. I would like to offer them up to be placed on your wiki so that others may get some use out of them. If you would like to discuss this more I invite you to contact me and be an active participant in their creation. Your expertise and insight as developers of the program would be greatly welcomed.
[[url:http://www.example.com|http://swrpgrc.com/index.php?option=com_content&amp;view=category&amp;id=9&amp;Itemid=23ExampleName]] Is where the tutorials are currently published.
</description>
  <from-support type="integer">1</from-support>
  <id type="integer">1119549</id>
  <importance type="integer">123</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>bk41IAy1Or3RJLeJe5afGb</notification-list>
  <number type="integer">123</number>
  <priority type="integer">3</priority>
  <reporter-id>bk41IAy1Or3RJLeJe5afGb</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Tutorials</summary>
  <updated-at type="datetime">2010-08-24T13:58:51Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bk41IAy1Or3RJLeJe5afGb</id><login>Alicia86</login><login_name warning="deprecated">Alicia86</login_name><name>Alicia86</name><website>http://swrpgrc.com</website></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">5</component-id>
  <created-on type="datetime">2010-08-28T22:57:15Z</created-on>
  <description>Umm, not sure how, but for some reason, the Server Browser is not opening when I click on it. Not even CTRL+B will open it.

Not certain if this is a bug or just me being downright retarded, but I have seen no discussion on this matter, and there is no option to reset OpenRPG to it's installed defaults.

EDIT: The window itself flashes for a second, and then goes back to normal. No browser in sight. I have updated and possibly down-dated to each version I could find. Also, here's my system info:

OpenRPG System Info 09-28-10
OpenRPG Version: 1.8.0
OpenRPG Build: 090712-00
Python: 2.6.2 (r262:71605, Apr 14 2009, 22:40:02) [MSC v.1500 32 bit (Intel)]
wxPython Version: 2.8.10.1
Platform: Microsoft-Windows-32bit-WindowsPE

</description>
  <from-support type="integer">1</from-support>
  <id type="integer">2016457</id>
  <importance type="integer">131</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>a9LVVGSVCr375QeJe5cbCb</notification-list>
  <number type="integer">131</number>
  <priority type="integer">3</priority>
  <reporter-id>a9LVVGSVCr375QeJe5cbCb</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Server Browser will not open.</summary>
  <updated-at type="datetime">2010-09-29T00:06:21Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>a9LVVGSVCr375QeJe5cbCb</id><login>IxionIndustries</login><login_name warning="deprecated">IxionIndustries</login_name><name>IxionIndustries</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2010-09-11T13:41:31Z</created-on>
  <description>wodex dieroller fails to handle openended die rolls properly. It only counts the first die roll, not the re rolled die. ex [8,9,[10,9]] will count as 3 success vs target of 8 not 4.

Attached is a new wodex dieroller that fixes this problem. I created two new world of darkness commands. .wod(target)  -- sums up all dice 8+ or what ever target you supply and .wods1(target) sums up all dice 8+ or target specified and subracts 1's from the roll. Open ended die rolls are handles by the std function .open(), the re-rolled dice were being returned as an instance instead of as an iterable list. I return the dice rolls as iterable lists.</description>
  <from-support type="integer">1</from-support>
  <id type="integer">2084115</id>
  <importance type="integer">132</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>dA9rpUVvCr36EzeJe5cbLr</notification-list>
  <number type="integer">132</number>
  <priority type="integer">3</priority>
  <reporter-id>dA9rpUVvCr36EzeJe5cbLr</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>wodex dieroller incorrectly adds openended die rolls.</summary>
  <updated-at type="datetime">2010-09-11T13:44:39Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dA9rpUVvCr36EzeJe5cbLr</id><login>rtrentc</login><login_name warning="deprecated">rtrentc</login_name><name>rtrentc</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">1</component-id>
  <created-on type="datetime">2010-11-10T19:08:04Z</created-on>
  <description>Maybe I am just in way over my head but a) there is no online manual, b) I can't figure out how to create new trees for the game system I want to run</description>
  <from-support type="integer">2</from-support>
  <id type="integer">2530165</id>
  <importance type="integer">134</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>cf10K47p0r37PLeJe5cbLA</notification-list>
  <number type="integer">134</number>
  <priority type="integer">3</priority>
  <reporter-id>cf10K47p0r37PLeJe5cbLA</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Manual + Tree</summary>
  <updated-at type="datetime">2010-11-10T19:08:04Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cf10K47p0r37PLeJe5cbLA</id><login>sunofbast</login><login_name warning="deprecated">sunofbast</login_name><name>sunofbast</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-12-17T19:08:26Z</created-on>
  <description>I unchecked Map in the window bar at the top, and it disappeared. No matter how many times I toggled it, it would not come back. I've restarted OpenRpg, and installed all the updates, and it's still not there. How can i get my Map window back? It was docked in the default mode.</description>
  <from-support type="integer">2</from-support>
  <id type="integer">2790783</id>
  <importance type="integer">135</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>cleZhEcHar4lxpeJe5cbCb</notification-list>
  <number type="integer">135</number>
  <priority type="integer">3</priority>
  <reporter-id>cleZhEcHar4lxpeJe5cbCb</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>map gone</summary>
  <updated-at type="datetime">2010-12-17T19:08:26Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cleZhEcHar4lxpeJe5cbCb</id><login>SashaFierce</login><login_name warning="deprecated">SashaFierce</login_name><name>SashaFierce</name><email>nice_ahsas@hotmail.com</email></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2011-01-28T04:17:53Z</created-on>
  <description>After moving the chat window to a secondary monitor, and closing openRPG, the chat window has completely disappeared, and I've as far been unable to recover it.</description>
  <from-support type="integer">2</from-support>
  <id type="integer">3026033</id>
  <importance type="integer">136</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>bwZTR0kPur4j-4eJe5cbLA</notification-list>
  <number type="integer">136</number>
  <priority type="integer">3</priority>
  <reporter-id>bwZTR0kPur4j-4eJe5cbLA</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Chat window disappeared.</summary>
  <updated-at type="datetime">2012-02-09T07:56:01Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bwZTR0kPur4j-4eJe5cbLA</id><login>Foxyer</login><login_name warning="deprecated">Foxyer</login_name><name>Foxyer</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2011-04-14T16:58:26Z</created-on>
  <description>My whispers aren't going through- at all; it's highly annoying and it doesn't let me whisper my results to my GM/DM so I can get my saving throws in without cluttering up the game! Please help.</description>
  <from-support type="integer">2</from-support>
  <id type="integer">3624995</id>
  <importance type="integer">137</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>auRSQKzRCr4kS8eJe5cbLA</notification-list>
  <number type="integer">137</number>
  <priority type="integer">3</priority>
  <reporter-id>auRSQKzRCr4kS8eJe5cbLA</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>The Whisper Function has Stopped Working For Me. No one Receives.</summary>
  <updated-at type="datetime">2011-04-14T16:58:26Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>auRSQKzRCr4kS8eJe5cbLA</id><login>john_lawhorne</login><login_name warning="deprecated">john_lawhorne</login_name><name>john_lawhorne</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">6</component-id>
  <created-on type="datetime">2011-09-06T02:51:14Z</created-on>
  <description>For some reason I can join rooms just fine, but I CANNOT create a room for my games. I am currently using windows 7 32 bit version, and also my OpenRPG refuses to update either.</description>
  <from-support type="integer">2</from-support>
  <id type="integer">6028341</id>
  <importance type="integer">138</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>dDn68C2dir4kl8eJe5cbLr</notification-list>
  <number type="integer">138</number>
  <priority type="integer">3</priority>
  <reporter-id>dDn68C2dir4kl8eJe5cbLr</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Cannot create rooms</summary>
  <updated-at type="datetime">2011-09-08T13:22:52Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dDn68C2dir4kl8eJe5cbLr</id><login>zanevalorenbishop</login><login_name warning="deprecated">zanevalorenbishop</login_name><name>zanevalorenbishop</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">1</component-id>
  <created-on type="datetime">2011-10-18T19:43:09Z</created-on>
  <description>If I open any tree node, close it, then open it again, OpenRPG crashes entirely, leaving only &quot;segmentation fault&quot; as an error message.   openrpg_sysinfo.txt follows.

OpenRPG System Info 10-18-11
OpenRPG Version: 1.8.0
OpenRPG Build: 090712-00
Python: 2.6.7 (r267:88850, Aug 11 2011, 12:16:10) 
[GCC 4.6.1]
wxPython Version: 2.8.12.0
Platform: Linux-3.0.0-12-generic-pae-i686-with-debian-wheezy-sid</description>
  <from-support type="integer">2</from-support>
  <id type="integer">8488903</id>
  <importance type="integer">139</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>c3XBVY-Car4iCbacwqjQXA</notification-list>
  <number type="integer">139</number>
  <priority type="integer">3</priority>
  <reporter-id>c3XBVY-Car4iCbacwqjQXA</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Repeated use of tree nodes crashes OpenRPG</summary>
  <updated-at type="datetime">2012-02-09T07:53:56Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>c3XBVY-Car4iCbacwqjQXA</id><login>hueloovoo</login><login_name warning="deprecated">hueloovoo</login_name><name>hueloovoo</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2012-02-29T02:56:10Z</created-on>
  <description>My OpenRPG has worked fine until today. I am unable to browse servers. I have not changed any hardware recently and I have done a fresh reinstall as well as normal computer reboots. Only new programs on my computer since the last successful use of OpenRPG are Anno 2070 and Dawn of Discovery (Anno 1404).</description>
  <from-support type="integer">1</from-support>
  <id type="integer">15882153</id>
  <importance type="integer">140</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>cPmRFeyOar4yxdacwqjQWU</notification-list>
  <number type="integer">140</number>
  <priority type="integer">3</priority>
  <reporter-id>cPmRFeyOar4yxdacwqjQWU</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Not able to browse servers</summary>
  <updated-at type="datetime">2012-02-29T02:57:45Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cPmRFeyOar4yxdacwqjQWU</id><login>abibiliboop</login><login_name warning="deprecated">abibiliboop</login_name><name>abibiliboop</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2012-03-23T22:49:36Z</created-on>
  <description>So I hate to make a ticket for something stupid but it seems its the only way of communicating at the moment.

I noticed from the assembla mailing list there has been some activity.  So I came here to see what is going on but I can't seem to post in the message area?  Not sure if its do to me permission level or what?  

I tend to be a busy individual but I still use this branch of OpenRPG for my gaming and a few of my gamers, myself included, are programmers.  Since updated have disappeared we have delved into the code a couple of times to make a change or two ourselves to make our lives easier.

Well not sure what can be done about the posting thing?  And I sure hope there is still life in this software.</description>
  <from-support type="integer">1</from-support>
  <id type="integer">17570693</id>
  <importance type="integer">141</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>cWMjumrmqr3Amzab7jnrAJ</notification-list>
  <number type="integer">141</number>
  <priority type="integer">3</priority>
  <reporter-id>cWMjumrmqr3Amzab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Can't Post Messages</summary>
  <updated-at type="datetime">2012-03-23T22:49:36Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cWMjumrmqr3Amzab7jnrAJ</id><login>Gelcur</login><login_name warning="deprecated">Gelcur</login_name><name>Gelcur</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2012-04-13T16:16:36Z</created-on>
  <description>I recieved this error while updating. can you help?</description>
  <from-support type="integer">1</from-support>
  <id type="integer">18807773</id>
  <importance type="integer">142</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>az80nKHymr4AZpacwqjQYw</notification-list>
  <number type="integer">142</number>
  <priority type="integer">3</priority>
  <reporter-id>az80nKHymr4AZpacwqjQYw</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Getting error during update</summary>
  <updated-at type="datetime">2012-05-20T23:31:27Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">Small</estimate>
  <total-estimate type="float">1.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>az80nKHymr4AZpacwqjQYw</id><login>ikavalios</login><login_name warning="deprecated">ikavalios</login_name><name>ikavalios</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">6</component-id>
  <created-on type="datetime">2012-04-15T01:57:26Z</created-on>
  <description>I am continuously failing to connect to the servers. I have restarted my computer and reset my system settings. Open RPG is attempting to access server addresses 127.0.0.1:6774

any advice would be appreciated.</description>
  <from-support type="integer">1</from-support>
  <id type="integer">18846383</id>
  <importance type="integer">143</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>dVnY_uHP0r4z9oacwqjQWU</notification-list>
  <number type="integer">143</number>
  <priority type="integer">3</priority>
  <reporter-id>dVnY_uHP0r4z9oacwqjQWU</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Failing to connect to server. </summary>
  <updated-at type="datetime">2012-04-15T01:57:26Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">Small</estimate>
  <total-estimate type="float">1.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dVnY_uHP0r4z9oacwqjQWU</id><login>mike.a.k.croce</login><login_name warning="deprecated">mike.a.k.croce</login_name><name>mike.a.k.croce</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2009-07-02T20:50:25Z</created-on>
  <description>This is funny.  I am looking for some way to get the chat windown to do CSS short of converting from wxPython to some other GUI package, and look what I found:

http://www.nabble.com/HTML-Rendering-td17953761.html

Three years later still nothing with wxMozilla.  Ah well.  It does occur to me that a simpler way around things would be to have the current non-CSS tags and the CSS stuff both together.  The CSS is ignored by the chat window.  Upon export we simply purge the non-CSS tags (such as &lt;b&gt;...&lt;/b&gt;).  </description>
  <from-support type="integer">0</from-support>
  <id type="integer">425456</id>
  <importance type="integer">34</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>dYtGZ-kC4r3BfFab7jnrAJ</notification-list>
  <number type="integer">34</number>
  <priority type="integer">4</priority>
  <reporter-id>dYtGZ-kC4r3BfFab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Add CSS to Chat</summary>
  <updated-at type="datetime">2010-08-24T10:51:45Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dYtGZ-kC4r3BfFab7jnrAJ</id><login>davidbyron</login><login_name warning="deprecated">davidbyron</login_name><name>davidbyron</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">7</component-id>
  <created-on type="datetime">2009-07-08T22:38:10Z</created-on>
  <description>Plans to re work the settings menu so it is safer and reduces any chances of user error.  The new menu will look almost identical by use wx.Notebook.  Here is an example from http://wiki.wxpython.org/Simple%20wx.Notebook%20Example


&lt;pre&gt;&lt;code&gt;
import wx


# Some classes to use for the notebook pages.  Obviously you would
# want to use something more meaningful for your application, these
# are just for illustration.

class PageOne(wx.Panel):
    def __init__(self, parent):
        wx.Panel.__init__(self, parent)
        t = wx.StaticText(self, -1, &quot;This is a PageOne object&quot;, (20,20))

class PageTwo(wx.Panel):
    def __init__(self, parent):
        wx.Panel.__init__(self, parent)
        t = wx.StaticText(self, -1, &quot;This is a PageTwo object&quot;, (40,40))

class PageThree(wx.Panel):
    def __init__(self, parent):
        wx.Panel.__init__(self, parent)
        t = wx.StaticText(self, -1, &quot;This is a PageThree object&quot;, (60,60))


class MainFrame(wx.Frame):
    def __init__(self):
        wx.Frame.__init__(self, None, title=&quot;Simple Notebook Example&quot;)

        # Here we create a panel and a notebook on the panel
        p = wx.Panel(self)
        nb = wx.Notebook(p)

        # create the page windows as children of the notebook
        page1 = PageOne(nb)
        page2 = PageTwo(nb)
        page3 = PageThree(nb)

        # add the pages to the notebook with the label to show on the tab
        nb.AddPage(page1, &quot;Page 1&quot;)
        nb.AddPage(page2, &quot;Page 2&quot;)
        nb.AddPage(page3, &quot;Page 3&quot;)

        # finally, put the notebook in a sizer for the panel to manage
        # the layout
        sizer = wx.BoxSizer()
        sizer.Add(nb, 1, wx.EXPAND)
        p.SetSizer(sizer)


if __name__ == &quot;__main__&quot;:
    app = wx.App()
    MainFrame().Show()
    app.MainLoop()
&lt;/code&gt;&lt;/pre&gt;
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">431063</id>
  <importance type="integer">39</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">8909</milestone-id>
  <notification-list>c2Q8uOewur3BXsab7jnrAJ</notification-list>
  <number type="integer">39</number>
  <priority type="integer">4</priority>
  <reporter-id>c2Q8uOewur3BXsab7jnrAJ</reporter-id>
  <space-id>dIvWc45xer3lzlabIlDkbG</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Settings Menu</summary>
  <updated-at type="datetime">2010-08-24T10:53:57Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>c2Q8uOewur3BXsab7jnrAJ</id><login>sirebral</login><login_name warning="deprecated">sirebral</login_name><name>sirebral</name><website>http://www.knowledgearcana.com</website></reporter>
</ticket>
</tickets>

