GetVordText Version Difference

Thank you for the sample project that clearly shows the different behavior. It appears this change was introduced in v22.1.3 as part of a change to address the behavior you previously posted about.

In your sample you show that calling GetWordText for the offset between the "e" and "." in "Console." returns "." as the word text in v22.1.1 and "Console" as the word text in v22.1.4. The word break finder for "Console." is finding two words ("Console" and ".") and the given offset is positioned equally between both words.

So which word is the current word? The change made in v22.1.3 looks for the more significant character on either side of the offset and returns the word associated with the more signficant character. Technically this change was made to a GetWordTextRange method, but does inadvertently affect GetWordText.

While we believe the current logic is more accurate, we do see how the change has impacted the GetWordText method and should have been delayed until a more significant release.

To help us better understand your scenario, can you explain if you prefer "." to be the current word in this scenario or is the issue simply that the change has negatively impacted application behavior? Perhaps you could provide some specific examples from your application with an explanation on why one word is preferred over another?

Is the positioning of the GetWordText method just to get the text?

We use this method to obtain the text at the specified position in the automatic completion grammar service.

For example:

Console.|WriteLine

Our cursor is at the position of offset 8. At this time, we want to get the content "." in front of the cursor to determine whether the auto-complete list needs to pop up.
But currently this method returns "WriteLine" at offset 8 and "Console" at offset 7.

Hello,

We are adding an ITextSnapshot.GetWordText method overload for the next maintenance release that accepts an affinity argument.  You will be able to pass TextOffsetAffinity.Far to get the original behavior you want, which always scans forward for a word.