Skip to content

Issue 1726 batched defer window pos#6

Open
vogella wants to merge 2 commits into
masterfrom
issue-1726-batched-defer-window-pos
Open

Issue 1726 batched defer window pos#6
vogella wants to merge 2 commits into
masterfrom
issue-1726-batched-defer-window-pos

Conversation

@vogella
Copy link
Copy Markdown
Owner

@vogella vogella commented Jan 27, 2026

No description provided.

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @vogella, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the visual stability and performance of SWT applications on Windows by mitigating common flickering issues. It achieves this through the introduction of batched window positioning for composite children, leveraging the native DeferWindowPos API, and by implementing specific rendering optimizations for SashForm and Link widgets, resulting in a smoother and more responsive user interface.

Highlights

  • Batched Window Positioning: Implemented a batched version of the Windows API DeferWindowPos for more efficient and flicker-free repositioning of multiple child windows within a Composite on Win32 platforms.
  • SashForm Flicker Fix: Introduced platform-specific deferred layout calls (setLayoutDeferred) within SashForm on Win32 to prevent flickering during sash drag operations.
  • Link Widget Flicker Fix: Addressed flickering in Link widgets on Win32 by overriding WM_ERASEBKGND to prevent background erasure, which is a known issue with the native SysLink control during resizing.
  • New Link Widget Tests: Added comprehensive JUnit tests for the Link widget to verify its rendering stability, content integrity, and lack of flickering during rapid resizing and redrawing scenarios.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

…for SashForm

This commit improves the performance of Composite.resizeChildren by batching calls to the Windows DeferWindowPos API. Instead of making individual JNI calls for each child, arrays of window positions are passed to a new native method, which handles the loop in C.

This optimization allows SashForm to use deferred layout on Windows, which eliminates flickering during sash dragging.

Fixes eclipse-platform#1726
@vogella vogella force-pushed the issue-1726-batched-defer-window-pos branch from 0da5296 to 9445d3b Compare January 27, 2026 16:28
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces batched window positioning for Win32 platforms, which should improve performance and reduce flickering during layout operations. It also includes a specific fix for the Link widget on Windows to prevent flashing during resize, along with corresponding unit tests. The changes are well-implemented and address the stated issues effectively.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant