MapTool 1.1 Development Release Build 33 Release Candidate 1
Moderators: dorpond, trevor, Azhrei, Craig
- trevor
- Codeum Arcanum (RPTools Founder)
- Posts: 11311
- Joined: Mon Jan 09, 2006 4:16 pm
- Location: Austin, Tx
- Contact:
MapTool 1.1 Development Release Build 33 Release Candidate 1
Here it is, the first 1.1 Release Candidate. We'll be updating the website over the next couple days to reflect the RC status of this release.
In the mean time, please bang the heck out of this release, with particular attention to drawables. Please post bugs here and I'll track them.
Build 33 (11/26/06) RC1
* Remove ' from template distance measurements to be consistent with other distance rendering
* Change View Token Titles to View Token Names
* Fix "stamp layer panel pops into place the first time the tool is selected"
* Terminology change: "Stamp" layer has become the "Object" layer
* Add Default Grid Size to the preferences panel
* New Map dialog Browse remembers the last directory you were looking in
* Fix minimap update bug
* Remove "Exit" shortcut key
* Rebuild drawable renderer, now handles huge drawables with ease, and antialiases them
In the mean time, please bang the heck out of this release, with particular attention to drawables. Please post bugs here and I'll track them.
Build 33 (11/26/06) RC1
* Remove ' from template distance measurements to be consistent with other distance rendering
* Change View Token Titles to View Token Names
* Fix "stamp layer panel pops into place the first time the tool is selected"
* Terminology change: "Stamp" layer has become the "Object" layer
* Add Default Grid Size to the preferences panel
* New Map dialog Browse remembers the last directory you were looking in
* Fix minimap update bug
* Remove "Exit" shortcut key
* Rebuild drawable renderer, now handles huge drawables with ease, and antialiases them
Dreaming of a 1.3 release
Huzzah! Good usability tweaks.
I definitely like the change of the layer name to Object.
Small buglet: Draw a poly-line with left-click, several right-clicks and finish with a left-click. The line disappears. Draw another line segment and it comes back.
Actually, it happens with single line segments as well just not as consistantly. A problem with the display being changed outside of the AWT/Swing thread?
I noticed that Java 1.5.0_07 is particularly sensitive to this.
I definitely like the change of the layer name to Object.
Small buglet: Draw a poly-line with left-click, several right-clicks and finish with a left-click. The line disappears. Draw another line segment and it comes back.
Actually, it happens with single line segments as well just not as consistantly. A problem with the display being changed outside of the AWT/Swing thread?
I noticed that Java 1.5.0_07 is particularly sensitive to this.
I am very happy to say that this new drawing setup you having going on ROCKS!
I always avoided drawing large maps with the drawing tools because of how it slowed things down but now, I was able to draw a huge map (as if drawing on a battle mat) and noticed no slow down what-so-ever.
GREAT STUFF TREVOR!
Now, as far as the issue Phergus brought up - I did use the line (with snap on) and free hand tools and noticed no problem at all. I drew a huge map too.
I wonder if it is related to a java version? I am running 1.5.0_06 on this test box.
I always avoided drawing large maps with the drawing tools because of how it slowed things down but now, I was able to draw a huge map (as if drawing on a battle mat) and noticed no slow down what-so-ever.
GREAT STUFF TREVOR!
Now, as far as the issue Phergus brought up - I did use the line (with snap on) and free hand tools and noticed no problem at all. I drew a huge map too.
I wonder if it is related to a java version? I am running 1.5.0_06 on this test box.
I think the renaming of Stamps to Objects has broken all my campaigns. All the stamps that were are now tokens and are showing stacking symbols..
I am assuming there is no way around this, right Trevor? Except of course that I have to change them back into Objects now?
I would rather have it Objects than Stamps so this was definately a needed change but I was just getting into a panic when I thought about the 700+ objects in the Halloween campaign alone, along with the Tavern in a Tower and others that i use for gaming.
I am assuming there is no way around this, right Trevor? Except of course that I have to change them back into Objects now?
I would rather have it Objects than Stamps so this was definately a needed change but I was just getting into a panic when I thought about the 700+ objects in the Halloween campaign alone, along with the Tavern in a Tower and others that i use for gaming.
Last edited by dorpond on Thu Dec 14, 2006 3:26 pm, edited 1 time in total.
- trevor
- Codeum Arcanum (RPTools Founder)
- Posts: 11311
- Joined: Mon Jan 09, 2006 4:16 pm
- Location: Austin, Tx
- Contact:
Hmmm, I was afraid of that. I might be able to put in a stop gap, basically translating the old Stamp into Object on the fly.dorpond wrote:All the stamps that were are now tokens and are showing stacking symbols..
Fortunately, it's also fairly easy to mass change token types.
Dreaming of a 1.3 release
Can't test it at the moment (on a different PC) but I can confirm that it doesn't happen under Java 1.5.0_06.trevor wrote:Instead of drawing a new line segment, does it also "come back" if you simply pan the map ?Phergus wrote: Small buglet: Draw a poly-line with left-click, several right-clicks and finish with a left-click. The line disappears. Draw another line segment and it comes back.
I'll bet that any pan or resize will cause it to show up though.
I can confirm now that pan or resize causes the missing line segments to appear.
I don't know but it affected the SVG rendering as well. I found that I had to pass any changes to the SVG document off to the canvas update manager or I would see the same type of problems. Of course that's what the docs told me to do anyway but who reads docs?
I was told that the same kind of rule applies for changing Swing components on the fly.
javax.swing.SwingUtilities.invokeLater(new Runnable() {
public void run() {
/* code to modify components goes here */
}
});
I'm sure that you already know this.
I don't know but it affected the SVG rendering as well. I found that I had to pass any changes to the SVG document off to the canvas update manager or I would see the same type of problems. Of course that's what the docs told me to do anyway but who reads docs?
I was told that the same kind of rule applies for changing Swing components on the fly.
javax.swing.SwingUtilities.invokeLater(new Runnable() {
public void run() {
/* code to modify components goes here */
}
});
I'm sure that you already know this.
I ran a host session with Phergus as a client. I got this in Java. Not sure what caused it since I wasn't watching it.
The drawing stuff works really well though!
TinyLaF v1.3.04
'Default.theme' not found - using YQ default theme.
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
at net.rptools.maptool.client.tool.StampTool.cycleSelectedToken(StampTool.java:916)
at net.rptools.maptool.client.tool.StampTool.access$3(StampTool.java:889)
at net.rptools.maptool.client.tool.StampTool$15.actionPerformed(StampTool.java:878)
at javax.swing.SwingUtilities.notifyAction(Unknown Source)
at javax.swing.JComponent.processKeyBinding(Unknown Source)
at javax.swing.JComponent.processKeyBindings(Unknown Source)
at javax.swing.JComponent.processKeyEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.KeyboardFocusManager.redispatchEvent(Unknown Source)
at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(Unknown Source)
at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(Unknown Source)
at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(Unknown Source)
at java.awt.DefaultKeyboardFocusManager.dispatchEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
The drawing stuff works really well though!
TinyLaF v1.3.04
'Default.theme' not found - using YQ default theme.
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
at net.rptools.maptool.client.tool.StampTool.cycleSelectedToken(StampTool.java:916)
at net.rptools.maptool.client.tool.StampTool.access$3(StampTool.java:889)
at net.rptools.maptool.client.tool.StampTool$15.actionPerformed(StampTool.java:878)
at javax.swing.SwingUtilities.notifyAction(Unknown Source)
at javax.swing.JComponent.processKeyBinding(Unknown Source)
at javax.swing.JComponent.processKeyBindings(Unknown Source)
at javax.swing.JComponent.processKeyEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.KeyboardFocusManager.redispatchEvent(Unknown Source)
at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(Unknown Source)
at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(Unknown Source)
at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(Unknown Source)
at java.awt.DefaultKeyboardFocusManager.dispatchEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)