On 11/22/2011 12:26 PM, Manuel Collado wrote: > El 22/11/2011 11:02, Hussein Shafie escribió: >> On 11/22/2011 10:29 AM, Yves Forkl wrote: >>> Am 22.11.2011 09:19 schrieb Hussein Shafie: >>> >>>> The split command is a generic command which works with any document >>>> type, with or without a configuration. >>>> >>>> This command leverages the schema to determine whether the document >>>> after splitting the explicitly selected element in two at caret >>>> position would still be valid. If this is the case, the split command >>>> should work fine, otherwise it is disabled (grayed). >>> >>> Does this mean that split will never work when I am unable to find a caret >>> position within my list instance at which the split command becomes >>> enabled, with the whole list explicitly selected? >>> >> >> That's right. > > This would be a typical use case for the "virtual caret" suggested in a > previous message. Besides making simpler the automatic scroll policy, it > would also allow extending the scope of the split command. >
OK. >> >>> Can you explain this on the basis of the structure info below? >>> >>> My list instance looks like: >>> >>> <labeledlist> >>> <labeledlistitem> >>> <itemlabel>One.</itemlabel><listitem><para>Item 1.</para></listitem> >>> </labeledlistitem> >>> <labeledlistitem> > ^------------------- putting the "virtual caret" here > >>> <itemlabel>Two.</itemlabel><listitem><para>Item 2.</para></listitem> >>> </labeledlistitem> >>> </labeledlist> > > and selecting the<labeledlist> element would enable the split command > for this case. > > I understand than the "virtual caret" concept can be really difficult to > implement, and certainly requires more deep thoughts. So I don't expect > anything in the near or medium-term future, but I still think it is is > an idea worth to consider in the long term. > Thank you for your suggestion. -- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
