Hello, I can see two possible solutions to this problem. The first one would be to use non-persistent highlights. The API to manage non-persistent highlight is found in ro.sync.ecss.extensions.api.highlights.AuthorHighlighter. You can get access to the highlighter instance by calling AuthorAccess.getEditorAccess().getHighlighter(). You'll have to manually add the a highlight for each dxml-merge-start PI and also remove them when needed. The second solution would be to change a bit the processing instruction: <?dxml-merge-start text group="d2e150" mergeType="modify" ?> <?dxml-merge-end text group="d2e150"?> into: <?oxy_custom_start type="dxml-merge-start" text group="d2e150" mergeType="modify" color="255,255,0" ?> <?oxy_custom_end text group="d2e150"?> This way the PI will automatically be identified by Oxygen as a persistent highlight and you will also have in it all the information you need for custom processing. Best regards, Alex -- Alex Jitianu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 19-Dec-12 6:27 PM, Michael Anthony Smith wrote:
Hello,
In my last posting to this list, entitled "Request to enable 'form based editing' from processing instructions", we set out our use of processing instructions for merge conflict resolution. It would be nice if we could highlight the content between two of our processing instructions. So that the user could clearly see what 'content' was in consideration.
It may be possible to do this using AuthorPersistentHighlight, but this appears to be linked with the <?oxy_custom_start?> and <?oxy_custom_end?> processing instructions. We could use these, but it would make our processing significantly more complicated (and our format less succinct). Previous discussion on this topic on the oxygen user mailing list, suggested that this was limitation of the AuthorPersistentHighlight approach (at least at that time). Is there anything that we have missed/new-developments that would allow highlighting content between arbitrary processing instructions.
Best regards, Anthony. -- -- ------------------------------------------------------------------------- Michael Anthony Smith, DeltaXML Ltd "Michael Anthony Smith, DeltaXML Ltd "Experts in Information Change"" T: +44 1684 869035 E: anthony.smith@deltaxml.com <mailto:anthony.smith@deltaxml.com> http://www.deltaxml.com <http://www.deltaxml.com/> Registered in England 02528681 Reg. Office: Monsell House, WR8 0QN, UK
_______________________________________________ oXygen-sdk mailing list oXygen-sdk@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk