[Bug]: TestForm app: KCombobox from main.cs causes a crash about standard-toolkit

[giduac]

@Smurf-IV
Tested this on alpha and the error is gone!

[giduac]

@Wagnerp
Please, assign to Giduac.

TY!

[Wagnerp]

@Wagnerp Please, assign to Giduac.

TY!

@giduac

Done! :)

[giduac]

@Smurf-IV & @Wagnerp
Narrowed down further. Topic start updated.

[giduac]

@Wagnerp

A question about this and maybe you can help me short circuit this.

The error happens when the main form is shown and the Office 365 blue theme is active.
When for example the Office 365 Dark theme is active all is good.
When the font type and size is changed in StateCommon.Content in the designer the error is gone.

Could you please have a look if there are differences between the Blue and Dark theme which could lead to this?

[Wagnerp]

@Wagnerp

A question about this and maybe you can help me short circuit this.

The error happens when the main form is shown and the Office 365 blue theme is active. When for example the Office 365 Dark theme is active all is good. When the font type and size is changed in StateCommon.Content in the designer the error is gone.

Could you please have a look if there are differences between the Blue and Dark theme which could lead to this?

Hi @giduac

The only differences I can think of are the colours. You could use a application called WinMerge to compare the differences.

[giduac]

@Wagnerp
The only differences I can think of are the colours. You could use a application called WinMerge to compare the differences.

if a font is selected/set here then the errror is gone. Remove the font and the error is back.

[giduac]

@Smurf-IV
Can you please spare a couple of minutes and have a look at the topic start and the findings so far to see if you can point us in right direction here.

[Smurf-IV]

@giduac FYI: I have other things scheduled - I'll not be able to get to this until the 26th of May at the earliest.

[giduac]

@giduac FYI: I have other things scheduled - I'll not be able to get to this until the 26th of May at the earliest.

OK, NP.

I'll see how far I can get on this in the mean time.

[Smurf-IV]

@giduac are you in a position to solve this, Or do you want me to "have a go" at it still ?

[giduac]

Hi @Smurf-IV ,
I'd like you to have a look at it and see what you can make of it.
Not sure if I got all the info that's to be had.
This ain't cut and dried, and could well be an error within dotnet itself.

The topic start shows how far i got.
And main.cs in Testform still has this error.

Keep me posted on your findings and I'll see if I can be of assistance...

[giduac]

@Smurf-IV
FYI: Corrected the title and added to the topic start:
- Added: as stated earlier, it is not related to a specific theme.

[Smurf-IV]

Incoming PR: