TAdvProgressBar

Optimizing App Performance: Reducing Repaints in TAdvProgressBar is a core UI optimization strategy for Delphi and C++Builder developers using the TMS VCL UI Pack. Because TAdvProgressBar features complex graphics like multi-color stacked displays, smooth gradients, and custom text formatting, updating its position inside a tight loop triggers frequent, CPU-heavy screen repaints that drastically degrade application performance. The Core Problem: Redundant Repainting

When parsing a massive file line-by-line or downloading large datasets, developers often update the bar’s position on every iteration. This forces the VCL framework to constantly invalidate the control and redraw its complex visual elements (such as blocks, backgrounds, and shadows). If the loop runs thousands of times per second, the UI thread becomes a bottleneck, causing the entire application to lag or freeze. Best Practices to Reduce Repaints 1. Filter Out Redundant Value Changes

Historically, assigning a value to Position could trigger a repaint even if the new value was identical to the current one. While TMS Software optimized SetPosition to skip rendering when Value == FPosition, it remains best practice to protect your UI updates at the application level:

// Avoid forcing a redraw if the position hasn’t shifted if AdvProgressBar1.Position <> NewPosition then AdvProgressBar1.Position := NewPosition; Use code with caution. 2. Scale Progress Updates (Step Reduction)

If your loop processes 100,000 records but the progress bar is only 300 pixels wide, updating the UI 100,000 times wastes massive computational power. Instead, scale the values or update the bar only when a specific milestone (e.g., every 1% or every 500 items) is reached.

// Update only on percentage changes var CurrentPercent := Round((CurrentRecord / TotalRecords)100); if AdvProgressBar1.Position <> CurrentPercent then AdvProgressBar1.Position := CurrentPercent; Use code with caution. 3. Throttle Updates Using Time Thresholds

Instead of linking progress to data increments, link it to clock cycles. Use a millisecond timer to decouple the processing thread from the UI thread, ensuring the bar refreshes no more than 30 to 60 times per second.

// Example utilizing a simple tick count check inside a loop if GetTickCount - LastUIUpdate > 33 then // ~30 FPS begin AdvProgressBar1.Position := CurrentProgress; LastUIUpdate := GetTickCount; end; Use code with caution. 4. Turn Off Heavy Visual Features During Fast Actions How to Improve WPF Application Performance | SciChart