Had a chat with Konstantin on IRC today. We agreed to go for a1-a3 for now. In
addition, iteration will start at -1 (ie. an invalid boundary), so that you can
get all info by doing a loop starting with toNextBoundary().
But it needs to go in before beta 2, and all usages of QTBF in qt5.git and
Anyone?
Konstantin
2012/9/10 Konstantin Ritt :
> Hi folks,
>
> In fact, the current QTBF behaves just like if it were a broken break
> iterator...
> I mean that, [Issue1] despite it's name, it stops at every break
> opportunity and reports NotAtBoundary via boundaryReasons() method for
> the bre
Hi folks,
In fact, the current QTBF behaves just like if it were a broken break
iterator...
I mean that, [Issue1] despite it's name, it stops at every break
opportunity and reports NotAtBoundary via boundaryReasons() method for
the break opportunities that are not boundaries (this affects Line and
