On Thursday, March 28, 2024 2:11:19 PM EDT Troy A. Griffitts wrote:
> Hi David,
>
> The weirdness you might be running into is the behavior that SWLex
> modules 'snap' their key to the nearest entry upon renderText (or
> stripText, as you are calling).
> I know this doesn't seem completely
Hi David,
The weirdness you might be running into is the behavior that SWLex
modules 'snap' their key to the nearest entry upon renderText (or
stripText, as you are calling).
I know this doesn't seem completely intuitive, but I would try calling
stripText BEFORE calling getKeyText(). I
On Wednesday, March 27, 2024 4:10:30 PM EDT David "Judah's Shadow" Blue wrote:
> I'm still at a loss here. I've tried changing things to where I use a SWKey
> and use setText() there and called setPersist(true) and use that to set the
> module key. All to no avail. getKeyText(); is consistently
On Tuesday, March 26, 2024 1:01:36 PM EDT David "Judah's Shadow" Blue wrote:
> On Monday, March 25, 2024 4:06:19 PM EDT David "Judah's Shadow" Blue wrote:
> > On Monday, March 25, 2024 1:52:40 PM EDT David "Judah's Shadow" Blue
wrote:
> > > I've noticed a problem with lexicons not always getting
On Monday, March 25, 2024 4:06:19 PM EDT David "Judah's Shadow" Blue wrote:
> On Monday, March 25, 2024 1:52:40 PM EDT David "Judah's Shadow" Blue wrote:
> > I've noticed a problem with lexicons not always getting a value from
> > getKeyText(). It's intermittent, and I can't quite nail down why I
On Monday, March 25, 2024 1:52:40 PM EDT David "Judah's Shadow" Blue wrote:
> I've noticed a problem with lexicons not always getting a value from
> getKeyText(). It's intermittent, and I can't quite nail down why I would be
> getting empty strings when I call it sometimes.
Investigating further,
