Jeff Hooker wrote: > > I've got an established way of finding all of the nodes in a document and > apply a property to it. It basically takes the following command: > > <commandname="pmc.hideallnext"trace="true"> > <macrorepeatable="true"undoable="true"trace="true"> > <sequence> > <commandname="xpathSearch"parameter="%0"/> > <commandname="selectNode"parameter="self"></command> > <commandname="setProperty"parameter="[rebuildView]visible no"></command> > </sequence> > </macro> > </command> > > and runs it until it hits the end of the document. > > Originally, the xpath searches were on attribute values that were > exclusionary, so my xpath parameters looked like this: > (descendant::*|following::*)[...@arch='HyPHY20G'] > > However, we've since started supporting more than one value per attribute, > I've changed the xpath parameters to look like so: > (descendant::*|following::*)[contains(@arch, 'HyPHY20G')] > > This change has broken the feature.
I really don't see how this could be possible. Please *confirm* that using exactly the same copy of XMLmind XML Editor in the same working environment, changing back: (descendant::*|following::*)[contains(@arch, 'HyPHY20G')] to: (descendant::*|following::*)[...@arch='HyPHY20G'] will make your macro work and then restoring: (descendant::*|following::*)[contains(@arch, 'HyPHY20G')] will break it again. > When I run the commands one at a time from the command window, they still > work. When I try to run it as a complete command, I get "CANNOT EXECUTE" > messages in the console for the selectNode and setProperty commands. >
