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 - Corey Cooper

Pages: [1] 2 3 ... 414
1
Templates, Layouts and Sounds / Re: Clock-Help
« on: March 13, 2024, 06:05:09 AM »
Not really "fix" it, but work around it.  You'll need to set a size (width) on either the clock cell itself, or put the clock in a container with a fixed size.  For example, it looks like the clock "half" of the image is about 370 pixels.  You could set the width of the clock cell to 370, or change the contents of the clock cell to something like this:

<div style="width: 370px; overflow: hidden"><clock></div>

That should keep it a fixed size no matter its contents.

2
Templates, Layouts and Sounds / Re: Clock-Help
« on: March 11, 2024, 01:40:52 PM »
I see.  So, leave the preference "off" and you'll need to modify the Blinds cell.  Your Blinds cell is different from the default, but it will still be something like this.  You just need to add the abbreviateChips attribute:

Blinds<br><smallBlind abbreviateChips="true"> / <bigBlind abbreviateChips="true">

3
Templates, Layouts and Sounds / Re: Clock-Help
« on: March 10, 2024, 03:32:42 PM »
Preferences tab -> Currency / Numbers category:


4
Templates, Layouts and Sounds / Re: Clock-Help
« on: March 03, 2024, 10:14:40 PM »
Yes, take a look at the default layout.  It's basically done by having two property sets for the cell that displays the ante.  One property set displays the ante (usually the Default property set), the other property set is identical but doesn't display the ante.  The property set that doesn't display the ante has conditions: "Ante is non-zero": "No".  Double-negative, but basically it means use this property set when ante is zero.  When the ante is non-zero, it will skip that property set and use the Default property set.

5
Help Me / Re: Busted Player
« on: March 03, 2024, 09:50:35 PM »
Same steps as I previously posted.  Just edit the message:

The bounty on <name> has been claimed by <hitman>

6
Help Me / Re: Player Image not saving
« on: March 02, 2024, 11:53:22 PM »
Thanks for the follow-up.  That's good information to know.  Google shows a number of results for SyncTool.  Which one are you using?  Might help me to identify issues (or maybed correct them?) in the future.

7
Help Me / Re: Busted Player
« on: March 02, 2024, 11:50:55 PM »
On the Events tab:
- Press New Event button
- Select Choose a pre-defined event
- Select Player busts out
- Press OK
- Press OK

8
Help Me / Re: Dr. Neau Formula in Tournament Director
« on: March 01, 2024, 12:33:45 PM »
The "Test Range" window is a little wonky.  Like a lot of features, it was originally intended to showcase a single specific use case, but then was modified to make it more flexible.  Often that results in something being a little more complicated to use, sometimes not.  The idea of the Test Range window was originally to show the points a player would earn for each possible rank, 1 through n (n being the number of players in your tournament), for your formula.  But then it seemed logical that one might want to see how the points change when other factors change (instead of rank), so it evolved to a tool that allows you to see the points computed while one variable changes from one value to another at a certain rate.

What ends up making this window confusing, however, is that many formulas, even the simpler ones, have other variables involved that must be set in the Points for Playing window first, else you will not get the results you are looking for.  For example, here is the Test Range window testing the simple formula n-r+1:



I've set it to display the results of the formula for ranks 1 through 10.  But the results don't look right.  First place only gets 2 points, and the points start going negative at 4th place?  The reason is that n (number of buyins) was set to 2 in the Points for Playing window.  So to get the right results, I need to close the Test Range window, change the value of the buyins variable, then try the Test Range again.  I changed buyins to 10 and then opened the Test Range window again:



Much better.

9
Help Me / Re: Player Image not saving
« on: March 01, 2024, 10:50:13 AM »
Player images are imported and stored in your player database.  You'll need to get those images onto the laptop.  I would recommend backing up the database on the PC and restoring it on the laptop.  You can find the Backup and Restore features on the Database tab.

10
Help Me / Re: How to edit borders?
« on: March 01, 2024, 10:46:09 AM »
I'm using Excel 2019, which is admittedly a little out of date, but aside from some small differences the features work identically.  Excel doesn't have a size, but they both have styles with Excel having a few more styles than the TD.  But the behavior is the same.  Select a style and color, then press whatever border side you wish to apply it to.  It will change the border to that style and color, unless the border is already that style and color, in which case it will remove the border.  Make your changes so that the border in the preview section looks like you want it, press OK, it is applied.


11
Help Me / Re: Dr. Neau Formula in Tournament Director
« on: February 27, 2024, 08:10:23 PM »
You've already got the equivalent TD variables, you just need to replace them in the formula:

SQRT (buyins * defaultBuyinFee * defaultBuyinFee / totalCost) / (rank + 1.0)

If the issue is you are trying this formula in the Points for Playing Formula window and you are getting an error when you press the Test button, it's probably because you haven't given the variables any values.  During the course of the tournament, all of the variables will have a value, but of course when testing they only have a value if you provide one.

For example, a player in the tournament will have a total cost.  It won't be zero (well, it could be zero, but only if your player didn't pay anything at all to play in the tournament).  But if you don't provide a value in the Points for Playing window and try to test the formula, then the formula will be attempting to divide by the total cost, which is zero, which results in an error because you cannot divide by zero.  Just find the "totalCost" variable and give it a sample (non-zero) value, then press Test again.

12
Help Me / Re: Indivdual stats on players in season
« on: February 23, 2024, 11:52:02 PM »
The Stats tab will show the full stats of all of the players that match your stats profile.  When you say you want "one players complete stats", what do you mean?  Are you trying to view them on the Stats tab?  Are you trying to export them? 

13
Help Me / Re: How to edit borders?
« on: February 22, 2024, 09:13:09 AM »
Actually, I basically copied the border tool in Excel, so it's exactly like a spreadsheet border tool.

14
Help Me / Re: How to edit borders?
« on: February 17, 2024, 11:02:05 AM »
Open the Border window.  Set the size of border you want in the Size field.  Set the type of border you want: Solid, Dotted, Dashed, etc.  Select the color of border.  Once you've selected the border attributes, click on one of the five border buttons to apply those attributes to that particular border (or all of the borders at once if you click the corner button).  Those are toggle buttons.  If there's no border on that side, a border will be added using the properties you've selected.  If there is already a border on that side but with different properties, your selected properties will be applied, overriding the existing border.  If there is already a border on that side with the same properties, the border will be removed.  Once you've decided on your borders, press OK.

15
Help Me / Re: How to edit borders?
« on: February 15, 2024, 03:05:36 PM »
Ahh, OK.  I see now.  Now the next task is to figure out why I was NOT seeing it, but it's likely because I was using border sizes greater than 1.

I have not bought a license yet.  Could that be part of it?

No, evaluation mode is not crippled in any way.

To avoid this issue, you may need to increase your border size.  You may notice that on some borders, a size of 2 will actually render with a size of 1.  More specifically, some borders will render at 1 pixel size smaller than specified.  Explanation below.

Regarding the values not "sticking".  The border Size input does not represent the value of the border size, because it can't, as there are 4 borders and only 1 input, and the borders may all be a different size.  It is there to assign a size to a border, along with type and color.  When you open the Border window, the Size field defaults to the size of the first side that has a border, starting with top, then right, bottom, and left.  So if your top border size is 3, when you open the Border window the Size field will be preset to 3.  If your top border size is 0 (no border) and your right border size is 2, when you open the Border window the Size field will be preset to 2.  If no sides have borders, Size will default to 1.  You should be able to see from the illustration that your border sizes were retained, but the Size input will set to a value previously described.

So why do some borders render a pixel smaller?  Technically they don't, they render the correct size, but some of the background color of the cell may render a little over the border making the border look smaller.  The reason for this is a bug in Chromium.  When I modernized the TD (version 3.7) I was able to finally ditch Internet Explorer as the rendering engine and moved to Electron, which uses Chromium as its rendering engine.  Chromium is the rendering engine used in Google's Chrome browser (as well as others, such as Microsoft's Edge browser).  This was a huge leap forward and long overdue, and allows one to create much more modern layouts, using all the great stuff that has been added to HTML and CSS specifications over the years.  This also required a LOT of tweaking of TD code and rendering to keep it somewhat backwards compatible.  I did the best I could and for the most part layouts that worked in previous versions still look the same or similar in version 3.7.  While doing this, I discovered a rendering bug in Chromium.  Part of the rendering of a layout uses scaling, and in IE the only way to scale was to use the CSS "zoom" attribute.  This is a non-standard, Internet Explorer only feature, although other browsers did adopt it unofficially (it works in Chrome and Firefox, for example).  But being non-standard, it could go away at any time, and there are better ways to do it in modern browsers, and better often means it will render more accurately and faster, making the TD more efficient and run faster.  So I moved from using zoom to using modern CSS attributes to achieve the same effect.  This is where I discovered the bug.  Here's a rendering I made when working on a way around this bug that illustrates the issue:



On the left is the "Regular size" of a rendering of 6 elements, arranged in a grid, using 3 different ways to layout elements.  The second column is the same but scaled a little smaller using the "correct" way to scale it.  Tiny but noticeable lines appear between the elements.  That's the bug.  The third column is using the "old" way (zoom).  It looks fine, but again this is the old way and isn't as efficient and could go away at any time.  The final column is the same as the 2nd, the "correct" way, but with a workaround I applied.  The workaround is to shadow the background a little around some edges in order to "paint" over the lines that appear due to the bug.  It works, but the side effect is it can paint over a little of the border.  At the time I figured this was a worthwhile tradeoff, because surely Google would fix this bug soon.  Alas they have not.  But the workaround to the workaround is usually to just increase the border size where you see an issue.

I hope this helps workaround what has probably been a frustrating issue.

Pages: [1] 2 3 ... 414