MapTool 1.2 Development Release Build 18
Moderators: dorpond, trevor, Azhrei, Craig
That definately might be an option once we get individual views incorporated. Especially when we have really strange visions like Soldiers who are wearing Infrared Goggles or something. Like you said, we could view at that one player.Dalna wrote:Yes outside the button. This would also when you have individual views you could cycle through each player view...Or maybe a drop down box that you select who's view you want to see. For now of coarse it would just be player and DM.
Good idea Dalna!
- trevor
- Codeum Arcanum (RPTools Founder)
- Posts: 11311
- Joined: Mon Jan 09, 2006 4:16 pm
- Location: Austin, Tx
- Contact:
I was thinking the same thingDalna wrote:Yes outside the button. This would also when you have individual views you could cycle through each player view...Or maybe a drop down box that you select who's view you want to see. For now of coarse it would just be player and DM.
Dreaming of a 1.3 release
Small but worth mentioning.
If I drop a stamp and it is defaulted to Snap Off; if I right click on that and tell it to Snap to Grid, copy it with Control C, and then paste it, it will paste with Grid Off.
If I right click on the file, tell it to Snap to Grid, move it a bit to confirm it is snapped, copy it and paste it, it will paste with the Snap On like it should.
So basically, the snap to grid isn't being copied unless I move the stamp around first.
If I drop a stamp and it is defaulted to Snap Off; if I right click on that and tell it to Snap to Grid, copy it with Control C, and then paste it, it will paste with Grid Off.
If I right click on the file, tell it to Snap to Grid, move it a bit to confirm it is snapped, copy it and paste it, it will paste with the Snap On like it should.
So basically, the snap to grid isn't being copied unless I move the stamp around first.
I was drawing square textures when I went to change to a different texture in the texture dialog and when I went to start drawing it, I wasn't able to draw anything. So I tried a few times and nothing. I went into the dialog and changed texture but I still couldn't draw anything.
So then I changed to a different drawing tool instead of the square that wasn't working and then I got this:
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.drawing.RectangleTool.mouseMoved(RectangleTool.java:145)
at java.awt.AWTEventMulticaster.mouseMoved(Unknown Source)
at java.awt.AWTEventMulticaster.mouseMoved(Unknown Source)
at java.awt.Component.processMouseMotionEvent(Unknown Source)
at javax.swing.JComponent.processMouseMotionEvent(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.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(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)
So then I changed to a different drawing tool instead of the square that wasn't working and then I got this:
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.drawing.RectangleTool.mouseMoved(RectangleTool.java:145)
at java.awt.AWTEventMulticaster.mouseMoved(Unknown Source)
at java.awt.AWTEventMulticaster.mouseMoved(Unknown Source)
at java.awt.Component.processMouseMotionEvent(Unknown Source)
at javax.swing.JComponent.processMouseMotionEvent(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.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(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)
Outstanding bug
My group first noticed this one a couple weeks ago, but in that time I've also been moving and so did not have time to drop you a line about it.
If you use the /clear command, it will perform as expected and clear away the history window...
... and then disallow any new entries into the history window. In other words: from the moment you use the /clear command, you will no longer see anything that anyone types. In fact, you won't even be able to see what you type. Absolutely nothing is displayed in the history window, any longer. (This does not, however, effect what others are able to see; it only borks things up on your end.)
The only way that we found to undo this was to close out MT and restart it. This bug was verified by 3 of my players, and was first experienced by me while running the server.
I just downloaded your latest build, and ran to copies of MT locally: one in server mode, and the other as a client. The bug is still there.
-ltwally
BTW: Except for this latest bug, I really enjoy version 1.2. Keep up the good work!
pps. My guys are still itching for some form of typing indicator.... it turns out we're all really slow typers and we're all really impatient people!!
If you use the /clear command, it will perform as expected and clear away the history window...
... and then disallow any new entries into the history window. In other words: from the moment you use the /clear command, you will no longer see anything that anyone types. In fact, you won't even be able to see what you type. Absolutely nothing is displayed in the history window, any longer. (This does not, however, effect what others are able to see; it only borks things up on your end.)
The only way that we found to undo this was to close out MT and restart it. This bug was verified by 3 of my players, and was first experienced by me while running the server.
I just downloaded your latest build, and ran to copies of MT locally: one in server mode, and the other as a client. The bug is still there.
-ltwally
BTW: Except for this latest bug, I really enjoy version 1.2. Keep up the good work!
pps. My guys are still itching for some form of typing indicator.... it turns out we're all really slow typers and we're all really impatient people!!
ps
Trevor: thanks for fixing the /clear bug.
I saw the first two screenshots from BattleGrounds ( http://www.battlegroundsgames.com/screenshots.html ) and immediately thought, "whoa, I should be using Fog-of-War in MT !!" Then I started playing with it, but was unable to peel back the FoW with a token's lighting....
Am I doing something wrong? Is it a bug? Or is it just not a feature of MT?
Also, I would like to request that the light have a new point-of-view option: centered on player. That way, a player doesn't have to keep track of which point his lantern is on, or whatever. We'd like to assume that if his vision is 4-squares, it is 4-squares from every corner of his token. (As it is, the best we can do is emenate from a corner, which hides a little that we'd rather not have hidden....)
Anyhoo, thanks again..
-ltwally.
I saw the first two screenshots from BattleGrounds ( http://www.battlegroundsgames.com/screenshots.html ) and immediately thought, "whoa, I should be using Fog-of-War in MT !!" Then I started playing with it, but was unable to peel back the FoW with a token's lighting....
Am I doing something wrong? Is it a bug? Or is it just not a feature of MT?
Also, I would like to request that the light have a new point-of-view option: centered on player. That way, a player doesn't have to keep track of which point his lantern is on, or whatever. We'd like to assume that if his vision is 4-squares, it is 4-squares from every corner of his token. (As it is, the best we can do is emenate from a corner, which hides a little that we'd rather not have hidden....)
Anyhoo, thanks again..
-ltwally.
- trevor
- Codeum Arcanum (RPTools Founder)
- Posts: 11311
- Joined: Mon Jan 09, 2006 4:16 pm
- Location: Austin, Tx
- Contact:
You'll want to use Vision instead of Light. Light is the Old Way, Vision is the New Way. The current light implementation will soon be replaced with something different.
To add a vision to a token, right click it->Vision->New Vision, select the type and radius, then when the fog of war is on right click the token->Expose->Visible Area.
Note this is a 1.2 feature only. Note if you add topology (the eye tool) the vision will automatically calculate line of sight
To add a vision to a token, right click it->Vision->New Vision, select the type and radius, then when the fog of war is on right click the token->Expose->Visible Area.
Note this is a 1.2 feature only. Note if you add topology (the eye tool) the vision will automatically calculate line of sight
Dreaming of a 1.3 release
- trevor
- Codeum Arcanum (RPTools Founder)
- Posts: 11311
- Joined: Mon Jan 09, 2006 4:16 pm
- Location: Austin, Tx
- Contact:
Re: Outstanding bug
This is fixed for 1.2b19ltwally wrote: If you use the /clear command, it will perform as expected and clear away the history window...
... and then disallow any new entries into the history window.
Dreaming of a 1.3 release
Exception in Grid Adjustment dialog
While trying to set a negative offset. One each for the X and Y.
BTW new maps don't pick up the new grid size but they do get the offset. They should do both or neither probably.
Exception in thread "AWT-EventQueue-0" java.lang.NumberFormatException: For input string: "-"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at net.rptools.maptool.client.tool.GridTool.getInt(GridTool.java:192)
at net.rptools.maptool.client.tool.GridTool.getInt(GridTool.java:189)
at net.rptools.maptool.client.tool.GridTool.copyControlPanelToGrid(GridTool.java:172)
at net.rptools.maptool.client.tool.GridTool.access$2(GridTool.java:166)
at net.rptools.maptool.client.tool.GridTool$UpdateGridListener.keyReleased(GridTool.java:386)
at java.awt.Component.processKeyEvent(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)
BTW new maps don't pick up the new grid size but they do get the offset. They should do both or neither probably.
Exception in thread "AWT-EventQueue-0" java.lang.NumberFormatException: For input string: "-"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at net.rptools.maptool.client.tool.GridTool.getInt(GridTool.java:192)
at net.rptools.maptool.client.tool.GridTool.getInt(GridTool.java:189)
at net.rptools.maptool.client.tool.GridTool.copyControlPanelToGrid(GridTool.java:172)
at net.rptools.maptool.client.tool.GridTool.access$2(GridTool.java:166)
at net.rptools.maptool.client.tool.GridTool$UpdateGridListener.keyReleased(GridTool.java:386)
at java.awt.Component.processKeyEvent(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)