Thank you, but unfortunately this only helps me a small bit.
If these filters are never meant to be presented to the users as "option
filters", why do these still inherit from SWOptionFilter? Note that
GreekLexAttribs and PapyriPlain are inserted into SWMgr::optionFilters
by SWMgr::init(). Why is
Thanks Troy,
Is it safe to assume that the example you gave for the Duke Databank of
Documentary Papyri
( http://papyri.info/docs/ddbdp )
is for use with some specialist software that's based on SWORD ?
i.e. Not one of our well-known front-ends.
Just updated
Not looking at the code, but quickly I can comment that the PapyriPlain
filter is used with the Duke Databank of Papyri as a LocalOptionFilter
(not added to the list of global options presented to the user to
toggle, but can still be toggled programmatically). Hope this helps.
Troy
On
On 27.10.2016 22:54, Jaak Ristioja wrote:
> Hi!
>
> While refactoring some option filters code for Sword++ I found two
> strange option filters, GreekLexAttribs and PapyriPlain which inherit
> from SWOptionFilter and use SWOptionFilter::SWOptionFilter(). This
> behavior was introduced in SVN
