-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Find/replace overlay: find-dialog are resized unnormally if it is used for MD-files #2147
Comments
I’ve seen that too. I’m not sure if that’s a Mylyn problem. It’s always been a problem that two find dialogs open depending on which tab is open. |
Thank you for reporting that issue. It is still reproducible with recent I-Builds? We have fixed several problem with respect to to sizing and placement since M1, so the issue might have been already been resolved. |
Here's a trick that I use to get something else into the target platform. Use Navigate -> Open Setup -> Workspace and copy and paste this text onto the Workspace instance and save it:
Then use Help -> Perform Setup Tasks to perform the Modular Targlet tasks, with such that the Mylyn feature is in the target platform. Launch a runtime workspace with this feature included in the launch. Then you can open a *.md file with the Mylyn editor to see how it works with the latest SDK source. |
…lipse-platform#2147 The FindReplaceOverlay currently expects a target control that is an instance of Scrollable to provide a horizontal and vertical scrollbar. This is invalid, as per API the according getter methods do not necessarily return scrollbars. In consequence, exceptions occur that lead to an improperly positioned overlay, as the update callback for the position and size aborts. This change ensures that scrollbars of the target control are only considered when available. Fixes eclipse-platform#2147
Thank you, @merks! With your trick, I was able able to reproduce the issue within the blink of an eye :-) @speckyspooky the issue you reported is still present in the current development state. It reveals a bug in the find/replace overlay implementation. Thanks again for reporting it! I have proposed a fix in #2154. Note that this will not have any effect on the different find/replace UIs in the source and preview tabs, which is because the source tab uses the Eclipse-integrated search functionality while the preview tab uses the browser-integrated one (IE or Edge, depending on what is used). Just like before, the find/replace bar of one tab will stay open when switching to the other tab, which seems to be caused by the Mylyn markdown editor not using a multi-page editor but some "custom" implementation for showing multiple tabs. |
Thanks for your fast fixing! |
…lipse-platform#2147 The FindReplaceOverlay currently expects a target control that is an instance of Scrollable to provide a horizontal and vertical scrollbar. This is invalid, as per API the according getter methods do not necessarily return scrollbars. In consequence, exceptions occur that lead to an improperly positioned overlay, as the update callback for the position and size aborts. This change ensures that scrollbars of the target control are only considered when available. Fixes eclipse-platform#2147
Steps to reproduce
I use the eclipse version 2024-09. The problem is when the Find/Replace-dialo will be opend on an md-file
the sizing of the dialog is unnormally huge.
Additional on it there is a difference between the "Markdown Source" and the "Preview".
If the find dialog is started at the preview-register a mix of old and new search is shown.
###MD-file, "Markdown Source" register, opened find-dialog
###MD-file, "Preview" register, opened find-dialog
![grafik](https://private-user-images.githubusercontent.com/41593722/354349913-b06ae6b2-90a6-408d-8c89-ddf0ced52ba6.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk2MDIyMDQsIm5iZiI6MTczOTYwMTkwNCwicGF0aCI6Ii80MTU5MzcyMi8zNTQzNDk5MTMtYjA2YWU2YjItOTBhNi00MDhkLThjODktZGRmMGNlZDUyYmE2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE1VDA2NDUwNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQyNjJkOGU3ODNjODc2Y2Q0NmE2MzJhOTVmOTc3NTQ4MzA0Zjk3NDI2NjdiNzlkYjI5MGZkMTFlOTNjMTUyNDgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.DGckf17pJtRlqQhN2YpXNLpMwSlW8yYN6hMQohiuR-0)
Tested under this environment:
The text was updated successfully, but these errors were encountered: