Profile Picture

NTabControl maxes out CPU on hover

Posted By Craig Swearingen 8 Years Ago
Author
Message
Craig Swearingen
w00t Posted 8 Years Ago
View Quick Profile
Supreme Being

Supreme Being (97 reputation)Supreme Being (97 reputation)Supreme Being (97 reputation)Supreme Being (97 reputation)Supreme Being (97 reputation)Supreme Being (97 reputation)Supreme Being (97 reputation)Supreme Being (97 reputation)Supreme Being (97 reputation)

Group: Forum Members
Last Active: 4 Years Ago
Posts: 99, Visits: 654
I've been using the NTabControl extensively in my application. I noticed today that my application updating hung unexpectedly. Watching the task manager I saw the CPU for my application max out the system.

This can be easily reproduced by launching the "Examples C# for Nevron UI" application that came with my license. I'm on build 11.12.14.12.

1) In the "All Examples" list select the "Tab Control" example.
2) Check the "Has Close" and "Show Close Button on Each Tab" checkboxes
3) Show the Windows Task Manager so you can watch the CPU spike
4) Hover the mouse over a non-top tab making the close button on the right show
5) See the CPU spike and stay maxed out

It seems as though it locks the UI trying to show the "Close" tool tip and never does. I tried in my application setting the ShowToolTips property to false but this didn't do anything.

1) If I set HasClose and ShowCloseButtonOnEachTab to false I can still get this to occur but its much more difficult to find the mouse hover spot where it happens.

2) Is there something I can do in my license to fix this issue?





Nevron Support
Posted 8 Years Ago
View Quick Profile
Supreme Being

Supreme Being (4,090 reputation)Supreme Being (4,090 reputation)Supreme Being (4,090 reputation)Supreme Being (4,090 reputation)Supreme Being (4,090 reputation)Supreme Being (4,090 reputation)Supreme Being (4,090 reputation)Supreme Being (4,090 reputation)Supreme Being (4,090 reputation)

Group: Forum Members
Last Active: 9 hours ago
Posts: 2,962, Visits: 3,363
Hello Craig,

It is a bug.

It will be fixed in the next release.

Best Regards,
Nevron Support Team





Similar Topics


Reading This Topic