search

Krypton-Suite / Standard-Toolkit

An update to Component factory's krypton toolkit to support .NET Framework 4.6.2 - 4.8.1 to .NET 6 - 8
BSD 3-Clause "New" or "Revised" License
374 stars 56 forks source link

[Bug]: Launching TestForms -> Controls Test results in Exception message box #1556

Closed Smurf-IV closed 6 days ago

Smurf-IV commented 4 weeks ago

Using today's alpha:

image

@giduac Appears to be theme selection related

Smurf-IV commented 4 weeks ago

And when launching Calendar: image

giduac commented 3 weeks ago

Hi @Wagnerp,

Please assign to me, ty.

Wagnerp commented 3 weeks ago

Hi @Wagnerp,

Please assign to me, ty.

Hi @giduac

Done

giduac commented 3 weeks ago

@Smurf-IV & @Wagnerp

These messages do not happen consistently. I had it one time yesterday. Then tried another 10 times or so without problems.

Seems that somewhere a setting gets changed that triggers a debugtools warning/message... That gets triggered every time a theme change is performed....

Next to that:

giduac commented 3 weeks ago

Hi @Wagnerp & @Smurf-IV,

A question about form fading.

Which was the reason to add the ModernFadeFormIn and ModernFadeFormOut methods to KryptonFormFadeController?

Wagnerp commented 3 weeks ago

Hi @Wagnerp & @Smurf-IV,

A question about form fading.

Which was the reason to add the ModernFadeFormIn and ModernFadeFormOut methods to KryptonFormFadeController?

Hi @giduac

They were designed specifically to work with .NET. Problem with fading though is there is a bug where the KForm 'pops' in at the very last second.

giduac commented 3 weeks ago

@Wagnerp Ok, thanks.

The modern fadeout method doesn't work since the loop is infinite. Making all programs using this and .NET hang on fade out. The < .NET and this version also has some flickering when fading.

I'll make the FadeForm with some test controls to show a more fine grained fade in and out which is more fluent. But that will always be a bit speculative since not all computers are the same and also the load on a system can influence that.

With the findings of that FadeForm we can then adjust those methods and maybe the .NET Framework ones also.

The updated FadeForm for testing:

https://github.com/Krypton-Suite/Standard-Toolkit/assets/96108132/8f55c31b-afae-41e0-bc1a-bde7380a99a9

giduac commented 3 weeks ago

@Smurf-IV & @Wagnerp

I'd like you to test the updated FadeForm and play with the added controls to see what you think are good settings so we can update the methods in the KFormFadeController.

See the above post.

Smurf-IV commented 3 weeks ago

Can the "FadeForm" be moved to the extended toolkit, as it appears to have never "Really" worked due to the number of bugs. And, also move the bugs as well ?

giduac commented 2 weeks ago

@Smurf-IV & @Wagnerp,

If someone get these Debug messages (as those are not replicable) make sure to hit break in the debugger so we can see where these come from.

giduac commented 6 days ago

Hi @Wagnerp, Seems that this error has gone. When reappears this can be reopened. Please close ty.

giduac commented 2 days ago

Being handled through: https://github.com/Krypton-Suite/Standard-Toolkit/issues/1321