Yes, I know I already said this is a great function... and it is, but
there does seem to be a small problem with the last [printing] char on
a line. :)
What I see in the GTK [on Windows] widget incarnation of Scintilla is
that a click *in* the last char on a line (but to the right of the
*midpoint*) is returning the -1 code for "no char close to here". All
other cases work as expected/wanted... in particular, horizontal
matching seems to give a "hit" if within half a char width to the
right or left of a char that is surrounded by spaces. So one might
assume that this would also work at the end of a line...
I have tried to get debugging prints to work from
Editor::PositionFromLocationClose(), but am having no luck with my
usual approach of inserting Windows kernel debugger calls to
OutputDebugString and monitoring the output with Dbgview from
Sysinternals - I see none of my trace messages when running in the GTK
widget environment. And I can not see anything with the
Platform::DebugPrintf stuff either, but that could be because I am not
using it correctly.
And yes, SCI_POSITIONFROMPOINT does work, but since it really does
give you the closest char even if it is a long way (inches away on the
display) from that char, it is less useful for my purpose.
Finally, I notice that when I use a SciLexer.dll with my trace
messages with SciTE, the internal functions
Editor::PositionFromLocation() and Editor::PositionFromLocationClose()
are called at a very high rate with any mouse movement - no buttons
down etc. Is this happening to support "hotspot" styles whether they
are in use or not, or is this happening for some other reason?
Robert Roessler
[EMAIL PROTECTED]
http://www.rftp.com
_______________________________________________
Scintilla-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scintilla-interest
