Add evas_textblock_cursor_is_inside_word_get API to determine whether cursor is
inside a word or is pointing to a word break character.
Signed-off-by: Shilpa Singh <shilpa.singh@samsung.com>
@feature
Details
Details
API should return EINA_TRUE if cursor is inside word else EINA_FALSE, test case also updated
Diff Detail
Diff Detail
- Repository
- rEFL core/efl
- Branch
- textblock
- Lint
No Linters Available - Unit
No Unit Test Coverage - Build Status
Buildable 967 Build 1032: arc lint + arc unit
This comment was removed by shilpasingh.
Comment Actions
What's the purpose of this API? Also, the naming of this API does not conform with our naming convention. The correct naming would be:
evas_textblock_cursor_word_is_inside(), but even that is not a good name. Maybe evas_textblock_cursor_word_is() would be better.
Anyhow, I don't understand the purpose of this API, more info would be appreciated.
Comment Actions
How about evas_textblock_cursor_is_inside_word_get
some what similar to name evas_textblock_cursor_format_is_visible_get
and also purpose becomes clearly understandable?
else evas_textblock_cursor_word_is() also seems fine.
Purpose:
For requirements/applications which track input and need to know when was word inputted. For e.g:
Spellchecker: In entry changed, the Input text is monitored continuously and once its known that word was successfully inputted, the word is sent for spellchecking and not just that this API is also used for further other
logic's as well. (as this API gives more control)
Applications which track word input will need this, say for e.g: Transliteration
I am using english keyboard and once I have entered the word successfully, that word gets replaced by original
script, if not for above API, I wont know when to actually replace
Comment Actions
sorry shilpa! this one seems to have languished. i think it's time to push it along again. @tasn - yes name will have to change and interfaces api makes all of this be different now. i can see this as convenient.
Comment Actions
@raster, I changed the name from evas_textblock_cursor_is_inside_word to evas_textblock_cursor_is_inside_word_get based on @tasn comment
some what similar to name evas_textblock_cursor_format_is_visible_get
and by this name it looks like the purpose of API becomes clearly understandable
what do you think? @tasn also suggested below name
evas_textblock_cursor_word_is() should I use this name?
and anyother change is needed?