-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Newline not working #3
Comments
It is a known limitation that selections ignore line breaks, so the selection will just keep going off the end of the line, until an area equal to that of the keyword string is marked. The shape of a multi-line selection is simply not a rectangle. That's the root issue. We are considering a neat solution where a selection may be broken up into multiple subselection, each of which is a rectangle. As for operators, not all are called by every document, as some of them (like T-star and double qoute) are redundant, or short hand/syntactic sugar. |
Ok, i do need it for my current project so i'm working on a solution myself (which i'll obviously share when i made it). About the opertors, i did notice that Tm gets called a lot (at least at each new line), cant we do something with that? |
Thanks, I'd really appreciate any contribution. Yeah, for each Tm (commonly representing line breaks) we could "cut" the selection. I mean, finalize it as if it was really the end of the keyword, but then start a new selection and keeping pointers between consequtive selection rectangles. BTW, ain't that "close" button the worst? ;) Keep hitting it by mistake too... |
Ah I see, guess I misread the adobe documentation. But that would work. And yes, it is a bit weird, they should color it red or something :P |
Thing is, while Tm marks a new line, it doesnt mark the end or position of the previous, so we'll have to figure something else for that. |
That would be the current state, just before the Tm arrives. The framework constantly keeps the current rendering state up to date. |
But for some reason, the current rendering state's line and testmatrix are identity matrices. |
(at that point) |
nvm, its due to BT, i can just store the coordinates just before that point. Will come back when i have the final solution ;) |
any progress? |
No. |
When searching for a string that covers multiple lines, the frame comes out wrong. This is due to the fact the search doesn't seem to account multiple lines (while i think this is implemented). I did notice that T* ' and "" operators are set up, but they aren't being called.
The text was updated successfully, but these errors were encountered: