Author |
Message |
linyifei
Joined: 2012-01-19 03:18:40 Posts: 196 Location: Sydney, Australia (UTC +10)
|
Since upgrading to Cool VL Viewer 1.26.4.72 from 1.26.4.65 (Mac versions) I have noticed an annoying glitch when editing text in the viewer. When cut/pasting text, a spurious character seems to be being attached to the end of the last line. This extra character seems to be handled differently in different parts of the viewer environment. When pasting text into a chat-line, it appears as a small black box. In editing a notecard, it appears as a question-mark. When editing a script it appears as a box that acts like a carriage return/line feed which confuses the script editor.
Has anyone else observed this, or should I start looking for some issue at my end?
|
2013-05-30 07:16:17 |
|
|
Atashi
Joined: 2013-02-02 22:15:52 Posts: 35
|
I have seen this as well. I think I first noticed it with 1.26.4.71 and it's still there in 1.26.4.72. It looks to me like some kind of control character or other special character.
I see it when copy -pasting within the viewer eg. from chat history to a notecard or script window, or from an external program and into the viewer.
|
2013-05-30 17:53:12 |
|
|
linyifei
Joined: 2012-01-19 03:18:40 Posts: 196 Location: Sydney, Australia (UTC +10)
|
Yeah, I have spoken to a couple of my Cool VL Viewer-using friends in-world and they're seeing this too.
Henri, should I open a new thread in the Bug Report section, or will this do?
|
2013-05-31 00:21:45 |
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 5545
|
I am sorry, but MacOS-X specific bugs are beyond my scope of investigations (I don't have access to any MacOS-X computer)...
|
2013-05-31 00:23:47 |
|
|
linyifei
Joined: 2012-01-19 03:18:40 Posts: 196 Location: Sydney, Australia (UTC +10)
|
Ah... So this problem does not occur on Windows or Linux versions? I obviously talk to too many Mac users!
|
2013-05-31 00:30:50 |
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 5545
|
No, I cannot reproduce this issue here, under Linux/Windows... Note that each OS got a specific "end of line" marker: UNIX/Linux uses a "line-feed" (LF), DOS/WIndows uses both a "cariage return" and a "line-feed" (CR/LF) and Macs use a cariage return (CR)... Of course, if you copy some text (from a text editor supporting all three formats for example) with a different end of line marker than the one natively used by your OS, you will encounter weird characters at the end of lines...
|
2013-05-31 07:33:10 |
|
|
linyifei
Joined: 2012-01-19 03:18:40 Posts: 196 Location: Sydney, Australia (UTC +10)
|
Thank you for confirming that this was Mac-specific, Henri. I am aware that different OS handle "end of line" differently, but I am seeing the problem copy/pasting within the viewer environment. I cannot imagine that this has been caused by a change in the Cool VL Viewer code, so I am scratching my head as to the cause. Could someone with experience in building apps under OS/X comment please?
|
2013-05-31 23:50:51 |
|
|
Atashi
Joined: 2013-02-02 22:15:52 Posts: 35
|
I think it started with the build 2 weeks ago today. My memory is terrible though for details like that.
I wonder if this has to do with switching compilers from gcc 4.0 to the llvm 4.2 version? Maybe something funky in there. Alternatively maybe there's something fairly common in the build that changed from around .69 to .70
|
2013-06-01 20:08:29 |
|
|
linyifei
Joined: 2012-01-19 03:18:40 Posts: 196 Location: Sydney, Australia (UTC +10)
|
I'm not sure if it is related, but I also find that it is impossible to cut/paste between fields in the editor, which is a bit annoying when building.
|
2013-06-03 13:15:43 |
|
|
linyifei
Joined: 2012-01-19 03:18:40 Posts: 196 Location: Sydney, Australia (UTC +10)
|
Sorry about the duplicate post above. I've done some more testing on this, and I find that Copy/Paste is fairly comprehensively broken in the Mac version. I cannot copy/paste when renaming folders or objects in inventory, for example.
Everything was working fine in 1.26.4.65. I have tested the builds subsequent to that, and the problem seems to date from 1.26.4.70, which was the first built with llvm-gcc-4.2 rather than gcc-4.0, according to the announcement posting.
Katherine, can you comment on this at all?
|
2013-06-05 01:53:37 |
|
|