non ID/PW connect then wxWidgets Debug alert happen #21

New Issue

2016-09-26T06:24:53+02:00

Ghost commented

2016-09-26 06:24:53 +02:00

(Migrated from codeberg.org)

non ID/PW connect then wxWidgets Debug alert happen

![error](https://cloud.githubusercontent.com/assets/12795655/18822571/555863dc-83ec-11e6-84b2-3ffe0a9610f1.PNG) non ID/PW connect then wxWidgets Debug alert happen

Ghost commented

2016-09-26 11:05:28 +02:00

(Migrated from codeberg.org)

Thank you for reporting this.

This is a Debug Alert - occurs only in Debug builds. In Release builds it does not appear.
This is an extra sanity check in wxItemContainer::GetClientObject() (wxWidgets) before returning NULL, which is one of the expected scenarios in my code later on. Therefore, totally harmless.
This occurs only when you have no user certificates installed and "<empty>" is the only choice in certificate selection control. The "<empty>" has no client object data itself and wxChoice remains configured to wxClientData_None instead of wxClientData_Object - which would be after the first certificate is added to the list.

Thank you for reporting this. - This is a _Debug_ Alert - occurs only in Debug builds. In Release builds it does not appear. - This is an extra sanity check in `wxItemContainer::GetClientObject()` (wxWidgets) before returning NULL, which is one of the expected scenarios in my code later on. Therefore, totally harmless. - This occurs only when you have no user certificates installed and "<empty>" is the only choice in certificate selection control. The "<empty>" has no client object data itself and `wxChoice` remains configured to `wxClientData_None` instead of `wxClientData_Object` - which would be after the first certificate is added to the list.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Amebis/GEANTLink#21