[opensource-dev] VWR-20094 - Maybe still a hope for scripters with viewer 2?
Dave Booth
dave at meadowlakearts.com
Fri Sep 24 07:27:38 PDT 2010
On 9/24/2010 08:49, Opensource Obscure wrote:
> On Fri, 24 Sep 2010 08:38:38 -0500, Dave Booth<dave at meadowlakearts.com>
> wrote:
>> On 9/24/2010 04:57, Satomi Ahn wrote:
>>> Hello all,
>>>
>>> I just wanted to mention that I found how to fix the bug that was
>>> keeping all scripters from switching to viewer 2 (the one that made
>>> the viewer freeze on loading large scripts).
>> Oh trust me, its a good one to fix but it sure isnt "the" bug :)
>> Personally, the one that gets furthest up my nose is the cursor drift
> what is the PJIRA entry for that?
> does it affect all viewer releases?
>
> opensource obscure
>
Theres plenty of them - most refer to notecards, because the problem
shows up easier in paragraph-based stuff like notecards. The more text
you have in a "line" (which a nc will wrap as a paragraph) the worse it
gets. An explicit \n resets it but in a long code line it happens too,
particularly when you have a UI scaling to anything other than 1.0 (some
folks report it when scale>1.0, some when scale<1.0) You can click
somewhere in a line of code and start typing to insert characters and
then see them inserting several places to the left of where the click
and the blinking cursor indicate they should, or see the cursor getting
further and further ahead of the characters you're typing, if you're
typing a new line.
https://jira.secondlife.com/browse/VWR-20178 and its dupes are the
clearest description of it for notecards,
https://jira.secondlife.com/browse/VWR-18875 and
https://jira.secondlife.com/browse/VWR-21388 point it out in the script
editor
As for versions, I screamed and fled from the 2.0.x viewers... only came
back to the 2.1 beta so I can tell you its definitely in 2.1 beta and later
From a printers perspective, it looks to me very much like the kerning
and tracking data in the fonts used are a little off. This would have
least effect with UI scale = 1, but as soon as you apply a scaling
factor other than unity then it show much more rapidly - my digital
typography knowledge is a little rusty but I believe that particularly a
tracking error would grow as a square function with line length when
scaled that way. If the data in the font itself is good, then its in the
editor code.
More information about the opensource-dev
mailing list