Home | Blog | Software | Reviews and Features | Forum | Help | Donate | About us
topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • December 08, 2016, 09:51:33 PM
  • Proudly celebrating 10 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: Errors when .ini number format doesn't match current regional settings  (Read 813 times)

sba

  • Member
  • Joined in 2007
  • **
  • default avatar
  • Posts: 51
    • View Profile
    • Donate to Member
Hi,

I'm hereby resurrecting an old thread about the same topic.

The current implementation of ScreenShot Captor yields fatal errors such as:

---------------------------
Screenshot Captor
---------------------------
'1.0' is not a valid floating point value.
---------------------------
OK   
---------------------------

if the .ini file contains numbers represented using a format different from the current "regional settings."

This problem will occur whenever the user changes the settings.

With my developer hat on, my feeling is that this should not be, because the user-configurable number formatting settings are related to UI, i.e. it specifies how the user wants to enter data, and how the system should present numbers displayed to the user--not how applications should internally represent information that the user will never see.

So I would suggest that the code be modified so that the encoding of numbers (or dates, or time, or whatever) in the configuration file(s) be independent from the input / display settings the user might want to choose.

What do you think?

mouser

  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 36,421
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Read more about this member.
    • Donate to Member
Re: Errors when .ini number format doesn't match current regional settings
« Reply #1 on: August 23, 2013, 06:32:50 AM »
Yes you are correct of course, this is a silly bug that's been in place for far too long.  time to fix.