Page 1 of 1

2 weird bugs

Posted: Wed Sep 08, 2021 11:50 am
by zerolatitude
1. SC 4.0 doesnt do automatic updates for the last few versions for me. It used to - its stopped. if I do Check for updates it says no updates found. I have to go to the downloads page and manually update. Any setting I should look at? Registry editing is fine. Currently on 4.0.8138.0. Windows 10, 21H1

2. This one is weird. In target name, I cannot type in any target beginning with M1. The letters after that go to the front of the name. Eg, M104 become 04M1. M11 becomes 1M1. I then have to manually delete the first characters and aroow my way to the end and type it in.

Note that L104 is fine. M204 is fine. But if it begins with M1, its weird. Any suggestions? Log extract is below.

nfo 17:13:38.789535 #1 Ended void SharpCap.Base.CaptureProviderBase<T>.StartPreview() in void SharpCap.Base.CaptureProviderBase<T>.StartPreview()
Debug 17:13:38.806491 #1 Ended (Profile applied) bool SharpCap.Models.Camera.ApplyDefaultProfile() in bool SharpCap.Models.Camera.ApplyDefaultProfile()
Info 17:13:38.882852 #1 Toolbar/Menu input : SharpCap.ViewModels.Actions.OpenCameraAction Folder Monitor Camera complete in async Task SharpCap.ViewModels.UIAction.Execute()
Debug 17:13:39.166361 #1 Started new SharpCap.UI.Hardware.MountControl(Mount model) in new SharpCap.UI.Hardware.MountControl(Mount model)
Debug 17:13:39.171348 #1 Started new SharpCap.ViewModels.MountViewModel(Mount model) in new SharpCap.ViewModels.MountViewModel(Mount model)
Info 17:13:39.173340 #21 =='Monitor mount movement thread' (New Thread)
Debug 17:13:39.173340 #21 Started void SharpCap.ViewModels.MountViewModel.MountMonitor() in void SharpCap.ViewModels.MountViewModel.MountMonitor()
Debug 17:13:39.175337 #1 Ended new SharpCap.ViewModels.MountViewModel(Mount model) in new SharpCap.ViewModels.MountViewModel(Mount model)
Debug 17:13:39.181320 #1 Started new SharpCap.ViewModels.FocuserViewModel(Focuser adaptor, IUIProvider uiProvider) in new SharpCap.ViewModels.FocuserViewModel(Focuser adaptor, IUIProvider uiProvider)
Debug 17:13:39.182347 #1 Ended new SharpCap.ViewModels.FocuserViewModel(Focuser adaptor, IUIProvider uiProvider) in new SharpCap.ViewModels.FocuserViewModel(Focuser adaptor, IUIProvider uiProvider)
Info 17:13:42.090815 #1 Target name changed to M in void SharpCap.Models.Application.set_TargetName(string value)
Info 17:13:42.329794 #1 Target name changed to M1 in void SharpCap.Models.Application.set_TargetName(string value)
Info 17:13:42.476521 #1 Target name changed to 0M1 in void SharpCap.Models.Application.set_TargetName(string value)
Info 17:13:42.675023 #1 Target name changed to 04M1 in void SharpCap.Models.Application.set_TargetName(string value)
Info 17:13:44.732909 #1 Target name changed to 0M1 in void SharpCap.Models.Application.set_TargetName(string value)
Info 17:13:44.910420 #1 Target name changed to M1 in void SharpCap.Models.Application.set_TargetName(string value)
Info 17:13:47.654896 #1 Target name changed to M in void SharpCap.Models.Application.set_TargetName(string value)
Info 17:13:47.988791 #1 Target name changed to M1 in void SharpCap.Models.Application.set_TargetName(string value)
Info 17:13:48.187688 #1 Target name changed to 0M1 in void SharpCap.Models.Application.set_TargetName(string value)
Info 17:13:48.486153 #1 Target name changed to 04M1 in void SharpCap.Models.Application.set_TargetName(string value)
Info 17:13:50.479704 #1 Target name changed to 0M1 in void SharpCap.Models.Application.set_TargetName(string value)
Info 17:13:50.700562 #1 Target name changed to M1 in void SharpCap.Models.Application.set_TargetName(string value)
Info 17:13:52.493235 #1 Target name changed to M10 in void SharpCap.Models.Application.set_TargetName(string value)
Info 17:13:52.727083 #1 Target name changed to M104

Re: 2 weird bugs

Posted: Wed Sep 08, 2021 1:50 pm
by admin
Hi,

I do not publish auto-updates straight away when I make a new version - I usually do an auto update at least one week behind and sometimes several weeks behind, to allow time for any silly bugs to be found and fixed. As it turned out, I put a new auto-update out yesterday (4.0.8138), but there is already a newer version for manual download. What this means is that if you want to be right on the latest version you will have to download manually each time. If you are happy waiting a little longer and ending up getting versions that have already been 'proved' by some real world testing then wait for the auto-update to come along.

The second issue is (I think) because you have 'M1' as one of the custom targets that you have set up in your target name drop down. When you type in one of the preset items, Windows helpfully selects the preset for you and moves the cursor back to the beginning of the text. I was unaware of this and I will see if there is a way that I can disable that.

cheers,

Robin

Re: 2 weird bugs

Posted: Fri Sep 10, 2021 3:12 am
by zerolatitude
Thanks for the info re the updates - will wait for the auto update and see if all goes well.

Re the typing bug, yes it went away when I removed M1 from the dropdown. Weird one. hope you can find a solution, though its really more of an inconvenience than an issue.

Thanks.

Re: 2 weird bugs

Posted: Wed Sep 15, 2021 12:07 pm
by zerolatitude
Just checking in here.

I am on 4.0.8138, published 30 Aug.

On the download page, there are 3 newer versions - 8149, 8169 and 8173. But no auto-update so far. Is this okay?

Re: 2 weird bugs

Posted: Wed Sep 15, 2021 1:20 pm
by admin
Hi,

yes, that's correct. I only do the auto-update after a couple of weeks minimum and when I am happy that there are no silly bugs in the new version going for auto-update.

cheers,

Robin

Re: 2 weird bugs

Posted: Thu Sep 16, 2021 5:28 pm
by zerolatitude
Okay thanks