Tagged: sql file tab view
April 16, 2018 at 5:34 am #580718
When I open sql file, it it displayed correctly. But sometimes when I switch tabs (any java file and then return to sql file) it is displayed in strange view. I can not change view of file to full screen, only I have to close tab and reopen sql file again. It is unconfortable for me to do it.
It is bug or can I configure it someway.
Thanks.April 16, 2018 at 6:29 am #580724
Sorry that you are seeing this problem. Thank you for the screenshot.
I could not replicate the problem with MyEclipse 2017 CI 10 at my end.
1. Can you please clarify if you can consistently replicate this problem with any .sql file or a particular .sql file? If it is a particular .sql file, then please share the file with us.
2. Can you please check if you can replicate the problem in a new workspace as well? If yes, then please send us the .log file located at workspace dir/.metadata/.log to help us check for any related errors/exceptions.
3. Please share with us the MyEclipse Build Id and Version details from Help > About MyEclipse section along with your OS and version details for further investigation.
Apologies for inconvenience caused.
Genuitec SupportApril 17, 2018 at 3:10 am #581017
Problem occurs randomly, with any sql file.
I am attaching logs.
It happens on clear workspace too.
Version: 2017 CI 10
Build id: 15.0.1-20171220April 19, 2018 at 10:24 am #581662
Apologies for the delayed response. Thank you for the details and the log file.
The log file does not have any related errors.
I have filed a bug for the dev team to look into this problem.
Can you please also share the OS and version details?
Genuitec SupportApril 23, 2018 at 12:14 am #582320
MyEclipse Enterprise Workbench
Version: 2017 CI 10
Build id: 15.0.1-20171220April 23, 2018 at 2:45 am #582372
We’ve been able to replicate this issue internally, but in conjunction with use of the inline search. So if you use the inline search in the SQL editor, then switch away to another editor and come back, you’d find the layout as you describe.
Are you invoking the inline search at all in the SQL editor? If not, we will need to keep looking for additional points of failure.
In case you are unaware, the inline search replaces the regular search in recent versions of MyEclipse and looks like this: