| commit | b382326cc98dc98711da33acc9d9d124c67b0dff | [log] [tgz] |
|---|---|---|
| author | jmajano <jmajano@redhat.com> | Wed Jun 30 11:49:50 2021 -0400 |
| committer | Alexander Kurtakov <akurtako@redhat.com> | Thu Jul 01 07:38:54 2021 -0400 |
| tree | 552442ad57c1a28ccca6fc6dc5cf2e64d123fcc4 | |
| parent | 3b71d9cf52b3a0232be4c05c60383ac3aaae0921 [diff] |
Bug 567215 - [GTK4] Port SWT Combo While working on a fix for SWT Snippet 26, the issue was found in adjustChildClipping as it applied some logic on READ ONLY Combos. The bug is that when an item is selected, the widget disappears until a resize of the window. There are a couple issues: 1) the gtk_cell_view_set_fit_model function appears to not be doing what its supposed to. This can be seen as the combo resizes based on the length of the item string. This function should allow for the CellView to be smaller than the max size. 2) The combo does not conform to setBounds, thus this could be interfering with set fit model, but to test this the setBounds issue needs to be fixed. For now, the fix in this patch will allow snippet 26 to run without it disappearing when an item is selected, but it currently does not behave like it does in GTK3. I have made a comment to revisit this issue once other bugs are fixed. Change-Id: I0e4d771028e53b5f89fa869a191a01f7f9d7112a Signed-off-by: jmajano <jmajano@redhat.com> Reviewed-on: https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/182657 Tested-by: Platform Bot <platform-bot@eclipse.org> Tested-by: Alexander Kurtakov <akurtako@redhat.com> Reviewed-by: Alexander Kurtakov <akurtako@redhat.com>
Thanks for your interest in this project.
See the following description for how to contribute a feature or a bug fix to SWT.
Information regarding source code management, builds, coding standards, and more and be found under the following link.
Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).
Contact the project developers via the project's “dev” list.
This project uses Bugzilla to track ongoing development and issues.
Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!