search

bustiiing / blazingstars

Automatically exported from code.google.com/p/blazingstars
0 stars 0 forks source link

pre-set preflop raises doesn't work with decimal amounts #42

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. modifying the # of BBs into a decimal amount (ex. 5,4) works for the current 
session
2. closing and re-running blazing stars restore the only integer value of the 
amount (ex. 5)
3.

What is the expected output? What do you see instead?

i want blazing stars to mantain the value I want.

What version of the product are you using? On what operating system?

blazing stars version 0.9.8b (21) on mac OSX 10.6.2

Please provide any additional information below.

sorry for my english
regards

Original issue reported on code.google.com by marco.br...@gmail.com on 27 Jan 2010 at 2:59

GoogleCodeExporter commented 8 years ago 
marco,

I can't replicate this problem;  the entry fields don't allow the European way 
of
inputting decimals (i.e. 5,4 vs. 5.4), but I use the North American decimal
convention with no problem, since my PFRs are set to 2.5, 3 and 4 BB.  Does the 
North
American decimal input work for you?

Original comment by steven.h...@gmail.com on 27 Jan 2010 at 11:22

GoogleCodeExporter commented 8 years ago 
if i put 2,5 in the entry field,  it works for the current session, but the 
next time i run blazing stars it restore 
the integer value of the number I inserted.
if i put 2.5 in the entry fields, when i move to the next field it 
automatically replace it with 2.

Original comment by marco.br...@gmail.com on 28 Jan 2010 at 12:33

GoogleCodeExporter commented 8 years ago 
Ah, okay, I've figured out what's causing this:  when the Language & Text 
preference
pane is set to the Italian region (or any other European region, I presume), the
number formats change and BlazingStars can't deal with this.  Of course, now I 
have
no idea how to fix this, but perhaps the internet can help.  I'll see what I 
can do,
marco;  sorry it's taken me so long to get around to this, but I've been a bit 
busy.
 Until I can find a fix for this, you can "solve" the problem by changing your region
to a North American one or customizing your Numbers format.

Original comment by steven.h...@gmail.com on 2 Feb 2010 at 8:19

GoogleCodeExporter commented 8 years ago 
Okay, I think I've got this one licked.  I'll upload a new debug build so that 
you
can give it a try.

Original comment by steven.h...@gmail.com on 2 Feb 2010 at 9:49

GoogleCodeExporter commented 8 years ago 
thanks...i temporarily resolved it by modifyng numbers format.
i'm at the first experience with google code, where i can find the debug builds?
thanks

Original comment by marco.br...@gmail.com on 2 Feb 2010 at 10:49

GoogleCodeExporter commented 8 years ago 
marco,

Go to the home page for the project, and it's one of the featured wiki pages.

Original comment by steven.h...@gmail.com on 2 Feb 2010 at 11:02

GoogleCodeExporter commented 8 years ago 
Since there's been no further info, I'm assuming that this has been resolved.  
Let me
know if there's any further problems, marco.

Original comment by steven.h...@gmail.com on 3 Feb 2010 at 6:58

GoogleCodeExporter commented 8 years ago

Original comment by steven.h...@gmail.com on 3 Feb 2010 at 6:58