Disable content completion in Attributes view

<oXygen/> general issues.
Seb
Posts: 23
Joined: Mon Feb 20, 2017 8:03 pm

Disable content completion in Attributes view

Post by Seb » Thu Mar 09, 2017 3:35 pm

Hi,

I want to disable content completion in the Attributes view, because this often leads to mistakes in our project.

I know about the content completion preferences [1], but they do not seem to have any effect on the Attributes view.
I also know about this doc page [2], but there is no mention on how to disable content completion.


[1] https://www.oxygenxml.com/doc/versions/ ... etion.html
[2] https://www.oxygenxml.com/doc/versions/ ... anels.html

Radu
Posts: 6511
Joined: Fri Jul 09, 2004 5:18 pm

Re: Disable content completion in Attributes view

Post by Radu » Thu Mar 09, 2017 3:56 pm

Hi,

Just to see if I understand, you have an attribute (probably a profiling attribute) which can take multiple values and you want the attribute to be edited without Oxygen proposing in the combo box single value choices for it, right?
If not, could you elaborate? Do you want the attribute to be shown as completely read-only? What version of Oxygen are you using?
In the Oxygen DITA framework configuration folder there is a content completion configuration XML file:

OXYGEN_INSTALL_DIR\frameworks\dita\resources\cc_config.xml

You can probably add in it something like:

Code: Select all

    <match attributeName="audience">
<items action="replace"/>
</match>
in order to say that you want for the attribute named @audience no values and you want this setting to replace the existing values.

More about the cc_config.xml:

https://www.oxygenxml.com/doc/versions/ ... -proposals

Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com

Seb
Posts: 23
Joined: Mon Feb 20, 2017 8:03 pm

Re: Disable content completion in Attributes view

Post by Seb » Fri Mar 10, 2017 2:02 pm

Hi Radu,

thank you. You understood correctly, and creating a cc_config.xml has solved my problem. It's even better that I can switch off suggestions per attribute name instead of globally.

Post Reply