The Tournament Director Forums

Main => Beta Testing => Topic started by: Corey Cooper on April 14, 2016, 12:41:20 AM

Title: 3.4 beta 2
Post by: Corey Cooper on April 14, 2016, 12:41:20 AM
Version 3.4.b2 is finally ready!  Please try it out and let me know what you think.

FOR ALL OF THOSE EXPERIENCING THE LOAD/SAVE BUTTON ISSUE: This beta version has a built-in replacement dialog for the system file dialog that is not working for some people.  It is designed to automatically detect that the system file dialog fails to open, and fallback on the new built-in replacement dialog.  It's not perfect but I hope it will be a suitable replacement and get those affected by this issue back in business.

Standard beta testing disclaimer:
This is a BETA release of the software.  Beta means I am not aware of any bugs, but I'd like to get some more testing done before an official release.

If you plan to participate in the beta test, backup your data first.  This can never be stated too often.  The TD can do this for you, just press the "Backup" button on the Database tab and check all options.  You should do this whether you try a beta version or not.

Below is the relevant part of the changes.txt file.

Thank you again to everyone who will participate in this test release.  Please post or email any feedback you have.


Edit: 3.4 beta 2 has been superseded by 3.4 beta 3.  See http://www.thetournamentdirector.net/forums/index.php?topic=5231.0


The Tournament Director 3.4 beta 2
Copyright (c) 2004 - 2016 Corey Cooper



Version 3.4 beta 2
======================================================================
New Features:
----------------------------------------------------------------------
- Added built-in File Browser to fix load/save buttons not functioning issue
- Added direct integration with StatsGenie.com.  Now tournaments can be uploaded to StatsGenie.com directly from the
  Tournament Director application
- Added preference to default league selections to <All> instead of league of current tournament
- Added built-in layout that doesn't change colors on alternating rounds
- Added "Convert" feature on Prizes tab to convert all percentage prizes to fixed prizes
- Added startup hotkeys:
  - Holding down the Shift key while the Tournament Director initializes will reset the Display Management preference
    and bring any off-screen windows back to the main display
  - Holding down the Ctrl key while the Tournament Director initializes will reset the font size back to the default
    size of 10
  - Holding down the Alt key while the Tournament Director initializes will reset the language back to the default
    English language catalog
- Added hotkey Ctrl+` (backtick) to maximize the current dialog (as long as the dialog is resizable)
- Revisited all dialogs and added code to ensure dialogs don't size larger than the screen when the font size is
  increased
- Checkboxes and radio buttons now scale with font
- Updated <pointsFormula> layout token to optionally use Points for Playing formula



----------------------------------------------------------------------
Bugs Fixed:
----------------------------------------------------------------------
- BUG (3.4.b1): When a column is dragged to first position and dropped the column header disappears
- BUG (3.4.b1): Event messages squeezed into tall columns of text
- BUG (3.0): Event and status messages sometimes appear in incorrect location and then move to correct location
- BUG (3.4.b1): Event and status messages do not appear in specified location
- BUG (2.0): When Auto-save is enabled and the tournament file is read-only, error messages continually appear
- BUG (3.2): Pressing ESC or Add Players button from New Player dialog when "Auto seat" is checked will display a
  dialog warning when there are no empty seats
- BUG (3.4.b1): Settings window opens offscreen if preference enabled to center dialogs on Settings or Game window
- BUG (3.2): Error shown for Automatic Prizes configuration even when configuration was valid
- BUG (3.4.b1): CurrentTime causes an error when added to the dashboard
- BUG (3.4.b1): PrizePool causes an error when added to the dashboard
- BUG (3.4.b1): Exporting from Database tab can cause error
- BUG (3.1): Rounding code uses precision of Amount to be rounded instead of nearest
- BUG (3.2): Error can occur when editing multiple transactions
- BUG: Backing up or restoring with many (1000s) of files can take a long time
- BUG (3.0): Variables can be inserted into read-only formulas by double-clicking
- BUG (3.4.b1): "Show Find on Stats tab of Settings window" preference missing from Preferences tab
- BUG (3.4.b1): "Chip Up" checkmarks don't display unless Break is edited
- BUG (3.4.b1): <startingChips> layout token displays nothing
- BUG (3.4.b1): Toolbox on Layout tab no longer adjustable
- BUG (3.4.b1): Data Stores dialog contents shrink when Active Data Store is changed
- BUG (3.4.b1): Set Chip Counts dialog renders incorrectly
- BUG (3.4.b1): Highlighting on Set Dealer Buttons dialog stopped working
- BUG (3.4.b1): <currentTime> doesn't respect "Use 24-hour clock" preference
- BUG (3.0): Buy-in time column on Players tab has time even for players who are not bought-in
- BUG (3.4.b1): Resizing Prize Suggestions Config dialog may cause an error
- BUG (2.?): Seating algorithm can seat locked players at the end of the final table, instead of randomly
- BUG (3.4.b1): Error sometimes seen when entering Players tab and Track Players is set to Simple mode
- BUG (3.4.b1): Hotkeys on player dialogs not always working



Version 3.4 beta 1
======================================================================
New Features:
----------------------------------------------------------------------
- Overhauled user interface code, which should result in fewer errors from IE
- Added preference for font size of Settings window and all dialogs (Preferences tab, Display section)
- Added Search feature to search for players on Players tab, Database tab, and Stats tab
- Added preference to allow for different player name formats for Game window and Settings window
- Changed "Increment by 1 in Simple mode" preference to "Prompt for player count when performing actions in Simple
  mode" and added sub-preference "Don't prompt for bust-out actions".  This allows returning to previous behavior of
  prompting for number of players to buy-in, rebuy, add-on, etc, while assuming only a single player when busting
  players out of the tournament (in Simple mode only).
- Increased number of places that record player movement in the tournament history (when that preference is enabled)
- Rename Columns dialogs updated to only show columns currently configured for display
- Added ability to limit the number of players displayed on the Stats tab
- Updated Export Layout to warn when images cannot be found on disk
- Added "minWinnings" attribute and [winnings] format to <inlineRankings> layout token
- Added <buyinFee> layout token
- Renamed some layout tokens for consistency: <startingChips> -> <buyinChips>, <buyinPoints> -> <pointsForBuyin>,
  <entries> -> <buyins>, <buyin> -> <buyinFee>.  Old token names will still work.
- Added "profileName" attribute to layout tokens <rebuyChips>, <rebuyFee>, <rebuyPoints>, <rebuyRake>, <rebuys>,
  <addonChips>, <addonFee>, <addonPoints>, <addonRake>, <addons>, <buyinChips>, <buyinFee>, <buyinPoints>,
  <buyinRake>, and <buyins>.
- Added "minPoints" attribute to <inlineRankings> layout token
- Updated "connector" attribute for <inlineRankings> layout token to allow for multiple connectors
- Added <image> layout token
- Added <currentdate> layout token
- Added "StartCountdown" <tdbutton> type
- Added "number" attribute to <nextbreak> token to allow specification of break #
- Added "Copy contents to all other Property Sets" feature on Cell dialog
- Added ability to move or delete multiple Screen Sets or multiple Screens on Screen Sets dialog
- Added "Swap" button on the Font dialog to swap the text and background colors
- Updated formula tooltips to show the value of the selected variable, and added a link to focus on the selected
  variable
- Added "WinCount" Overall Score variable (Stats)
- Settings window now sizes based on main display size, instead of 1024x768.
- Added "Preview" button to all exports, which displays the exported data in the default browser
- Updated Rounds spreadsheet mode so cursor left & right move between fields
- Updated Import Players Wizard for clarity
- Added buttons to Dashboard for Bust-out, Rebuy, Add-on, Add Players, and New Player
- Lots of other tweaks and improvements



----------------------------------------------------------------------
Bugs Fixed:
----------------------------------------------------------------------
- BUG (3.2): Rounding for "Average Hits" on Stats tab doesn't truncate to 2 digits past decimal point
- BUG (3.2): Clicking on the volume control track (above or below the slider) moves the slider randomly
- BUG (3.2): Chip images display via the <chips> layout token are left-aligned while the text is centered
- BUG (2.0): Error on Seating dialog when tables have been deleted.  Incorrect results when tables have been reordered.
- BUG (3.0): Error upon closing Hand Timer window
- BUG (3.3): Screen transitions preference and Tournament export preference overwrote each other (fixed in 3.3 patch 3)
- BUG (3.0): "Scan sub-folders" in Filter of Stats Profile not respected.  Refreshing stats always scans sub-folders
- BUG (3.2): Numerous bugs on Layout Conditions dialog
- BUG (2.2): Delete button is always enabled on HTML Styles dialog
- BUG (3.2): When "Remove Player from Tournament" (context menu) is selected and the player has already bought into the
  tournament, a confirmation dialog is presented before removing the player.  Even if the confirmation is canceled, the
  player is unseated.
- BUG: StatsGenie export uses 0 and 1, but should use 0 and -1
- BUG (3.2): Cheat Sheet button on Token Builder dialog closes the dialog
- BUG (3.2): Error when renaming a cell and the name of an existing cell is chosen
- BUG (3.3): Moving back and forth between Add Players and New Player adds "OK, repeat" buttons
- BUG (3.0): Pressing "List" on the Random Player dialog doesn't respect changes to criteria unless "Check" is pressed
  first
- BUG (3.2): League membership isn't shown when editing a player on the Players tab
- BUG (3.0): File.getLastModified(...) error in several places
- BUG (3.3): "Invalid seat number" error when importing players even when option to seat players not bought-in to the
  tournament is disabled
- BUG (2.0): Chip adjustment accepts negative amounts but becomes positive upon reloading a tournament
- BUG (2.0): When dragging items in the Settings window, ESC key should cancel drag, not close Settings window
- BUG (3.0): Copying a banner creates another banner with the same name
- BUG (3.2): "Clear" buttons missing from Config Files dialog
- BUG (3.2): On New Tournament dialog, if 2nd option is the last one selected, then the default tournament is cleared
  on the Config Files dialog
- BUG (3.3): Error on Last Table Balance dialog if a player listed has since been removed from the tournament
- BUG (3.2): Issues on Quick Start Wizard
- BUG (3.3): Salesperson selection missing from Add-on and Undo Add-on dialogs in Simple mode
- BUG (3.2): "Save" button doesn't enable upon loading a tournament
- BUG (3.3): Default order is incorrect on Arrange sections dialog of Controls tab
- BUG (3.3): Shift-click broken on players dialogs of Stats Profile dialog
  - used for league and season selection for filter
- BUG (IE): In IE10+, select lists don't update properly, leaving previously selected items still highlighted
- BUG (3.3): Some rows listed on same row in Clear Tables dialoh
- BUG (2.0): Import Players Wizard limits columns to 30 (changed to 100)
- BUG (3.3.b2): Error when clicking "Show Settings window tab nagivation arrows" (fixed in 3.3 patch 2)
- BUG (3.3): Error when exporting tournament with no players in it (fixed in 3.3 patch 1)
- BUG (3.3): Error on Data Stores dialog (fixed in 3.3 patch 1)
- BUG (3.3): Preference "Continue where I left off" does not load last loaded tournament (fixed in 3.3 patch 1)
- BUG (3.0): Chip values aren't abbreviated on the Dashboard
- BUG (2.5): 'this.getElement(...)' error is various places
- BUG (3.2): Overall Scores formula (Stats) variable "topTenCounts" is implemented as "listTopTenCounts"
- BUG (3.3.b1): "Tournaments" section is empty on Stats Player dialog
- BUG (3.2): <pointsformula> token should not round values
Title: Re: 3.4 beta 2
Post by: efdenny on April 17, 2016, 05:48:25 PM
Looks really good, Corey.  I can confirm that the message behavior issue has been resolved.  Thanks again!
Title: Re: 3.4 beta 2
Post by: Seitz333 on April 18, 2016, 07:15:34 PM
Downloaded and installed, have a tourney tomorrow night, will give it a try and report back.

Chuck
Title: Re: 3.4 beta 2
Post by: Corey Cooper on April 19, 2016, 12:30:58 PM
Looks really good, Corey.  I can confirm that the message behavior issue has been resolved.  Thanks again!

Thanks for the update!  Glad to hear it is fixed.
Title: Re: 3.4 beta 2
Post by: Corey Cooper on April 19, 2016, 12:31:18 PM
Downloaded and installed, have a tourney tomorrow night, will give it a try and report back.

Chuck

Thank you!  All feedback is appreciated.
Title: Re: 3.4 beta 2
Post by: Seitz333 on April 20, 2016, 01:15:21 PM
Everything went good last night, other than the black dialog screen/TD freezing. This usually happens about 2hrs into the tourney, last night it happened about 30min in (only once). Usually I can just exit TD and restart, last night I had to CTRL+ALT+DEL to bring up Task Manager to close TD, then restart TD.

Chuck
Title: Re: 3.4 beta 2
Post by: Corey Cooper on April 20, 2016, 08:50:33 PM
Everything went good last night, other than the black dialog screen/TD freezing. This usually happens about 2hrs into the tourney, last night it happened about 30min in (only once). Usually I can just exit TD and restart, last night I had to CTRL+ALT+DEL to bring up Task Manager to close TD, then restart TD.

Chuck

Thanks for the update!  Wish I could explain the black screens.  More incentive to get away from IE.
Title: Re: 3.4 beta 2
Post by: RichieD on April 24, 2016, 05:22:57 PM
Hi Corey,

Well.. I finally decided to try the beta...

All seemed good right up until TD froze..  :(

The point at which everything just froze was when the "Suggest Player Movement" dialog appeared, the mouse pointer continually changed icon from busy to arrow etc., no dialog buttons were active and the TD application became unresponsive (timer stopped etc) - the only escape was to use task manager and zap the TD process.. then restart and "rebuild" the last state of the tournament  :-X

TD is normally so very reliable.. in the 4 years or so that I've used it, this is the FIRST time it has let me down.

My TD system, is a virtual machine (VMWARE) running Windows 7 Home Premium (64-bit) with all Microsoft patches up to 23/04/2016.

My observations on v3.4 beta 2:
1) the mouse does seem to change more frequently between pointer and the busy icon and it seems the TD application is "busier" than in previous versions.
2) keyboard actions are occasionally ignored and it sometimes needs a couple of attempts to get things to work (I'm used to typing ahead when buying in players etc.. I can't do this now as I have to wait for dialogs to render and display etc).

Let me know it there's anything evidential I can provide you.. otherwise i'll be returning to v3.3 !! 
Title: Re: 3.4 beta 2
Post by: mcfrojd on April 24, 2016, 08:23:34 PM
I run a small tournament today, with no problems.
Will run a bitter one on Thursday, will have more to report then.
Title: Re: 3.4 beta 2
Post by: Corey Cooper on April 26, 2016, 03:46:06 PM
Hi Corey,

Well.. I finally decided to try the beta...

All seemed good right up until TD froze..  :(

The point at which everything just froze was when the "Suggest Player Movement" dialog appeared, the mouse pointer continually changed icon from busy to arrow etc., no dialog buttons were active and the TD application became unresponsive (timer stopped etc) - the only escape was to use task manager and zap the TD process.. then restart and "rebuild" the last state of the tournament  :-X

TD is normally so very reliable.. in the 4 years or so that I've used it, this is the FIRST time it has let me down.

My TD system, is a virtual machine (VMWARE) running Windows 7 Home Premium (64-bit) with all Microsoft patches up to 23/04/2016.

My observations on v3.4 beta 2:
1) the mouse does seem to change more frequently between pointer and the busy icon and it seems the TD application is "busier" than in previous versions.
2) keyboard actions are occasionally ignored and it sometimes needs a couple of attempts to get things to work (I'm used to typing ahead when buying in players etc.. I can't do this now as I have to wait for dialogs to render and display etc).

Let me know it there's anything evidential I can provide you.. otherwise i'll be returning to v3.3 !! 

Wish I knew what was causing this.  I would be very interested to know if moving back to 3.3 definitively fixed it.
Title: Re: 3.4 beta 2
Post by: RichieD on April 26, 2016, 06:45:18 PM
Hi Corey,

Well.. I finally decided to try the beta...

All seemed good right up until TD froze..  :(

The point at which everything just froze was when the "Suggest Player Movement" dialog appeared, the mouse pointer continually changed icon from busy to arrow etc., no dialog buttons were active and the TD application became unresponsive (timer stopped etc) - the only escape was to use task manager and zap the TD process.. then restart and "rebuild" the last state of the tournament  :-X

TD is normally so very reliable.. in the 4 years or so that I've used it, this is the FIRST time it has let me down.

My TD system, is a virtual machine (VMWARE) running Windows 7 Home Premium (64-bit) with all Microsoft patches up to 23/04/2016.

My observations on v3.4 beta 2:
1) the mouse does seem to change more frequently between pointer and the busy icon and it seems the TD application is "busier" than in previous versions.
2) keyboard actions are occasionally ignored and it sometimes needs a couple of attempts to get things to work (I'm used to typing ahead when buying in players etc.. I can't do this now as I have to wait for dialogs to render and display etc).

Let me know it there's anything evidential I can provide you.. otherwise i'll be returning to v3.3 !! 

Wish I knew what was causing this.  I would be very interested to know if moving back to 3.3 definitively fixed it.
Reverted back to v3.3, ran a tournament tonight and had no issues.. none of the mouse pointer rapidly changing between icons.. and no lockup. I'll keep you informed of any developments!
Keep up the good work Corey, it is appreciated.  :)
Title: Re: 3.4 beta 2
Post by: NCPL on April 27, 2016, 11:40:45 PM
Ran a 6 hour tournament last night using the new beta version. Happy to report no problems what so ever. I am running it on Windows 10
Title: Re: 3.4 beta 2
Post by: Corey Cooper on April 30, 2016, 09:37:55 PM
Ran a 6 hour tournament last night using the new beta version. Happy to report no problems what so ever. I am running it on Windows 10

Thanks for the info!
Title: Re: 3.4 beta 2
Post by: Corey Cooper on April 30, 2016, 09:39:00 PM
Hi Corey,

Well.. I finally decided to try the beta...

All seemed good right up until TD froze..  :(

The point at which everything just froze was when the "Suggest Player Movement" dialog appeared, the mouse pointer continually changed icon from busy to arrow etc., no dialog buttons were active and the TD application became unresponsive (timer stopped etc) - the only escape was to use task manager and zap the TD process.. then restart and "rebuild" the last state of the tournament  :-X

TD is normally so very reliable.. in the 4 years or so that I've used it, this is the FIRST time it has let me down.

My TD system, is a virtual machine (VMWARE) running Windows 7 Home Premium (64-bit) with all Microsoft patches up to 23/04/2016.

My observations on v3.4 beta 2:
1) the mouse does seem to change more frequently between pointer and the busy icon and it seems the TD application is "busier" than in previous versions.
2) keyboard actions are occasionally ignored and it sometimes needs a couple of attempts to get things to work (I'm used to typing ahead when buying in players etc.. I can't do this now as I have to wait for dialogs to render and display etc).

Let me know it there's anything evidential I can provide you.. otherwise i'll be returning to v3.3 !! 

Wish I knew what was causing this.  I would be very interested to know if moving back to 3.3 definitively fixed it.
Reverted back to v3.3, ran a tournament tonight and had no issues.. none of the mouse pointer rapidly changing between icons.. and no lockup. I'll keep you informed of any developments!
Keep up the good work Corey, it is appreciated.  :)

If you get the urge, and have the time, try the beta version again and see if you get the same results.  It would be good to know if the behavior is reproducible.  I appreciate your efforts regardless.
Title: Re: 3.4 beta 2
Post by: efdenny on May 01, 2016, 10:15:20 AM
Happy to report no problems at all with the software during a 9 hour tournament yesterday, running on Windows 10.
Title: Re: 3.4 beta 2
Post by: Corey Cooper on May 03, 2016, 11:30:30 AM
Happy to report no problems at all with the software during a 9 hour tournament yesterday, running on Windows 10.

Awesome, thanks for the info.  :)
Title: Re: 3.4 beta 2
Post by: Ben Jennings on May 23, 2016, 12:41:33 PM
Hi Corey,

Started having problems with the save/load buttons not working again in the previous version I was using so have just downloaded 3.4 and they do seem to be working now. I recreated the last tournament I ran and went through all the motions with no problems, so I think it's all good   :D

On a side note, I noticed that when bringing up a menu list by right-clicking something (I only did this on the layout section) the menu wasn't bound by the edges of the screen as would normally happen. Just thought I would mention it...

cheers for all the hard work
Ben
Title: Re: 3.4 beta 2
Post by: Corey Cooper on May 26, 2016, 04:08:55 PM
Good to know, Ben!  Thanks!
Title: Re: 3.4 beta 2
Post by: jodybingo on June 17, 2016, 10:47:32 AM
I think I'll install my TD and start playing around with it again. I haven't run a tournament in a few years and haven't played either but I enjoyed working with TD. I'll do the beta this weekend and take some time to familiarize myself with it again and hopefully get active on the forums again!
Title: Re: 3.4 beta 2
Post by: Corey Cooper on June 17, 2016, 10:51:23 AM
I think I'll install my TD and start playing around with it again. I haven't run a tournament in a few years and haven't played either but I enjoyed working with TD. I'll do the beta this weekend and take some time to familiarize myself with it again and hopefully get active on the forums again!

Nice to have you back, jodybingo!
Title: Re: 3.4 beta 2
Post by: jodybingo on July 01, 2016, 01:52:37 PM
Hi Corey.
The Main Window looks great! (compared to the main window in previous versions).
I had a few ideas in mind before I stopped working in poker and I'll run them by you.
Towards the end of my poker career I was going to suggest allowing a way for players to leave a deposit on tournaments. While at Playground Poker Club we had several tournaments where the buy-in was over $3000 and $5000. We allowed people to make payments on the tournament and kept a spreadsheet for this. I was hoping, one day, TD would be able to do this as well. At the club we had one computer running our tournaments and always had a laptop at the tourney desk with TD running just in case. If TD would allow players to leave deposits on a tournament we could keep the laptop running the major tourney and enter in amounts. With the current version there is kind of a workaround. I am able to use a rebuy or an add-on to achieve this. I override the rebuy or add-on amount to reflect a theoretical payment and the amount paid shows up on the Players Tab. Then I came across an issue with what I tried to do. The receipts don't print any rebuy or add-on information purchased at the time of buy-in. So I was unable to print the amount paid to date. If possible,  a menu when right-clicking that would print player information (table/seat, buy-in, rebuy, add-on info). We had tournaments where players could purchase an initial add-on or rebuy before the start of the tournament and being able to sell this at the tournament counter would offer a bit more control over the number of add-ons/rebuys purchased. Or dealers would also handle less money at the table (the player could give the receipt and give the chips for add-ons/rebuys if it is shown on the receipt).
I'll be back when I explore the beta version a bit deeper!
Title: Re: 3.4 beta 2
Post by: jodybingo on July 03, 2016, 02:29:55 PM
From the Player's Tab after a Buy-In. TD also crashed and completely shut down.
Title: Re: 3.4 beta 2
Post by: Corey Cooper on July 05, 2016, 04:30:17 PM
Hi Corey.
The Main Window looks great! (compared to the main window in previous versions).
I had a few ideas in mind before I stopped working in poker and I'll run them by you.
Towards the end of my poker career I was going to suggest allowing a way for players to leave a deposit on tournaments. While at Playground Poker Club we had several tournaments where the buy-in was over $3000 and $5000. We allowed people to make payments on the tournament and kept a spreadsheet for this. I was hoping, one day, TD would be able to do this as well. At the club we had one computer running our tournaments and always had a laptop at the tourney desk with TD running just in case. If TD would allow players to leave deposits on a tournament we could keep the laptop running the major tourney and enter in amounts. With the current version there is kind of a workaround. I am able to use a rebuy or an add-on to achieve this. I override the rebuy or add-on amount to reflect a theoretical payment and the amount paid shows up on the Players Tab. Then I came across an issue with what I tried to do. The receipts don't print any rebuy or add-on information purchased at the time of buy-in. So I was unable to print the amount paid to date. If possible,  a menu when right-clicking that would print player information (table/seat, buy-in, rebuy, add-on info). We had tournaments where players could purchase an initial add-on or rebuy before the start of the tournament and being able to sell this at the tournament counter would offer a bit more control over the number of add-ons/rebuys purchased. Or dealers would also handle less money at the table (the player could give the receipt and give the chips for add-ons/rebuys if it is shown on the receipt).
I'll be back when I explore the beta version a bit deeper!

Couldn't you just buy the player into the tournament for however much they deposited, and then increase their buy-in for each additional deposit?  You could use the "Paid in full" box to indicate that they were fully paid up.  For example, buy the player into the tournament for $500 when they make the first payment, then increase their buy-in to $1500 when they paid the next $1000.

Or are you wanting to keep a ledger of sorts?  I mean, you want the TD to record each payment, where you could look back and see that someone paid $500 on this date, and then another $1000 on that date, etc.?
Title: Re: 3.4 beta 2
Post by: Corey Cooper on July 05, 2016, 04:37:45 PM
From the Player's Tab after a Buy-In. TD also crashed and completely shut down.

Well that sucks.  As obvious as it looks, it sounds like IE ran out of memory (probably your PC had plenty of memory, but the amount allocated by IE wasn't enough).  I know there is a memory leak of some kind.  I spent a good amount of time last year trying to figure out where it was, but eventually decided I had to move on.  The leak has been there since at least version 3.1, if I recall correctly, so I figured it wasn't crucial to fix it ASAP.  If you see this again, take a look at the mshta.exe process in the task manager and see how big the memory size is.  My development version starts up at about 100 to 150MB, and will go up over time, particularly if screens in the main window change often.  Once it gets to over 1GB in size (can't remember exactly where, maybe 1.7GB?) it may become unresponsive and/or crash.
Title: Re: 3.4 beta 2
Post by: jodybingo on July 05, 2016, 10:00:50 PM
//Couldn't you just buy the player into the tournament for however much they deposited, and then increase their buy-in for each additional deposit?  You could use the "Paid in full" box to indicate that they were fully paid up.  For example, buy the player into the tournament for $500 when they make the first payment, then increase their buy-in to $1500 when they paid the next $1000.

Or are you wanting to keep a ledger of sorts?  I mean, you want the TD to record each payment, where you could look back and see that someone paid $500 on this date, and then another $1000 on that date, etc.?//

 When I was in poker I was hoping to be able to look back at their payments but even while recording them in a spreadsheet the need to do so never came up. I hadn't thought about just using the buy-in option though.

//Well that sucks.  As obvious as it looks, it sounds like IE ran out of memory (probably your PC had plenty of memory, but the amount allocated by IE wasn't enough).  I know there is a memory leak of some kind.  I spent a good amount of time last year trying to figure out where it was, but eventually decided I had to move on.  The leak has been there since at least version 3.1, if I recall correctly, so I figured it wasn't crucial to fix it ASAP.  If you see this again, take a look at the mshta.exe process in the task manager and see how big the memory size is.  My development version starts up at about 100 to 150MB, and will go up over time, particularly if screens in the main window change often.  Once it gets to over 1GB in size (can't remember exactly where, maybe 1.7GB?) it may become unresponsive and/or crash.//

 I had to screenshot the error message because there wasn't an option to copy to clipboard. Not sure when you decided to remove that option but I got the message through. I'll have time tomorrow after work to play around after work so I'll see if I can recreate the crash.

I tried looking on the forums and in the help files but couldn't find what I was looking for... can you explain to me the itemN and amountN work when exporting to reciepts?
Thanks
- Jody
Title: Re: 3.4 beta 2
Post by: Corey Cooper on July 07, 2016, 07:41:25 PM
Quote
I had to screenshot the error message because there wasn't an option to copy to clipboard. Not sure when you decided to remove that option but I got the message through

That option has not been removed.  It's possible you saw a different error message.  The TD tries to capture error messages, but IE isn't always cooperative.

Quote
I tried looking on the forums and in the help files but couldn't find what I was looking for... can you explain to me the itemN and amountN work when exporting to reciepts?

"item" is a generic term for a line-item on a receipt.  Anything that adds up to the total value.  For example, for a buy-in there will be a rebuy cost (the fee) and possibly a bounty chip cost.  For a rebuy, there will be a be a rebuy cost (again, the fee) and again, possible a bounty chip cost.  For an add-on there will only be an add-on cost.

The idea was to make these generic terms, instead of "buyin" and "rebuy" and "addon" which would necessitate different templates for different types of receipts.  Of course, it seems obvious I could have just gone with "fee", but there's also the bounty chip cost, which may or may not be on a receipt.  Further, the code was written to allow additional fees as well, in case there were other line items that needed to be represented (although I'm not sure that is exposed anywhere in the code).

Bottom line, if you're hosting a tournament all you need are line0, amount0 (for the buy-in/rebuy/add-on fee) and possibly line1, amount1 (for the bounty chip) in your receipt template to represent the fees/costs to a player.
Title: Re: 3.4 beta 2
Post by: jodybingo on July 25, 2016, 02:03:38 PM
Hi Corey.
Not sure if it's me or...I played with a receipt printer this weekend and can't get an image to print. The generated HTML shows an image on the top of the receipt but the printer (Epson TM IV-88) gives me an X (broken link). I tried placing the image in the images folder, templates folder and eslewhere on the hard drive. I used the <datastore>/images and <datastore>/template. I wrote out the full URL of the image and it still won't print the image.
Title: Re: 3.4 beta 2
Post by: jodybingo on July 25, 2016, 10:19:24 PM
To add a bit more information.
I'm using Dreamweaver to build a receipt. Using the beta version (and checking the HTML code after export) I see the <datastore> token is inserted even if I didn't use it to begin with. When using the same receipt template with the older version the image (logo) is printing fine.
Title: Re: 3.4 beta 2
Post by: Corey Cooper on July 25, 2016, 11:52:42 PM
What does the template look like and what does the resulting HTML look like?  The image (<img ...>)tag should be enough to see what might be going on.
Title: Re: 3.4 beta 2
Post by: jodybingo on July 26, 2016, 02:18:05 PM
The code from the template and the output file is identical (see below). At first, from my PC (and the official version) the print settings within IE had the "print background colors and images" unchecked. After activating that feature the image printed on the receipt. From my laptop (and the beta version) I had to activate that option in IE but the images still aren't printing.

Dreamweaver gives me this in the template:
<tr>
          <td align="center" style="font-size: 36pt"><nobr><img src="../images/express.jpg" width="240" height="174"></nobr></td>
        </tr>
And from the older version of TD (on another PC it prints fine.

Output gives me this
<tr>
          <td align="center" style="font-size: 36pt"><nobr><img src="../images/express.jpg" width="240" height="174"></nobr></td>
        </tr>
Title: Re: 3.4 beta 2
Post by: jodybingo on July 26, 2016, 02:25:40 PM
Within minutes of my last post....the image is printing when I enter the full URL of the image (C:\Users\jodyb\Documents\The Tournament Director 2\Data\images/express.jpg), but not with the <datastore> token or the
<img src="../images/express.jpg" width="240" height="174"> html
Title: Re: 3.4 beta 2
Post by: Corey Cooper on July 26, 2016, 09:42:21 PM
That's basically what I saw.  Full URL works.  Relative URLs should work too, but of course are relative to the receipt file's location.

The <datastore> token isn't being replaced, but I'm not sure it was ever supported in receipt templates.  I can certainly add it.  I have a to-do to make a set of the more common/generic tokens work for every export (more consistency).
Title: Re: 3.4 beta 2
Post by: shushs on August 12, 2016, 06:01:44 PM
The answer may be in the forums... but is there a way to roll back to 3.4beta1? The 'key press' stutter, and having to click multiple times (some times) is just not conducive to running a tournament. I have been struggling for a while, but it finally has me beaten. 
Title: Re: 3.4 beta 2
Post by: Corey Cooper on August 15, 2016, 03:28:03 PM
If you want to install beta 1, just follow the same link at the start of this thread, but change the b2 to b1:

http://www.thetournamentdirector.net/TournamentDirector34b1.exe

The earlier beta is still there for now.  I usually don't allow a rollback in this way just to keep people moving forward, but if you want to give this a try, go for it.  If it works, please share with us, at least I'd have something more concrete to work with.  But this issue is not a beta version issue - it affects all versions of the TD.  In fact, it will affect any HTML application that still uses Internet Explorer.  It's really a Windows 10 issue.
Title: Re: 3.4 beta 2
Post by: shushs on August 15, 2016, 03:53:27 PM
Well, if it is Windows 10 that is the culprit, then please excuse my finger pointing. I've had and used your product for quite some time, and I am extremely happy with it. I will see if I can dredge up an older Windows machine and test b2 out on it.
Title: Re: 3.4 beta 2
Post by: Akentut on September 15, 2016, 01:01:08 PM
The answer may be in the forums... but is there a way to roll back to 3.4beta1? The 'key press' stutter, and having to click multiple times (some times) is just not conducive to running a tournament. I have been struggling for a while, but it finally has me beaten.
I  have the same issue. I wiped my AIO Dell, Since I'm MS Cert, I have a full new copy of Win 10 Pro 1607. Which I did a format and install, only installed antivirus and then Ver. 3.4b2 and still have the keyboard or even mouse click issue. Sometimes having to click the mouse 3 or 4 times for something to happen. Even the touch screen has the same issue. I'll install b1 and see if that helps. This is about as clean an install as I can do. I'll report back.

Tnx
Title: Re: 3.4 beta 2
Post by: Akentut on September 20, 2016, 10:05:46 PM
Update on keyboard/Mouse pause and stutter. I found while using Actiontec screen beam, which I use to broadcast my PC screen to a TV in another room as I run two tables, the software is running a file that uses approx. 15% CPU time. I disabled it after my screen was active and the problem almost went away completely. I have since updated the Actiontec firmware and software and have a major improvement in the keyboard and mouse actions. Hopefully this will be the end of it. Or I can just use an HDMI cable from my PC to the other TV to solve the CPU usage by that software.

The file is Awdtsp.exe which needs to be running in order to broadcast the video.
Title: Re: 3.4 beta 2
Post by: Corey Cooper on September 21, 2016, 10:03:17 AM
Very interesting.  Thank you for the followup on this.  Although it seems unlikely that this same program is the ultimate cause of the problem - more likely it is just exacerbating it.  Helpful nonetheless.  Thanks!
Title: Re: 3.4 beta 2
Post by: Akentut on October 05, 2016, 03:32:29 PM
Well that didn't fix it. Now I have had numerous crashes when the timer counts down to 00:01 then stops and locks up the program. I does restart when I reload as autosave was on. Working on uninstalling KB3194496 that was just installed to see if that's fixed.
Title: Re: 3.4 beta 2
Post by: Akentut on October 05, 2016, 10:06:31 PM
Success! I uninstalled the latest cumulative update kb3194496 and all is running. No stutter on keyboard entries or mouse clicks and the freeze at one second is also gone. Seems there is numerous files that are updated with the last update. I don't think I'll try to find the one or ones that are culprit, but the list is very large.

It maybe in your best interest to see what files TTD is using and go from there. I used to be a programmer and used a lot of DLL files from MS, but I don't know what ones you use. I've an idea that one of those has changed or been updated. You can get the list from http://www.microsoft.com/?kbid=3194496


 (http://www.microsoft.com/?kbid=3194496)Alan
Title: Re: 3.4 beta 2
Post by: Akentut on October 06, 2016, 01:23:22 PM
Yeah! Ran tournament for 3 1/2 hours and no failures, freezes or slow keyboard/mouse. Everything back to normal, sound, setup screen, pause, etc. Also disabled windows updates, by going into services, find wuauserv and disabled.
Title: Re: 3.4 beta 2
Post by: Corey Cooper on October 10, 2016, 03:11:01 PM
Thanks for the update!  I'll uninstall KB3194496 and see what happens.
Title: Re: 3.4 beta 2
Post by: jodybingo on October 25, 2016, 04:39:44 PM
Can you build in a dialog that pops up if a user tries to buy-in more than 1 player at a time? One of my guys here accidentally selected all the players in the DB and added to the tourney and he kinda got a shock when the thermal printer spit out 200 receipts!
It was good for aq laugh but took a bit of work to remove the extra names.
Thanks
Title: Re: 3.4 beta 2
Post by: Corey Cooper on October 27, 2016, 10:56:53 AM
A preference to warn if more than N buy-ins (or rebuys or add-ons) are purchased at once?  Probably not too difficult.  I'll look into it.
Title: Re: 3.4 beta 2
Post by: RichieD on November 06, 2016, 05:33:57 PM
 :( :( :(
v3.4 beta 2 has let me down once again..
This time it froze part way through a screen transition, interestingly right clicking on the frozen display brought up a dialog for TD selections, but any selections weren't satisfied.
From the task manager the mshta process was >1Gb of Private working set memory.. and INCREASING even whilst frozen.
The only way out was to kill the process and re-start TD.

I've had VERY similar instances of freezing on 3.4 B2 after approx. 4.5hrs of operation, so I'd be inclined to suggest that there might be a memory leak somewhere!
The problem I now have, is that I'd like to go back to v3.3 (which NEVER crashed/froze) but the tournament files aren't compatible..
Any easy fix to allow 3.4B2 files to revert to v3.3???

I'm using Win 7 x64

Title: Re: 3.4 beta 2
Post by: Corey Cooper on November 06, 2016, 06:35:52 PM
Sorry to hear it RichieD.  Yes, there is definitely a memory leak, and if you'll dig back through this thread you'll see that I actually identified that it has been there since version 3.1.  At the time it seemed like it should be an easy thing to identify since I was able to pinpoint the version in which it was introduced, but in practice it has been much more difficult.  I am able to say with pretty high confidence that screen transitions are either the source of the leak, or highly exacerbate the problem.  Therefore I suggest that if your layout changes screens often, to change layouts or reduce the frequency of screen changes.  Personally, I wouldn't change screens more than once per minute for an average tournament.  At least until I am able to fix the leak.

I don't think going back to 3.3 will help.  The memory leak could possibly be worse in 3.4.b2, but I don't know.  I haven't done any testing around that specific issue.
Title: Re: 3.4 beta 2
Post by: RichieD on November 07, 2016, 04:42:05 PM
I don't think going back to 3.3 will help
In the time I've had v3.3 (since release!) it has NEVER crashed or frozen (it's been a bit slow on occasions..).
In the month or so I've used 3.4b2, it has frozen five times  :(
My screen transitions/layout etc haven't changed since v3.3 and screen changes/transitions are approx. 3 minutes apart!
Any chance of including some debugging to the event log to help in finding the miscreant code?!
Title: Re: 3.4 beta 2
Post by: Corey Cooper on November 08, 2016, 05:01:10 PM
That's a lot different from my testing, but I'm sure it's valid.  I just took another stab at the memory leak issue, assuming it has to do with screen transitions, and by removing part of the transition code, the memory leak was slowed down in a huge way.  It didn't get rid of it entirely, but it looked pretty promising.  I haven't yet had time to investigate further, but if this doesn't allow me to actually fix it, I might be able to add an option to truly disable screen transitions, and tackle it that way, at least for the time being.

FYI, screen changes always occur using screen transitions, even if they are disabled.  Basically, if you disable screen transitions, it's still the same code path, it's just that the transitions are "instant".  That makes the code easier and more consistent.  I might just code in a separate path that doesn't use the transition code.  Anyway, more investigation is needed...
Title: Re: 3.4 beta 2
Post by: jklaver on November 09, 2016, 03:49:59 PM
Do you have any date for the final version of TTD (4 version) after beta v3.4 beta 2?
Title: Re: 3.4 beta 2
Post by: Corey Cooper on November 09, 2016, 04:03:03 PM
Well RichieD, I will have to thank you.  A few months ago I tried to tackle this memory leak and went down a few rabbit holes before giving up.  Your post convinced me to pause on current work and take another quick look.  This time appears to be a different story.  And I hope I'm not celebrating prematurely.  But a little change to the screen changing code has produced dramatic results.

To give you an example, I have a saved tournament (which is complete) with a layout that changes the screen every 3 seconds.  If I load up that tournament and just let the application do its thing (I don't interact with it), the memory size starts at about 100MB and will get well over 1GB within 5 minutes.  As a control, I repeated this experiment but locked the screen so no screen changes occur.  The memory size started again at 100MB and did not meaningfully change in that same time period.  This tells me the screen changes are a big factor in the memory leak.  Or maybe more accurately that the screen changes are a big memory leak (but there are probably others).

After making my changes, I've now had the application running for nearly 45 minutes, changing screens every 3 seconds, and the memory size is currently at 109MB.  That's an enormous improvement.  Plus, manual screen changes occur noticeably faster and feel a lot more responsive.

This is a limited test, and it didn't include other actions, but it still feels like a pretty big win.  Thanks for your post!
Title: Re: 3.4 beta 2
Post by: Corey Cooper on November 09, 2016, 04:03:51 PM
Do you have any date for the final version of TTD (4 version) after beta v3.4 beta 2?

"When it's done" unfortunately.  This one has dragged quite a bit but there has been a lot of fundamental change.  The sooner the better, but it's not quite ready yet.
Title: Re: 3.4 beta 2
Post by: RichieD on November 10, 2016, 11:46:42 AM
This is a limited test, and it didn't include other actions, but it still feels like a pretty big win.  Thanks for your post!
You are very welcome!  :D
Keep up the good work..
Title: Re: 3.4 beta 2
Post by: Corey Cooper on November 10, 2016, 02:39:23 PM
So the test has been running now for nearly 24 hours.  Changing screens every 3 seconds.  Memory size is just under 400MB.  So there's still a leak, but comparatively it is pretty small and really unlikely to affect anyone anymore.  Let's hope that was the only big one!
Title: Re: 3.4 beta 2
Post by: Chowda on November 22, 2016, 05:44:16 PM
Hi Corey... been running Version 2.5.14 for awhile with no issues and then today while getting ready to build a tournament for Friday it seems the load button is not working. I even changed my computer to go back to a recovery point when I knew it was working and still nothing. I see there is this version 3.4 beta 2 that we can load but it seems temporary (30 day trial)? I use my software every 3 weeks and reply on my program, is my Version 2.5.14 obsolete? Do I need to pay for a different version?

Please HELP!
Title: Re: 3.4 beta 2
Post by: Corey Cooper on November 23, 2016, 12:09:34 PM
Hi Chowda,

Unfortunately there's little I can do about the load/save button issue until I port the software to a new framework.  Version 3.4 beta 2 has a workaround in it, in the form of a file dialog I coded myself.  It's not great, but it does get the job done.

Version 3.0 was released over 5 years ago, and there have been 6 versions released since (with a new version in the works), so in a sense, yes, version 2.5.14 is obsolete.  It is still available for download for those people who still hold a v2 license, because I don't want to force anyone to upgrade.  But there is no work going into version 2 and with ongoing work in with version 3 I can't support version 2 anymore and haven't supported it in years.  Sorry, it's just impossible for me to support both versions.
Title: Re: 3.4 beta 2
Post by: jodybingo on November 23, 2016, 01:48:44 PM
Hi Corey.
Would it be possible to allow players to Add-On or Rebuy at buy-in (on the same dialog as add players/new players)?
Thanks,
Jody
Title: Re: 3.4 beta 2
Post by: Corey Cooper on November 28, 2016, 01:47:08 PM
Sure, anything's possible.  :)

I had a request some time ago for something similar.  I think I referred to it as a buy-in "console".  I still have it in my notes as a "big ticket" item, if I can ever get to it.  Here's the post I found: http://www.thetournamentdirector.net/forums/index.php?topic=3316.0

I'd really love to stop having to work on fixes and workarounds to issues outside of the application's control and get back to providing features and needed functionality...

Title: Re: 3.4 beta 2
Post by: jodybingo on November 28, 2016, 04:55:43 PM
Thanks Corey!
On a side note, it's too bad the TD Forums don't have a like button like Twitter and FB
Title: Re: 3.4 beta 2
Post by: Corey Cooper on December 03, 2016, 11:17:48 PM
I agree.  I don't really do FB or Twitter but liking would serve to tally popularity of a feature and also to "follow" it.  Maybe SMF will incorporate that in a future version.
Title: Re: 3.4 beta 2
Post by: Seitz333 on December 08, 2016, 10:23:47 AM
That's a lot different from my testing, but I'm sure it's valid.  I just took another stab at the memory leak issue, assuming it has to do with screen transitions, and by removing part of the transition code, the memory leak was slowed down in a huge way.  It didn't get rid of it entirely, but it looked pretty promising.  I haven't yet had time to investigate further, but if this doesn't allow me to actually fix it, I might be able to add an option to truly disable screen transitions, and tackle it that way, at least for the time being.

FYI, screen changes always occur using screen transitions, even if they are disabled.  Basically, if you disable screen transitions, it's still the same code path, it's just that the transitions are "instant".  That makes the code easier and more consistent.  I might just code in a separate path that doesn't use the transition code.  Anyway, more investigation is needed...

FYI I ran a tourney on Tuesday and disabled screen transitions and still received the black screen and tourney locked up. Had to quit and restart TD.

Chuck
Title: Re: 3.4 beta 2
Post by: Corey Cooper on December 08, 2016, 01:56:52 PM
But does your layout change screens?  Or does it sit on a single screen throughout the entire tournament?
Title: Re: 3.4 beta 2
Post by: Seitz333 on December 09, 2016, 09:01:55 AM
It changes every 40 min. Each level is 20 min, and after 2 levels the tourney pauses for dealer changes.

Chuck
Title: Re: 3.4 beta 2
Post by: Corey Cooper on December 09, 2016, 04:17:30 PM
Hmm, that doesn't seem to be related.  All I can say at this point is try the next beta version when I (FINALLY) finish it and let's see if anything changes.
Title: Re: 3.4 beta 2
Post by: Al1_fr78 on December 14, 2016, 06:04:13 AM
Is 3.4 an issue to slow/typing problems with W10 on version 3.3 ? If it should, I'm interesting in testing, please let me know.
Title: Re: 3.4 beta 2
Post by: Corey Cooper on December 14, 2016, 09:43:03 AM
Is 3.4 an issue to slow/typing problems with W10 on version 3.3 ? If it should, I'm interesting in testing, please let me know.

No, unfortunately I don't think so.  But I'm still investigating the issue.  If there's anything that can be done to mitigate the issue from within the code, it will definitely make it into the beta.