Important: These forums are for discussions between SkyDemon users. They are not routinely monitored by SkyDemon staff so any urgent issues should be sent directly to our Customer Support.

Win SD: a bug in a COMxxx port combobox listing


Author
Message
Adam N
A
Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)
Group: Forum Members
Posts: 14, Visits: 6
Hello

A perhaps a minor issue.

On: PC, SkyDemon 3.8.2.0, Win10 - 64

Setup - GPS Navigation Options - GPS Hardware

Port: COMxxxx

The listing in the combobox is wrong - e.g. seems to be wrongly setting up the 0x00 delimiter to strings.

Example:
COM1 <<< OK
COM10 <<< OK
COM70 <<< wrong - this shall be COM7 (and in Win it is, yet it seems the SD keeps the data from the previous field - the last '0' char)
COM80 <<< same issue
COM11 <<< OK
COM12 <<< OK

How it shall look like:
COM1
COM10
COM7
COM8
COM11
COM12

Actually, it breaks even more (further every time the window itself is open), see the screenshot:


Not sure it this is a win32 API issue under Win10/64,
or something in SD.

Luckily the ComboBox could be editted manually, which has saved the day.

So just FYI, I guess, hope it helps.

---
‌‌
Also, could a direct "raw COM port capture to a file" feature be added (even if only to a Win EXE version of SD), right in there; of course to fully work along the "Go Flying" mode. That would be so great and useful !

a.
Adam N
A
Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)
Group: Forum Members
Posts: 14, Visits: 6
Further set of issues:
Once changing the available COMx ports on the computer (adding / removing hardware), the SD faults:‌

‌‌
System.ArgumentOutOfRangeException: InvalidArgument=Value of 2 is not a valid argument for SelectedIndex.
Parameter Name: SelectedIndex

 in System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
 in Divelements.SkyDemon.UI.GpsNavigationOptionswindow.WarningOptionsWindow_Load(Object sender, EventArgs e)

 in System.Windows.Forms.Form.OnLoad(EventArgs e)
 in System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
 in System.Windows.Forms.Control.CreateControl()
 in System.Windows.Forms.Control.WmShowWindow(Message& m)
 in System.Windows.Forms.Control.WndProc(Message& m)
 in System.Windows.Forms.Control.ControlNativewindow.WndProc(Message& m)
 in System.Windows.Forms.Nativewindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


Happened while opening the "GPS Navigation Options" window. And is so stuck. Seems like an issue‌ connected with the ComboBox again. This happens regardless on the state of the SD (should the exe be closed and then opened again, or any other combination - simply once the available COMx list of ports changes due to whatever reason).
 Too bad that it is not gracefully handled, as the SD threw an exception and the window got stuck in a fully un-populated state, ‌losing all my previous configuration.

best,
 a.‌‌‌

Tim Dawson
Tim Dawson
SkyDemon Team (623K reputation)SkyDemon Team (623K reputation)SkyDemon Team (623K reputation)SkyDemon Team (623K reputation)SkyDemon Team (623K reputation)SkyDemon Team (623K reputation)SkyDemon Team (623K reputation)SkyDemon Team (623K reputation)SkyDemon Team (623K reputation)
Group: Forum Members
Posts: 7.8K, Visits: 8.4K
I think the first post problem is a win32 bug, we simply enumerate COM port names from the registry. COM ports are hardly ever used any more and this is a feature kept only for historical reasons; we don't intend to touch it.

The crash is concerning when bringing up that window but I do not think it is related to COM ports; the call stack confirms this as there is no set to SelectedIndex (which is causing the exception) related to COM ports. ‌‌
Adam N
A
Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)Too Much Forum (1.3K reputation)
Group: Forum Members
Posts: 14, Visits: 6
No issue, just wanted to report the situation.

For the first reported item - luckily a manual text entry saves the day, so it might just be small surprise to see the non-valid com port names, but no big deal.
‌‌
About the exception - It is fairly easy to replicate;‌‌ on Win10; just add  / remove any external BT device with RFCOMM (external GPS for example), which changes the contents of the enumeration result. As (obviously) the SD remembers the last configuration, it tries to apply it, and it might fail if the new list is different from what was there during the last time.

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search