MapTool 1.2 Development Release Build 17
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.2 Development Release Build 17
The "Use at your own risk" release.
This release targets bugs, and a touch of polish, and a new segmented image transfer mechanism. YMMV.
Ordinarily I'd wait a couple more days and do more testing of the networking part, but there's a couple high priority fixes needed from b16, and you all have proven to be amazing testers, so, I give you 1.2b17:
Build 17 (2/22/2007)
* Integrated dicelib into MapTool. This allows for more complex expressions.
* Changed the inline rolling to wrap the roll in «» characters.
* Changed the cheater detection to look for «» characters and the HTML equivalent character codes: «, «, », »
* Minor optimization to vision calculations
* Minor optimization to drawable renderer
* Minor tweak to make drawables snap-to-grid fit next to each other
* Segmented image transfers
* Remove red line from around menus
* Rotate map selector button arrow to point down
* Move View as Player to View menu
* Move New Map and Quickmap menus to File menu
* Fix bug: zone selection popup breaking when an invisible zone exists
* Indicate zone is hidden in zone selection popup
* Fix bug: area intersection NPE
* Show "Connecting" message until the campaign data has been loaded
This release targets bugs, and a touch of polish, and a new segmented image transfer mechanism. YMMV.
Ordinarily I'd wait a couple more days and do more testing of the networking part, but there's a couple high priority fixes needed from b16, and you all have proven to be amazing testers, so, I give you 1.2b17:
Build 17 (2/22/2007)
* Integrated dicelib into MapTool. This allows for more complex expressions.
* Changed the inline rolling to wrap the roll in «» characters.
* Changed the cheater detection to look for «» characters and the HTML equivalent character codes: «, «, », »
* Minor optimization to vision calculations
* Minor optimization to drawable renderer
* Minor tweak to make drawables snap-to-grid fit next to each other
* Segmented image transfers
* Remove red line from around menus
* Rotate map selector button arrow to point down
* Move View as Player to View menu
* Move New Map and Quickmap menus to File menu
* Fix bug: zone selection popup breaking when an invisible zone exists
* Indicate zone is hidden in zone selection popup
* Fix bug: area intersection NPE
* Show "Connecting" message until the campaign data has been loaded
Dreaming of a 1.3 release
Very cool Trevor! I am really liking the overall feel of MT as it progresses.
I see that the BOOT feature works well. I am not sure when you implemented that but it works like a champ - Bye bye bad guy! You might also want to implement a way to prevent that bad guy from popping back on after a boot though - block his IP or something but also allow us to unblock him so it isn't a perminent thing. Just a thought.
I loaded up the MountainPassV3 campaign that I love to use for my initial testing and I got this when it was loading. I already had a client connected when I loaded it in case you needed that information:
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.ui.zone.ZoneMiniMapPanel.paintComponent(ZoneMiniMapPanel.java:106)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JLayeredPane.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintWithOffscreenBuffer(Unknown Source)
at javax.swing.JComponent.paintDoubleBuffered(Unknown Source)
at javax.swing.JComponent._paintImmediately(Unknown Source)
at javax.swing.JComponent.paintImmediately(Unknown Source)
at javax.swing.RepaintManager.paintDirtyRegions(Unknown Source)
at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(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)
I see that the BOOT feature works well. I am not sure when you implemented that but it works like a champ - Bye bye bad guy! You might also want to implement a way to prevent that bad guy from popping back on after a boot though - block his IP or something but also allow us to unblock him so it isn't a perminent thing. Just a thought.
I loaded up the MountainPassV3 campaign that I love to use for my initial testing and I got this when it was loading. I already had a client connected when I loaded it in case you needed that information:
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.ui.zone.ZoneMiniMapPanel.paintComponent(ZoneMiniMapPanel.java:106)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JLayeredPane.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintWithOffscreenBuffer(Unknown Source)
at javax.swing.JComponent.paintDoubleBuffered(Unknown Source)
at javax.swing.JComponent._paintImmediately(Unknown Source)
at javax.swing.JComponent.paintImmediately(Unknown Source)
at javax.swing.RepaintManager.paintDirtyRegions(Unknown Source)
at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(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)
Well I tested for a good half hour - basically opening up older campaigns and poked around the interface to see what has changed. So far so good!
I won't know if the chucnking works well until I do some networking tests. Perhaps this weekend I will post a test for us users to play around with and see how things load up now.
Later on today I will do some map building to verify functionality in that area.
We are getting closer my Friend!
Great Stuff!
I won't know if the chucnking works well until I do some networking tests. Perhaps this weekend I will post a test for us users to play around with and see how things load up now.
Later on today I will do some map building to verify functionality in that area.
We are getting closer my Friend!
Great Stuff!
- trevor
- Codeum Arcanum (RPTools Founder)
- Posts: 11311
- Joined: Mon Jan 09, 2006 4:16 pm
- Location: Austin, Tx
- Contact:
Good feedback. I'll spend more time working with it this weekend.dorpond wrote:Drawing with snap on is worse now than it was in previous versions. just about everything drawn doesn't seem to be snapping to the grid now.
1.2b17 contains all the new features for 1.2, so now it's just a matter of fleshing out, polishing, and fixing bugs.
Dreaming of a 1.3 release
WHOA!!!
OK, this might be an isolated issue - I don't know. I was fixing a friends laptop and after I was done, I installed the latest Java and downloaded the zipped versions of 1.1b35 for our game night and I also download 1.2b17 so I could do some quick testing before I returned it to him.
I never started 1.1 and went right to 1.2b17. When I loaded it up, there was nothing at all in the image explorer - it is COMPLETELY empty!
Before I try the 'restore default images' trick, I wanted to leave it as is in case you wanted me to try anything Trevor.
So basically, I have no default tokens, no folders at all in the image explorer - just blank in those windows.
Let me know what you would like for me to try. Again this laptop never had Maptool on it previous to this installation.
OK, this might be an isolated issue - I don't know. I was fixing a friends laptop and after I was done, I installed the latest Java and downloaded the zipped versions of 1.1b35 for our game night and I also download 1.2b17 so I could do some quick testing before I returned it to him.
I never started 1.1 and went right to 1.2b17. When I loaded it up, there was nothing at all in the image explorer - it is COMPLETELY empty!
Before I try the 'restore default images' trick, I wanted to leave it as is in case you wanted me to try anything Trevor.
So basically, I have no default tokens, no folders at all in the image explorer - just blank in those windows.
Let me know what you would like for me to try. Again this laptop never had Maptool on it previous to this installation.
Re: MapTool 1.2 Development Release Build 17
I think it looks better.trevor wrote: * Rotate map selector button arrow to point down
I don't think I like this. The top level "document" for MapTool is the campaign. Maps are part of campaignstrevor wrote: * Move New Map and Quickmap menus to File menu
And it clutters up the File menu and leaves the Map menu with only 3(?) items.
When FoW is turned on by default, new maps are black in the minimap until you switch to another map or toggle the hidden status even if you turn off FoW. Basically the minimap isn't updating its status after a FoW toggle unless some other map action is taken.
You know that bug where if you zoomed way in on a big map and then hit the plus key to reset zoom to 1:1 how MT would put the map up and off the top left corner? It still does that.
Re: MapTool 1.2 Development Release Build 17
I think my default, new users are going to look under File when trying to make Maptool run. That being said, I think I like it where it is now. One the same hand, I can see it logically going under Map also. There are a few items that could go in many places; take Show as Player for one - that could also go under Map becasue it seems logical but so does View. "View -> View map as a player" or "Map -> View as a player".Phergus wrote:I think it looks better.trevor wrote: * Rotate map selector button arrow to point down
I don't think I like this. The top level "document" for MapTool is the campaign. Maps are part of campaignstrevor wrote: * Move New Map and Quickmap menus to File menu
And it clutters up the File menu and leaves the Map menu with only 3(?) items.
So there are a lot of places stuff could go. Like I said though, I think all new users are going to look under File to get things started.
Hey Trevor, you might want to take out Chat and Run macro under the Tools menu now. Are they really needed? Chat already exists under Window and who really uses the Run Macro tool anyway? Unless it is just there to show new users that it is possible *shrug*
Re: MapTool 1.2 Development Release Build 17
I think even new users will be able to make the leap that Map operations might be found under the Map menu.dorpond wrote:Like I said though, I think all new users are going to look under File to get things started.
But if New Map is under the File Menu shouldn't Delete Map be there also? Won't the new user look there for it? Adjust Grid should probably go under View where the other two Grid related operations are found. Enable FoW sounds like visual thing so it should probably move to View as well. Hide from Players is also a visual thing so off to the View menu it goes as well. Seems like the Map menu isn't really needed.
Maybe I'm giving humanity too much credit by expecting that users wouldn't take more than a second or two to find the Map menu.