entering step size in Windows application
Version 2 of the myFocuser Project
Brought to you by:
brownrb
Menu
▾
▴
Hello,
when using the Windows application on a computer with the german version of Win10, trying to enter the step size (e.g. 1.55 or 1,55 doesn't matter) the seperator will not be accepted. So, when entering 1.55 the application will use 155 instead, the same with 1,55. There's no way to entering the data as needed.
Is that behavior something that could be fixed in the application itself or do i need to change some windows settings?
Btw: Great application and well done documentation. I made till now three devies for my ED80, a Meade zero image shift focuser and a Skywatcher 10" Quattro. I'm very happy with it.
Thank you
Wolf
Hi
It has to do with the Windows Locale settings.
I thought that this issue was addressed earlier in the last release of the WIndows app.
I will take a look. Email me direct so I can send you a test version to try
Regards
Robert
Try these and let me know if its fixed
Hi Robert
Thanks for the quick answer. I made a fresh installation and unfortunately it shows the same behavior. When pressing the "Close" button it deletes the separator (dot). I tried to copy and past the value in to the field, but it doesn't worked as well.
Regards
Wolf
Hi Wolf
Yes, that is how I designed it. You can enter a value such as 1,25 but the moment you press enter or close the form, you note then when you reopen it the comma is gone and replaced with a dot
Thats because Windows perfers to do conversions on double types using a .
So its easier just to change it from , to a . and it ends up being a lot less code and thus easier to maintain. So sorry, you can enter as , but the app and windows is always going to use a .
I just tested the 2.3.7.0 and it is working exactly as intended. Entering 7,52 ends up being 7.52
ASCOM 242 is the same.
Regards
Robert
Hi Robert,
it`s exactly as you described. I'm not able to enter the ,.But when entering the . (dot), it will deleted at the end too. So, even typing 1.55, at the end the dot . is deleted and the value will be 155 instead of 1.55.
Best regards
Wolf
Hi Wolf
Please try this attached version.
You will need to uninstall previous before trying to install this one
It is only windows app. If works then I will copy code to ascom driver etc
It should retain the , being used a decimal separator
If issues
1. Enable logging
2. do what you do to cause issue - capture screenshot before and after
3. close
4. send me screenshots and logfile
Regards
robert
Both code for temp offset on main form and stepsize on extra settings form altered in this version.
here is v2.3.7.1
Hi Wolf
I you can let me know what language settings you are using in windows that can also help
Regards
Robert
Hi Robert
I removed the version 2.3.7.0 and installed the new version 2.3.7.1. I made a presentation with screenshots showing the complete process fom starting extra settings, entering different variants of values and showing the results for each try.
I'm using the German WIN10 version. The region settings are german as well.
Please find attached a PDF with the process screenshots and a screenshot of my region settings.
And here are the region settings.
Regards
Wolf
Last edit: Wolf 2017-07-07
Can you please try and post the logfile?
Its got me stumped right now. I had correctly guessed your settings were German and I had already changed mine to match during testing earlier. So its hard for me to see why this happening for you and not me. The logfile might give me a clue'
Regards
Robert
I actually changed a lot of code in v2.3.7.1 and now basically keep the string for stepsize that is entered exactly the same so I cannot see where its being changed. The logfile will help
Please try this update - I have added some more debug output in hope to find where the problem is - please run this version and then send me logfile
Hi Robert,
I tried version 2.3.7.2 with no success. Please find attached the log-file. There was no connection to the focuser, since I'm not at my telescope at the moment. As soon as I will be back at home I will try it fully connected.
Regards
Wolf
Hi Robert,
in the meantime I tested the version 2.3.7.2 on several other PC's, five in total. On each system is WIN10 installed, with german region settings. All PC's showing the same (strange) results, so it may be not a config problem on a single PC. In addition I attached the log-file from my observatory PC, connected to the focuser.
Thanks for your support
Wolf
Hi Wolf
Sorry for the back and fro and thanks for your patience, I believe there is some light at the end of tunnel now.
I have created a new machine with German Settings. I think I know better now why this is happening to you.
I have made code changes and tested it in German environment. It appears to be working.
I now need a few hours to copy the code into the remaining sections as well as the temperature offset.
So I'll do that today and send you the new code to try later today my time.
regards
Robert
Hi Wolf
Please try attached
Hi Robert,
you made it! It's working perfectly now.
Many thanks and best regards
Wolf
Thanks Wolf, really appreciate your help in testing.
I hope to do the mini-app and ASCOM driver changes tomorrow time permitting.
Best regards
Robert