Community
Participate
Working Groups
This appears to be a GTK 2.18 difference (hence me CCing Bogdan), but it looks like the selection area for the checkbox in CVS checkouts is too wide. I'll attach two screenshots of checking out from CVS with 3.5.1 on both GTK 2.16 and 2.18.
Created attachment 150922 [details] GTK 2.16 Checkbox selected, GTK 2.16
Created attachment 150923 [details] GTK 2.18 Checkbox selected, GTK 2.18
Is this valid for the checkbox in CVS checkouts dialog only or for all dialogs for jobs that can be run in background?
It looks like all that can be run in the background. Sorry, I don't know where to re-assign for that.
> It looks like all that can be run in the background. If so, it sounds like an UI issue to me, but they can push it further to SWT.
Also happens in other dialogs like the "Install new software dialog". I guess GridData.FILL is not appropriate for checkboxes anymore.
(In reply to comment #6) > Also happens in other dialogs like the "Install new software dialog". I guess > GridData.FILL is not appropriate for checkboxes anymore. In my opinion they never were. :P
Praveen, could you look into this? If GTK is just drawing the selected state differently in 2.18, this might be a WONTFIX. Need to know for sure what's happening.
This works for me. On both the GTK versions (2.16 and 2.18), the selection area of the checkbox pertains to its text adjacent to it. This applies to all the dialogs/views in the Eclipse, or even the ControlExample clearly shows the behavior for the selection/focus of check-box. Since the reported problem is expected behavior, closing as WORKSFORME. Please reopen with more details, if the problem seems to be different.
ControlExample checkboxes have the correct selection area on GTK 2.18. Should we re-open and move this to CVS since that's the component that seems to be offending?
We could do that...
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.