Community

Posted: **Tue Nov 22, 2016 2:28 pm**

I've noticed this issue/change in behavior in TextPad 8.1.0. Version 8.0.2 works as expected.

I use TextPad for coding.

Code: Select all

import java.util.Hashtable;

In 8.0.2, if you double-click on the letter "u" above, only the letters "util" are highlighted/selected: the selection does not include either full stop/period. This is the behavior I have come to expect.

However, in 8.1.0, if you do the same, then all of "java.util.Hashtable" becomes highlighted/selected. Somewhere along the way, full stops became included in the set of characters that a double-click selects.

The syntax file I use for Java has not changed, so no full stops were added there. Nor did I change/add to any of the characters specified at Configure > Preferences > Document Classes > Java > Syntax, "Other characters in words".

Can TextPad's behavior be reverted in this regard, so that a double-click within a word still honours full stops as delimiting characters, and are not included in the selection?

Thank you.

Posted: **Tue Nov 22, 2016 3:19 pm**

Has
View | Document Properties | Syntax | Other characters in words
become changed for any of your Java files?

Posted: **Tue Nov 22, 2016 3:58 pm**

ben_josephs wrote:Has
View | Document Properties | Syntax | Other characters in words
become changed for any of your Java files?

No change.

Posted: **Tue Nov 22, 2016 4:02 pm**

I have no ideas, I'm afraid. I can't reproduce what you're reporting.

Posted: **Tue Nov 29, 2016 9:15 pm**

Have any of the keywords in the syntax definition file got a "." in them?

Posted: **Wed Nov 30, 2016 2:34 pm**

bbadmin wrote:Have any of the keywords in the syntax definition file got a "." in them?

Yes.

From java1_6.syn:

Code: Select all

...
AbstractDocument
AbstractDocument.AttributeContext
AbstractDocument.Content
AbstractDocument.ElementEdit
AbstractElementVisitor6
...

So I suppose This Is The Way It Is Now?

Thanks,

Art.

Posted: **Wed Nov 30, 2016 5:32 pm**

That's what's causing it, as documented on the Syntax property page for the document class. You can avoid that by moving fields such as AttributeContext and Content to a [Keywords 3] section, although they could then show up as keywords divorced from AbstractDocument.

Community

Change In 8.1.0: Full Stop Now Included in "Words"

Change In 8.1.0: Full Stop Now Included in "Words"