Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.
Token ownership updates
I put in a bunch of the little ownership tweaks:
Person who drops a token is the initial owner
Added "All" and "Remove All" to Ownership menu
You can only change the state on an owned token
After I had updated the code to disable all the token popup menu items that are not available when a token is not owned, there were no usable items left. So I decided to try something out: You can't select a token if you don't have ownership to it. Let me know how it goes :)
LAN Server auto detect
The Connect to Server dialog has been updated. It now contains two tabs: LAN and Internet. To connect to someone on the internet (outside of your subnet) use the Internet tab and type in their IP address. If you are connecting to someone (including yourself) on your local network their server will show up in a list. The server will have the player name of the GM who started the server as the ID. Just double click the row to connect. This is also highly experimental, so let me know how it works out for you :)
The Remove All isn't working properly. I tried it with an owned token and unowned token and it didn't remove ownership of all the tokens
Feature - Have the owner of the tokens name appear next to the token name, in the information panel in brackets only on the GM's side
eg. Token A (BoB)
I live for this stuff!
Waiting for the nightly Alpha posting...
You realize we are getting use to this pace :)
Hmm, Could you provide the steps you took that shows the problem ? I've tried a couple different things and I can't reproduce it. Perhaps I'm not hitting the right sequence.
Actually, I was thinking along the same lines. I'm planning to build in hover-over info dialog popups which will include the owner list.
You realize I'm getting used to the great user testing and feedback :)
I am doing a lan connection to myself on one computer. I have it so there are tokens owned by the GM and tokens owned by the player. From the GM App I click on a token w/ownership and choose Remove All. It removes for that token, but not the rest. I also tried it with a non owned token.
Related to the non selection of non-owned tokens, you can select them by using the pointer and drawing a rectangle around it, but you still can't change any thing on it. Minor, but thought you should know...
Related to the initial ownership, the token appears as a question mark in the other info panel til clicked or moved. Minor as well...
I'll be around til late tonight if ya need more feedback... signed unofficial alpha guinea pig :)
Ooops, you're right, the code assumes one selected token. And didn't even think of the bounding box :P Got them fixed, but will just include them in the build tomorrow :)
Thanks for the testing !
Actually, I take that back: It does account for multiple selections. could you explain "for that token, but not the rest" ?
(The selection bounding box issue is fixed .. really :) )
It removes ownership for the token that is selected when I perform the 'Remove All', but not the rest
Let me just make sure we're on the same page. The Remove All and All options will only effect the tokens that are currently selected, and not any other tokens. Are you seeing that some tokens that are selected are not being updated ? Or just the ones that have not been selected (not red/white border) ?
The All-Remove All is working right, I just didn't have enough instances connected ;) I just tested with 1 GM and 2 Player connections on one computer (worked good with no noticable deficiencies...who needs others ;) ), but I would put a check next to 'All' just to be a completest and for clarity. This is what I couldn't see and since I only had one connection, I couldn't see that it picked 'All' players.
Works good, so....what's next! ;) <pant><pant>
oh good :)
The Lan feature seems to work good and is very handy...no guess work ;)
Oddly enough I (GM) can no longer delete tokens, pressing Del only unselects the token. I don't know if the token ownership changes are responsible, but it is definetly the new alpha.
Oops, my bad. Fixed, I'll push it tonight. Thanks !