User Answers

I would suggest first checking the browser you have selected in your Eclipse settings. From the preferences page, select General > Web Browser and confirm that the expected browser is selected.

Next take a look at the settings in your IE 11 browser to check the Emulation settings. (In the F12 Developer Tools make sure that the Document Mode selected there is not 7.

This is not possible at the moment. But it is something that has been requested by customers before, and it is on the Atelier development roadmap!

What version of Eclipse are you using? We've seen similar issues with Atelier 1.3.117 on versions of Eclipse besides Photon.

I would suggest that you start by installing a new Eclipse Photon client then install the Atelier plug-in.

My best guess from the description here is that the CSP application was not created properly in the Atelier Project. Currently you cannot create a new CSP application at the Atelier Project level - you need to copy the CSP app from the server. For example:

1. Create a new web application in Caché:

Development is aware of this issue. We do not have a timeline on when it will be fixed.

If you would like to track the progress of the development change, I would suggest opening up a WRC case (email or call +1 617-621-0700). A Support advisor will be able to link the relevant development change to the WRC case then you can keep track of it using the new UX in the WRC application.

Looks like you've got this figured out, but I wanted to add another option - using the Local Terminal option in the plugin to connect to a Caché/Ensemble/HealthShare/InterSystems IRIS instance

There is an existing request with development to improve the usability of XData blocks in Atelier. I added a note to that request, linking to this DC post, asking to consider the auto spacing/indentation as well. The request for XData usability improvements has not yet been roadmapped.

I've been working with Lucas S. on this in a WRC case. We believe that the source of the issue has to do with the encoding of the file, as compared to the file's contents and the encoding of the Eclipse workspace/Atelier Project/file in Atelier.

Copying this problem file into an Eclipse-only (non-Atelier) project does result in display issues until the file's encoding is changed within Eclipse. To change a file's encoding you can right-click the file in the Atelier or Project Explorer, click Properties and change the "Text file encoding" settings under the Resource section

After upgrading to Atelier 1.2, did you run into the issue described in the DC post here? If so you may have Googled and found information about adding -clearPersistedState, or something similar, to one of the Eclipse configuration files. However if a setting like that is left around in the config file, it could result in Eclipse not persisting data across shutdowns since that setting will be read back in each time you start Eclipse back up.