User contributions
Jump to navigation
Jump to search
- 14:33, 30 September 2014 diff hist +22 m LlJsonValueType "rope" added to show position
- 14:25, 30 September 2014 diff hist +52 m LlJsonValueType at least SOME output would be good.
- 14:22, 30 September 2014 diff hist +2 m LlJsonValueType small bugs
- 14:02, 29 September 2014 diff hist −3,547 m Talk:Combined Library false alert. it was just a bug in my debugger. current
- 13:52, 29 September 2014 diff hist −251 m Combined Library →Unicode Integer to UTF8: sad undo
- 13:52, 29 September 2014 diff hist −33 m Combined Library →Unicode Integer to UTF8
- 13:52, 29 September 2014 diff hist 0 m Combined Library →Unicode Integer to UTF8: nah wrong alert. could not reproduce results. possibly confused something else
- 12:46, 29 September 2014 diff hist +3,547 Talk:Combined Library →CombinedLibrary.zip: and it did it. I fixed 7 year old "unnoticed" bug in UnicodeIntegerToUTF8().
- 12:12, 29 September 2014 diff hist +289 Combined Library →Unicode Integer to UTF8: guess whop just fixed a bug that went unnoticed for 7 years and that was falely blamed on utf8 representations... OLLJ OH, thats me, YAY
- 10:52, 29 September 2014 diff hist +150 m UTF-8 →Limits: HAH that solves one conundrum! . i almost missed it... stupud hexadecimal representation always confuses me unneccessarily. function is simply poorly defuined for high ranges
- 10:48, 29 September 2014 diff hist +10 m UTF-8 →Limits: 2^20+2^16... but why does it start to fail at this value and not earlier (except for the simpler ealier ranges)
- 10:39, 29 September 2014 diff hist +53 m UTF-8 U+FFFE detailing
- 10:32, 29 September 2014 diff hist +12 m UTF-8 →Limits: i think i might "solve" these, except for U+FFFE, which is "broken by design" and has to be skipped, i think i can fix this.... 2^11 and 1114112 are just too strange to be coincidence
- 10:25, 29 September 2014 diff hist −1 m UTF-8 →Limits: syntax fix
- 10:24, 29 September 2014 diff hist +91 m UTF-8 →Limits: + wikipedia link about U+FFFE (and U+FFFF)
- 10:17, 29 September 2014 diff hist +183 m UTF-8 →Limits: tested 2x times, [65534..65535] was a false alert, while [65534] persists as "INVALID CHARACTER"
- 09:41, 29 September 2014 diff hist +62 m UTF-8 i dont think this is due to special utf8 characters. i think one case of one of these functions may simply be wrong!
- 00:27, 29 September 2014 diff hist +1 m LlJsonGetValue confused left and right
- 01:30, 27 September 2014 diff hist +36 m UTF-8 →General Use: the => These
- 01:29, 27 September 2014 diff hist +19 UTF-8 oh this was supposed to go into the == General Use== section...
- 01:27, 27 September 2014 diff hist +1,871 UTF-8 →General Use: i found some numerical ranges were these functions seem to UTTERLY FAIL !!!
- 04:41, 15 September 2014 diff hist +286 LlJson2List #example that makes sense, under some conditions
- 04:27, 15 September 2014 diff hist +430 LlJson2List +1 barely useful example, except to compress json string size a little bit
- 04:14, 15 September 2014 diff hist +888 LlList2Json +examples (and suggestions for more)
- 03:55, 15 September 2014 diff hist +18 m LlJsonGetValue paragraph in caveats typos, double sentences
- 03:52, 15 September 2014 diff hist +1 m LlJsonGetValue its |caveats= and not |caveats
- 03:50, 15 September 2014 diff hist +920 LlJsonGetValue
- 03:36, 15 September 2014 diff hist +195 LlJsonSetValue
- 19:16, 10 September 2014 diff hist +132 m LlJsonGetValue true dat
- 19:14, 10 September 2014 diff hist −47 m LlJsonGetValue -1 line of comment
- 19:12, 10 September 2014 diff hist +17 m LlJsonGetValue tested and colpiles on mono
- 19:10, 10 September 2014 diff hist +500 LlJsonGetValue better style
- 18:58, 10 September 2014 diff hist +379 m LlJsonGetValue more drafting
- 18:52, 10 September 2014 diff hist +927 m LlJsonGetValue basic syntax examples of the list parameter and the results it might cause
- 18:38, 10 September 2014 diff hist +159 m LlJsonGetValue first example is a reasonable redirect
- 18:35, 10 September 2014 diff hist −227 LlJsonValueType -30 syntax errors (ran trough mono compiler -nonsense that differenciated data typers for numbers. it's all floats as short strings for JSON !!!
- 18:19, 10 September 2014 diff hist +251 m LlJsonValueType closing comment
- 18:16, 10 September 2014 diff hist +111 LlJsonValueType
- 18:15, 10 September 2014 diff hist +42 m LlJsonValueType -1 dumb syntax error , forgot a llJsonGetValue(xxx,[i]) conversion
- 18:12, 10 September 2014 diff hist −7 m LlJsonValueType -1 syntax error; uncommented comments.
- 18:10, 10 September 2014 diff hist +8 m LlJsonValueType -1 syntax errir. "integer" data type not set as data type
- 18:09, 10 September 2014 diff hist +132 m LlJsonValueType more formatting
- 18:06, 10 September 2014 diff hist −1 m LlJsonValueType woupld
- 18:05, 10 September 2014 diff hist −21 m LlJsonValueType made 1 sentence less repetitive
- 18:03, 10 September 2014 diff hist −110 m LlJsonValueType duplicate comment that explains the same case twice is removed
- 18:00, 10 September 2014 diff hist +2 m LlJsonValueType typo in outdated comment
- 17:59, 10 September 2014 diff hist +5,278 LlJsonValueType the first example is more like pseudo-code that is lossibly very buggy. but it is a practical starting example
- 15:55, 30 August 2014 diff hist +682 LlAcos added an example, applying "the law of cosines"
- 13:09, 28 August 2014 diff hist −187 m Spherical Normal maps sorting paragraphs, fixing and cutting current
- 13:03, 28 August 2014 diff hist +1,040 Spherical Normal maps →Planar sculpt maps work just fine on all PRIM_SCULPT_TYPE_SPHERE sculpted prims