MapTool 1.3 Development Build 51

New build announcements plus site news and changes.

Moderators: dorpond, trevor, Azhrei, Craig

Daeger
Cave Troll
Posts: 85
Joined: Thu Oct 04, 2007 12:52 pm

Re: MapTool 1.3 Development Build 51

Post by Daeger »

trevor wrote:When you send it, could you include something specific to look for, perhaps even send a screenshot of what it's supposed to look like ?
I tried IM'ing you but you weren't there. It will look like what it looks like when you open it - there's a long table with a ton of chairs. When you start a server, some of the chairs crop up over the table. I'm emailing it now..

User avatar
trevor
Codeum Arcanum (RPTools Founder)
Posts: 11311
Joined: Mon Jan 09, 2006 4:16 pm
Location: Austin, Tx
Contact:

Re: MapTool 1.3 Development Build 51

Post by trevor »

Aha ! That's the part that I was missing 'and start server'

Sweet, this bug is officially nailed ! And will be part of tonights b52 build

Thanks for the help finding and squishing this one, it's been a pain for a long while
Dreaming of a 1.3 release

User avatar
Steel Rat
Great Wyrm
Posts: 1765
Joined: Tue Jun 13, 2006 5:55 pm
Location: Oak Harbor, WA
Contact:

Re: MapTool 1.3 Development Build 51

Post by Steel Rat »

Great work doods! darn, I shouldn't be using words like that when I'm almost 47. ;)

Some old requests again:

- Remember last zoom and position on save (This used to work, mentioned before. I think it changed somewhere between b30 and b33, if memory serves)
- Remember grid on/off settings for the campaign/map
- Remember token names on/off for campaign/map
Steel Rat
-----------
RPGMapShare.com - RPG Maps and Mapping objects.
Discord Server

User avatar
Mrugnak
Dragon
Posts: 745
Joined: Mon Jul 21, 2008 7:38 pm

Re: MapTool 1.3 Development Build 51

Post by Mrugnak »

Is conic vision part of this build, or just conic lights?

How do you set the degree-arc-thingy of the lights?

User avatar
jfrazierjr
Deity
Posts: 5176
Joined: Tue Sep 11, 2007 7:31 pm

Re: MapTool 1.3 Development Build 51

Post by jfrazierjr »

Mrugnak wrote:Is conic vision part of this build, or just conic lights?

How do you set the degree-arc-thingy of the lights?
arc=X, put that in right after you define the shape. You can ALSO set the arc for shadowy vision which is WAY cool.. Note the default is 90 degrees.
I save all my Campaign Files to DropBox. Not only can I access a campaign file from pretty much any OS that will run Maptool(Win,OSX, linux), but each file is versioned, so if something goes crazy wild, I can always roll back to a previous version of the same file.

Get your Dropbox 2GB via my referral link, and as a bonus, I get an extra 250 MB of space. Even if you don't don't use my link, I still enthusiastically recommend Dropbox..

User avatar
trevor
Codeum Arcanum (RPTools Founder)
Posts: 11311
Joined: Mon Jan 09, 2006 4:16 pm
Location: Austin, Tx
Contact:

Re: MapTool 1.3 Development Build 51

Post by trevor »

Mrugnak wrote:Is conic vision part of this build, or just conic lights?

How do you set the degree-arc-thingy of the lights?
Just lights for now
Dreaming of a 1.3 release

User avatar
RPTroll
TheBard
Posts: 3159
Joined: Tue Mar 21, 2006 7:26 pm
Location: Austin, Tx
Contact:

Re: MapTool 1.3 Development Build 51

Post by RPTroll »

trevor wrote:
Mrugnak wrote:Is conic vision part of this build, or just conic lights?

How do you set the degree-arc-thingy of the lights?
Just lights for now
Conic vision?!?!!? SWEEEEEEEEEEEEEEEEEEEEEEEEEEEET!
ImageImage ImageImageImageImage
Support RPTools by shopping
Image
Image

User avatar
Mrugnak
Dragon
Posts: 745
Joined: Mon Jul 21, 2008 7:38 pm

Re: MapTool 1.3 Development Build 51

Post by Mrugnak »

Bug: Conic lighting on a hex map... lights up the characters square :D

Sehmket
Kobold
Posts: 3
Joined: Tue Mar 03, 2009 6:41 pm

Re: MapTool 1.3 Development Build 51

Post by Sehmket »

Hi, all. I'm not sure if this is the right forum, but the problem cropped up after we upgraded to the new build, so I think I'm in the right spot.

We had the dim light set to red previously (I believe this is the default), and when we upgraded to the new version, it seems to be prefering the dim light over the regular light, for lack of a better way to say it. I took a screencap to help illustrate:

http://i62.photobucket.com/albums/h91/S ... xample.jpg

You can see here what I'm talking about - Naivera has a light source of four, and the two people inside her light source have a light source of 1 of dim light. The program seems to be prefering their dim light over the full light... how can we reverse this?

Thanks in advance!

User avatar
trevor
Codeum Arcanum (RPTools Founder)
Posts: 11311
Joined: Mon Jan 09, 2006 4:16 pm
Location: Austin, Tx
Contact:

Re: MapTool 1.3 Development Build 51

Post by trevor »

can you send me this campaign with this exact setup ?
Dreaming of a 1.3 release

Craig
Great Wyrm
Posts: 2107
Joined: Sun Jun 22, 2008 7:53 pm
Location: Melbourne, Australia

Re: MapTool 1.3 Development Build 51

Post by Craig »

cubeblue wrote:
trevor wrote:@cubeblue Could you look in your .maptool directory for a log.txt and see if there's an error in there, and post it here ?
I have a log.txt but it's empty (0 KB and when I open with notepad, there's nothing). I started MapTools up after I got that last error, would that wipe the log.txt?
Ok I got a similar error last night, after clicking the close and saving when it asked me if I want to save MapTool got stuck and I had to kill it. I didn't think much of it at the time as my computer has been playing up a lot last couple of days. But I managed to dig up the error from the log file.

Code: Select all

2009-03-04 00:43:16,388 [AWT-EventQueue-1] ERROR - java.lang.NullPointerException
java.lang.NullPointerException
	at com.jeta.open.support.DefaultComponentFinder.unregisterComponent(Unknown Source)
	at com.jeta.open.support.DefaultComponentFinder.componentRemoved(Unknown Source)
	at java.awt.Container.processContainerEvent(Container.java:2131)
	at java.awt.Container.processEvent(Container.java:2099)
	at java.awt.Component.dispatchEventImpl(Component.java:4497)
	at java.awt.Container.dispatchEventImpl(Container.java:2160)
	at java.awt.Component.dispatchEvent(Component.java:4327)
	at java.awt.Container.remove(Container.java:1163)
	at java.awt.Container.remove(Container.java:1203)
	at java.awt.Container.addImpl(Container.java:1032)
	at java.awt.Container.add(Container.java:903)
	at javax.swing.plaf.basic.BasicScrollPaneUI.updateColumnHeader(BasicScrollPaneUI.java:606)
	at javax.swing.plaf.basic.BasicScrollPaneUI$Handler.scrollPanePropertyChange(BasicScrollPaneUI.java:1100)
	at javax.swing.plaf.basic.BasicScrollPaneUI$Handler.propertyChange(BasicScrollPaneUI.java:1077)
	at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339)
	at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:276)
	at java.awt.Component.firePropertyChange(Component.java:7953)
	at javax.swing.JScrollPane.setColumnHeader(JScrollPane.java:1098)
	at javax.swing.JScrollPane.setColumnHeaderView(JScrollPane.java:1123)
	at javax.swing.JTable.unconfigureEnclosingScrollPane(JTable.java:764)
	at javax.swing.JTable.removeNotify(JTable.java:735)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at java.awt.Container.removeNotify(Container.java:2663)
	at javax.swing.JComponent.removeNotify(JComponent.java:4699)
	at javax.swing.JRootPane.removeNotify(JRootPane.java:750)
	at java.awt.Container.removeNotify(Container.java:2663)
	at java.awt.Window.removeNotify(Window.java:650)
	at java.awt.Window$1DisposeAction.run(Window.java:978)
	at java.awt.Window.doDispose(Window.java:990)
	at java.awt.Dialog.doDispose(Dialog.java:1243)
	at java.awt.Window.dispose(Window.java:937)
	at java.awt.Window.disposeImpl(Window.java:947)
	at java.awt.Window$1DisposeAction.run(Window.java:973)
	at java.awt.Window.doDispose(Window.java:990)
	at java.awt.Window.dispose(Window.java:937)
	at com.jidesoft.docking.DefaultDockableHolder.dispose(Unknown Source)
	at net.rptools.maptool.client.ui.MapToolFrame.closingMaintenance(MapToolFrame.java:1286)
	at net.rptools.maptool.client.ui.MapToolFrame.windowClosing(MapToolFrame.java:1240)
	at java.awt.AWTEventMulticaster.windowClosing(AWTEventMulticaster.java:333)
	at java.awt.AWTEventMulticaster.windowClosing(AWTEventMulticaster.java:332)
	at java.awt.Window.processWindowEvent(Window.java:1827)
	at javax.swing.JFrame.processWindowEvent(JFrame.java:279)
	at java.awt.Window.processEvent(Window.java:1785)
	at java.awt.Component.dispatchEventImpl(Component.java:4497)
	at java.awt.Container.dispatchEventImpl(Container.java:2160)
	at java.awt.Window.dispatchEventImpl(Window.java:2440)
	at java.awt.Component.dispatchEvent(Component.java:4327)
	at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
	at net.rptools.maptool.client.swing.MapToolEventQueue.dispatchEvent(MapToolEventQueue.java:24)
	at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:300)
	at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:210)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:200)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:195)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:187)
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)

Craig
Great Wyrm
Posts: 2107
Joined: Sun Jun 22, 2008 7:53 pm
Location: Melbourne, Australia

Re: MapTool 1.3 Development Build 51

Post by Craig »

plothos wrote:Cool. Thanks, IMarv.
Now,
trevor wrote:* Default properties will now be evaluated on the statsheet if there is no value in the property. Even from within evaluated properties.
How does this work, exactly? I take it this is so that coded properties using if() and such don't break the statsheet, but are empty properties in the argument treated as =0 or what?
Previously if you had something like
*ConMod:0
*Level:1
*HP:{Level*5+ConMod}

If you had not edited the token in the token properties (and some times when you had) You would get prompted for all 3 values on mouse over because it wasnt picking up the default. The same would occur if you did [Level] in chat. The change that was made was if the property does not exist on the token then go check the default values for the current token type and return the default if there is one.

If there is no default you will still get the prompt. So at this point you still need to provide defaults if you plan on basing an evaluated property on another one. I did not change the behavior if there is no default as that would stop prompting if that property was used in chat.

I can stop the prompting on mouse over if there is a general consensus as to what to return, hmm might require some tweaking to MapToolVariableResolver though.

User avatar
plothos
Great Wyrm
Posts: 1890
Joined: Sat Jun 21, 2008 1:07 am

Re: MapTool 1.3 Development Build 51

Post by plothos »

Craig wrote:Previously if you had something like
*ConMod:0
*Level:1
*HP:{Level*5+ConMod}

If you had not edited the token in the token properties (and some times when you had) You would get prompted for all 3 values on mouse over because it wasnt picking up the default.
This isn't universally true for me, actually, in b49. I can create a new token with defaults, never touch it, and have it display just fine. But it does sometimes cause problems, so...
Craig wrote:The change that was made was if the property does not exist on the token then go check the default values for the current token type and return the default if there is one.
THANK YOU THANK YOU THANK YOU!!!!!

User avatar
Hawke
Great Wyrm
Posts: 2261
Joined: Sat Apr 21, 2007 12:12 am
Location: Albuquerque, NM

Re: MapTool 1.3 Development Build 51

Post by Hawke »

Are auras in this build? And if so... how do I use them? Searched all three pages of this thread and didn't see any details.

User avatar
Rumble
Deity
Posts: 6235
Joined: Tue Jul 01, 2008 7:48 pm

Re: MapTool 1.3 Development Build 51

Post by Rumble »

I'm seeing high memory use while working with b51.

I've been rewriting a bunch of macros from an older setup to take advantage of new goodies, and I'm noticing that the memory usage is through the roof.

My campaign file has one map (the default "grasslands" map) and 8 tokens, and memory allocation was up around 528MB out of 608MB allocated. It's been open and running most of the day, and I've been editing a lot of macros, so that may account for it. The campaign itself is 6MB. Seems a bit high for one map and a few tokens.

Double clicking on the memory bar will drop it back down considerably, but it climbs up steadily as I edit macros. If you want, I can post a link to the campaign.

Post Reply

Return to “Announcements”