Main > Beta Testing
3.4 beta 1
Corey Cooper:
Even if you could enable the logging, I doubt it would give us anything useful. Thank you for the offer.
Lafrog:
Ok, ran the beta for the first time yesterday and here is what I found:
* No Setting window on the first run: Had to do the "ALT - SHIFT - CTRL - F12" trick
* Selecting the "Players Tab" automatically scroll down the display. ???
* The 24 hours preference is not respected on the Tournament Display... Actually the <currenttime> token does not take the pref into consideration
* The "Chip Up" column of the "Rounds" tab does not display the CHECK MARK properly.
* Trying to write to a "read only" file locks the application. I mentioned this before in the non beta version but I'll say it again anyway: I made all my "base tournament" files read-only to insure that they remain intact at all times, but when my manager forgets to do a "Save As", TD will eventually display an error dialog when attempting to auto-save the tournament. The problem here is there is no way to get out of this short of Force Quitting the app. Couldn't TD simply cancel the SAVE action and give us time to rectify the situation prior to attempting to save again? Because the dialog keeps coming back in a loop.
* Has the memory requirement much increase in this new beta? I have experience many BLACK dialog boxes and even transparent one while attempting different duties throughout my tournament. Busting out players was a biggy: Right-clicking would produce a transparent dialog, you had to guess where the "Bust player" option was and if you got lucky, you would then be presented with a black window (offering you to check other players to bust) where again you had to guess where the "OK" button was.
Later on in my tournament, I notice the whole app slowing down (countdown clock, scrolling info) where I simply decided to restart the whole thing (computer included). everything went fine after that... For information, TD is running under Windows 8, 8 Gig RAM 64 Bits, Intel Core i5-3230M CPU @ 2.60 Ghz
Lafrog
Corey Cooper:
--- Quote from: Lafrog on January 14, 2016, 02:11:52 PM ---Ok, ran the beta for the first time yesterday and here is what I found:
* No Setting window on the first run: Had to do the "ALT - SHIFT - CTRL - F12" trick
--- End quote ---
I've gotten a few reports of this. I'll be looking into how that preference may be being modified on first run. On a related note, I've added these:
- Holding down SHIFT while the application starts will "shift" all off-screen windows back onto the main display. This is the equivalent of Ctrl+Alt+Shift+F12.
- Holding down CTRL while the application starts will reset the font size back to the default.
--- Quote from: Lafrog on January 14, 2016, 02:11:52 PM ---
* Selecting the "Players Tab" automatically scroll down the display. ???
--- End quote ---
Never heard this. Can you be more descriptive?
--- Quote from: Lafrog on January 14, 2016, 02:11:52 PM ---
* The 24 hours preference is not respected on the Tournament Display... Actually the <currenttime> token does not take the pref into consideration
--- End quote ---
Yep. Bug in 3.4.b1, already fixed for 3.4.b2.
--- Quote from: Lafrog on January 14, 2016, 02:11:52 PM ---
* The "Chip Up" column of the "Rounds" tab does not display the CHECK MARK properly.
--- End quote ---
Same. bug in 3.4.b1, fixed for 3.4.b2.
--- Quote from: Lafrog on January 14, 2016, 02:11:52 PM ---
* Trying to write to a "read only" file locks the application. I mentioned this before in the non beta version but I'll say it again anyway: I made all my "base tournament" files read-only to insure that they remain intact at all times, but when my manager forgets to do a "Save As", TD will eventually display an error dialog when attempting to auto-save the tournament. The problem here is there is no way to get out of this short of Force Quitting the app. Couldn't TD simply cancel the SAVE action and give us time to rectify the situation prior to attempting to save again? Because the dialog keeps coming back in a loop.
--- End quote ---
I replied to that comment already. I've got a to-do item for addressing this. Not sure how I'm going to go-about it, because I don't think "Auto-save" should automatically disable in case of an error, as the error could be temporary. But maybe a dialog noting that since the tournament could not be saved, Auto-save will be disabled. We'll see...
--- Quote from: Lafrog on January 14, 2016, 02:11:52 PM ---
* Has the memory requirement much increase in this new beta? I have experience many BLACK dialog boxes and even transparent one while attempting different duties throughout my tournament. Busting out players was a biggy: Right-clicking would produce a transparent dialog, you had to guess where the "Bust player" option was and if you got lucky, you would then be presented with a black window (offering you to check other players to bust) where again you had to guess where the "OK" button was.
Later on in my tournament, I notice the whole app slowing down (countdown clock, scrolling info) where I simply decided to restart the whole thing (computer included). everything went fine after that... For information, TD is running under Windows 8, 8 Gig RAM 64 Bits, Intel Core i5-3230M CPU @ 2.60 Ghz
--- End quote ---
I don't think it's increased, but as I noted earlier in this thread, there's been a memory leak apparently since around 3.1. I did a lot in the upcoming beta to address it, but every path I went down turned out to be a red herring. So while changes have been made, I don't think it's going to have much effect, unfortunately. I've not personally seen the black dialogs. I don't know what to make of it. But to be completely honest, I don't know that I'll pursue any of these in the near term. After 3.4 goes out, I'm going to shift focus to trying to port the application to Chromium, and hopefully many of these issues will simply go away on their own. Might be wishful thinking, but I think IE is responsible for a lot of this.
Edit: Forgot to add: Thanks for all of the input! Very helpful.
Lafrog:
--- Quote from: Corey Cooper on January 15, 2016, 08:08:35 AM ---
--- Quote from: Lafrog on January 14, 2016, 02:11:52 PM ---
* Selecting the "Players Tab" automatically scroll down the display. ???
--- End quote ---
Never heard this. Can you be more descriptive?
--- End quote ---
Well, I have notice that when I go to the PLAYERS' tab the header scrolls out of view (shifts up to the beginning of the players' table), so I need to scroll back up to see my tabs buttons and the header.
--- Quote from: Corey Cooper on January 15, 2016, 08:08:35 AM ---
--- Quote from: Lafrog on January 14, 2016, 02:11:52 PM ---
* Trying to write to a "read only" file locks the application. I mentioned this before in the non beta version but I'll say it again anyway: I made all my "base tournament" files read-only to insure that they remain intact at all times, but when my manager forgets to do a "Save As", TD will eventually display an error dialog when attempting to auto-save the tournament. The problem here is there is no way to get out of this short of Force Quitting the app. Couldn't TD simply cancel the SAVE action and give us time to rectify the situation prior to attempting to save again? Because the dialog keeps coming back in a loop.
--- End quote ---
I replied to that comment already. I've got a to-do item for addressing this. Not sure how I'm going to go-about it, because I don't think "Auto-save" should automatically disable in case of an error, as the error could be temporary. But maybe a dialog noting that since the tournament could not be saved, Auto-save will be disabled. We'll see...
--- End quote ---
I am not saying that "AUTO-SAVE" should be disabled. but "fooling" TD into having completed the save might be a solution. That way it will attempt to auto-save again at the next cycle and allow the operator to fix the problem in the interim.
Thanks
Lafrog
shushs:
I understand that this may not be a priority, but I just wanted to add more information, in case it helps...
--- Quote from: Lafrog on January 14, 2016, 02:11:52 PM ---Ok, ran the beta for the first time yesterday and here is what I found:
<SNIP>
* Has the memory requirement much increase in this new beta? I have experience many BLACK dialog boxes and even transparent one while attempting different duties throughout my tournament. Busting out players was a biggy: Right-clicking would produce a transparent dialog, you had to guess where the "Bust player" option was and if you got lucky, you would then be presented with a black window (offering you to check other players to bust) where again you had to guess where the "OK" button was.
Later on in my tournament, I notice the whole app slowing down (countdown clock, scrolling info) where I simply decided to restart the whole thing (computer included). everything went fine after that... For information, TD is running under Windows 8, 8 Gig RAM 64 Bits, Intel Core i5-3230M CPU @ 2.60 Ghz
--- End quote ---
I can confirm that I have seen this since running the BETA also. I did purchase more RAM for my computer, and it hasn't been _as_ bad, but many buttons require me to "push" them twice. Personally, I think it is tied to the transitions. I turned them off prior to my memory upgrade, and saw some improvement, but I think the timing/logic tied to certain events is a component. (good finger pointing here) The reason, when typing / editing, just as the transitions fired, I'd lose keystrokes/clicks, then it'd be good until the next transition.
I am running an AMD A8-7410 APU / Radeon R5 with (now) 16GB RAM on Windows 10. My tournaments are smaller in size (less than 30 players) and I now lock the screen on the tournament screen. If there is anything I can do / test to help out... I'd be happy to.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version