On 07/16/2013 09:37 PM, Jeff Hooker wrote:
Small misunderstanding; it's not the whole screen that goes blank, just
the spot where the href value should be displayed in the topicref
element. XXE is not crashing or locking.
OK.
The root of my question is that either the "refresh" command is not
working (or is not for this context), or I am misunderstanding its
function. When run against an element with peusdo-elements such as this:
topicref:before {
content: paragraph(content(item-collapser(), " ",
attr(navtitle), " ",
drop-site(icon, icon(drop),
command, "setObject",
parameter, "href anyURI -
'%{value}'"), " "
), " "
),
topicref-format());
}
Should the command "refresh refresh[implicitElement]" force XXE to
re-layout and repaint selected topicref, including any associated
peusdo-elements?
It's very difficult to answer your question. Invoking command refresh is
rarely needed and I fail to see cases where there is a need to invoke
refresh from say, a macro-command.
The refresh command is correctly documented here:
http://www.xmlmind.com/xmleditor/_distrib/doc/commands/refresh.html
Parameter "rebuild" (not "refresh") recreates the full view, including
generated content, of the selected node. This is what happens when the
document is first opened in XXE.
For example, what follows is the deepest, fullest, kind of refresh of a
view of a document:
---
refresh rebuild[implicitDocument]
---
Therefore if you need to use refresh in a macro, please use
---
refresh rebuild[implicitElement]
---
and not
---
refresh refresh[implicitElement]
---
If so, am I understanding correctly that this process
should be the same process as the one used to layout and paint the
screen when the file is first opened, but run on a specific part of the
file rather than the whole file?
If so, it's puzzling, because the elements are laid out and painted
correctly when the file is opened or reopened, but using the "run
command" dialog to run the refresh command on the misbehaving topicrefs
does nothing and produces no error output in the command window. Perhaps
it is tied into the "topicref-format()" function, for which I have yet
to find documentation.
Yes, that's right. The map view is styled using a CSS extension.
Excerpts from map.css or bookmap.css:
---
/*
* Implementation of methods topicrefContent and chunkIcon.
*/
@extension "com.xmlmind.xmleditext.dita.MapStyleSheetExtension";
...
topicref:before {
display: inline;
content: invoke("topicrefContent", normal);
}
---
There is no documentation for this CSS extension. However you may want
to read its Java source code (short and straightforward) which is found
in src/com/xmlmind/xmleditext/dita/MapStyleSheetExtension.java
More information about CSS extensions:
http://www.xmlmind.com/xmleditor/_distrib/doc/dev/styleext.html#solution1
In answer to your question, yes, I am introducing some fairly minor
changes to your default map view; just moving the functions needed
closer to the user and trying prevent them from using the Attribute
pane, which just leads to trouble.
OK.
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
