Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - adhawkins

Pages: [1] 2
Beta Testing / Re: Next version (post 2.2.2) status
« on: March 09, 2007, 10:59:15 AM »
Beta is a testing phase that software sometimes goes to before release.

It's issued to a set of end users, and they're asked to use it in the way they normally would. Generally, as far as the developer is concerned the software is virtually finished at this point, so it's a way of finding any last minute bugs before it gets officially released to the masses.


General Discussion / Re: a almost tragic occurance.
« on: March 08, 2007, 11:06:26 AM »
Ah yes, that's a point  :-[



I'll get back to you on that one :)


Beta Testing / Re: Next version (post 2.2.2) status
« on: March 08, 2007, 10:32:06 AM »
Cool, look forward to it.


Templates, Layouts and Sounds / Re: web sites
« on: March 08, 2007, 09:34:07 AM »
I've just created a little site for our poker games. The layout leaves a lot to be desired as of yet, but the code is pretty much there. I have a set of 'admin' pages (that you won't be able to see) that let me create venues, leagues, seasons etc., and then I just upload the CSV export of each tourney.

It's here if anyone's interested.


Beta Testing / Re: Next version (post 2.2.2) status
« on: March 08, 2007, 09:30:51 AM »
When do you anticipate this being available? Are you still looking for people to test?


General Discussion / Re: a almost tragic occurance.
« on: March 08, 2007, 09:26:21 AM »
I've had something similar happen too, asked someone to press a button on the laptop, not realising they weren't computer literate.

The pressed the power button...

It would be good if there was a way of turning on 'Auto Save' by default. I still find myself forgetting to do it.


Suggestions / Re: Allocating prizes and rounding
« on: March 07, 2007, 11:50:11 AM »
adhawkins: You don't need to go back and change the prizes to a "fixed" amount just to deal with this issue.  You can either (a) adjust the amount of one or more of the prizes (the "Adjust by" field takes a positive or negative amount); or (b) override the amount
That (changing them to a fixed amount) is what I've done.

I think it would probably be simpler to just keep taking an amount off the first prize (the amount of the rounding) until the prize total equals the prize fund.

Ok, this might not be exactly what everyone wants, but they'd still have the option of manually editing the prize fund once the rounding had been completed.

How does that sound?


Suggestions / Allocating prizes and rounding
« on: March 07, 2007, 10:27:12 AM »
Hi all,

Not sure if this has been discussed before, but here goes.

Recently I've been running tournament very successfully using Tournament Director. However, I've found that if I let it automatically calculate prizes with rounding (I generally tell it to round prizes to the nearest £10), then it very often allocates more to prizes than there is in the prize pool.

When it does that, I make a note of the prizes it's calculated, and then manually set each place to a fixed amount, and adjust one of the payouts to account for the over-allocation.

Is this something that's known about and down to be fixed?



Or better, don't let anyone touch it except me? :)

Now I know how to make sure I don't get moved far from it, that should cover most eventualities.


Power buttons need to come with a clear, flip-up cover to prevent you from accidentally pushing it. Like you see in movies where they are about to launch a nuclear missile...
Anyone know where I can get one of these for an Acer laptop? :)


I guess I must just be lucky to have players that don't know the power button from a button on the screen marked 'Tournament' :)


The software does note when any change is made and prompts you before you do something destructive, including exiting the program. But whether or not a system shutdown triggers this is beyond my control, unfortunately.
I don't think it is, unless you've written it in a language that can't process the required windows message.

The relevant message is WM_QUERYENDSESSION:

The WM_QUERYENDSESSION message is sent when the user chooses to end the session or when an application calls the ExitWindows function. If any application returns zero, the session is not ended. The system stops sending WM_QUERYENDSESSION messages as soon as one application returns zero.

After processing this message, the system sends the WM_ENDSESSION message with the wParam parameter set to the results of the WM_QUERYENDSESSION message.

A window receives this message through its WindowProc function.

  HWND hwnd,          // handle to window
  WM_QUERYENDSESSION, // the message to send
  WPARAM wParam,      // not used
  LPARAM lParam       // logoff option
This parameter is reserved for future use.
Specifies whether the user is logging off or shutting down the system. If this parameter includes the ENDSESSION_LOGOFF value, the user if logging off. (Note that this parameter is a bit mask. To test for this value, use a bit-wise operation; do not test for equality.)
Windows 2000/XP: If this parameter is zero, the system is shutting down.

Return Values
If an application can terminate conveniently, it should return TRUE; otherwise, it should return FALSE.

I'll do a proper check this evening to ensure the 'save' prompt isn't displayed during a shutdown, but I'm pretty sure I didn't see it (although I was the other side of the room when the person concerned hit the power button on the laptop).


Locking players in their seat will not affect whether or not the table gets chosen for consolidation. You could have a locked player at every table (players who double as full-time dealers, for example). Which table would then get chosen to be eliminated? Not only that, but locking a player from moving doesn't necessarily mean the table shouldn't be consolidated.The final table designation workaround suggested by tandemrx is your best bet. If/when a feature to specify table breakdown order is implemented, it should take care of this.

Yeah, I've since thought of that. Making 'my' table the final table seems to be the best bet as you say.

As for the auto-save, I recommend placing a button on the screen as tandemrx suggested, or using the hotkey to save (Q by default - for "Quicksave"). There's also a Quicksave option on the context-menu (right-click). I'll put down a feature request for auto-saving after a major "event".
Yes, I realise not turning on auto-save in the first place was a bad move.

The reason for this comment arising was because I asked someone to operate the laptop for me one time in this first tourney, and (being a computer illiterate) they pressed the 'power' button.

Since thinking about this, I've realised that the software didn't put up a 'Do you want to save' prompt, I think it just exited. Are you catching the Windows 'shutdown' message (I think it's WM_QUERY_SHUTDOWN or something like that) and dealing with it the same way as someone closing the software?

That's more serious IMO, as it would mean (for example) all tournament info being lost if (say) a laptop decided to shut down cause of a low battery.

I realise that auto-saving would help stop this, but the software should never exit without asking you to save if there are changes you would lose.

And finally - if you see an error, send it to me. The error dialog even has a convenient "Email to Support" button to mail the error report to me (of course, you must have an email program installed and be connected to the internet). I can't help if I don't know what happened!
Agreed. I'm a software developer myself, so I realise there's nothing worse than a user telling you 'I got an error, but I can't remember what it was' :)

In future I'll try to remember to at least jot down the error message and the circumstances that appeared to cause it.

As I said previously, this was my first 'big' tourney (most others have been 2 tables max) so I was a little stressed out anyway!




You don't know my players :)

Most of them were disappearing to the bar or into side games immediately after busting out. I even had one player not tell me that he'd been eliminated at all, I found out about 10 players later when my tables wouldn't balance properly...  >:(


Suggestions / Minor gripe when busting players out
« on: November 19, 2006, 08:41:41 AM »
Hi again

Another minor gripe. When you bust players out, you have the option of restricting the list of hitmen to the people on that player's table.

However, the list still includes the player themselves.

I think I selected it by mistake and you get a warning that you can't knock yourself out, but it'd be nice if they were removed from the list.


Pages: [1] 2