difference in script editor, missing a few pixels and a crash
Moderator: Klaus
difference in script editor, missing a few pixels and a crash
Hi,
anyone has this issue too?
The character 1 is missing a few pixels in the right upper corner.
This is lc9rc1 this is lc819 i see also differences in thickness while the same font and size is used.
second thingy
Also had 3 times a crash which i could exactly replicate those 3 times and after that no more...
turned messages off-->i opened a stack-->got an error in script (which LC throwed up when opening the stack) -->open script-->i saw that End openStack was in the wrong place (it was caused by creating a new handler while hitting the return key)-->then wanted to copy/paste that line, i selected it and then hit CTRL-X-->LC9rc1 crashed
After this i repeated it a few times to be able to write it down for a bug report, but after the 3rd or 4th time it did not crash anymore, so...
regards,
Sphere
anyone has this issue too?
The character 1 is missing a few pixels in the right upper corner.
This is lc9rc1 this is lc819 i see also differences in thickness while the same font and size is used.
second thingy
Also had 3 times a crash which i could exactly replicate those 3 times and after that no more...
turned messages off-->i opened a stack-->got an error in script (which LC throwed up when opening the stack) -->open script-->i saw that End openStack was in the wrong place (it was caused by creating a new handler while hitting the return key)-->then wanted to copy/paste that line, i selected it and then hit CTRL-X-->LC9rc1 crashed
After this i repeated it a few times to be able to write it down for a bug report, but after the 3rd or 4th time it did not crash anymore, so...
regards,
Sphere
Re: difference in script editor, missing a few pixels and a crash
I haven't noticed any chopped off tops on this machine (sparky linux, debian testing), but I do see other ... weirdness when using the SE.
When I set the color to custard in the preferences, for instance, it looks more like pinkish. If I type rapidly, which is most of the time, it seems like it falls behind quite a bit. The abnormal looking text I get, but bumping the size to 13 or 14 seems to fix that here (font: free sans). I definitely don't care for the sourcecode pro font it defaulted to

When I set the color to custard in the preferences, for instance, it looks more like pinkish. If I type rapidly, which is most of the time, it seems like it falls behind quite a bit. The abnormal looking text I get, but bumping the size to 13 or 14 seems to fix that here (font: free sans). I definitely don't care for the sourcecode pro font it defaulted to



Re: difference in script editor, missing a few pixels and a crash
Thanks bogs, i will create a bug report
Re: difference in script editor, missing a few pixels and a crash
No problems. Love your sig by the way
Hint: you may want to switch the 'c' and 'i' below

Hint: you may want to switch the 'c' and 'i' below

...not mentioning the startup speed, whcih we now have again with SSD

-
- VIP Livecode Opensource Backer
- Posts: 10043
- Joined: Sat Apr 08, 2006 7:05 am
- Contact:
Re: difference in script editor, missing a few pixels and a crash
I wonder if this issue is perhaps somehow related to the text rendering change needed to accommodate this:
http://quality.livecode.com/show_bug.cgi?id=20856
http://quality.livecode.com/show_bug.cgi?id=20856
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
Re: difference in script editor, missing a few pixels and a crash
Could be? Was a bit out of my level.

Re: difference in script editor, missing a few pixels and a crash
Thanks Bogs, glad you like it 
@ Richard, i don't know for sure if it is the same, looks a bit like it.
Those little screenshots where taken on Win10
And these 2 are taken on Mac (well that is...Hackintosh)
lc9rc1 and lc819 did not change any default text setting

@ Richard, i don't know for sure if it is the same, looks a bit like it.
Those little screenshots where taken on Win10
And these 2 are taken on Mac (well that is...Hackintosh)
lc9rc1 and lc819 did not change any default text setting
Re: difference in script editor, missing a few pixels and a crash
I have 2 questions, whats the default font on the one that is messing up, and what happens if you change the default font to a different one?
From what that bug report said (if I understood it correctly) this mostly affected one kind of font, skia(?).
From what that bug report said (if I understood it correctly) this mostly affected one kind of font, skia(?).

Re: difference in script editor, missing a few pixels and a crash
it de faults to..Default
but it seems to be Source Code Pro 12
on size 13 and bigger it's ok
I know it's a storm in a glass of water,
but strange (or not)so different on the script editor in the lc versions
but it seems to be Source Code Pro 12
on size 13 and bigger it's ok
I know it's a storm in a glass of water,
but strange (or not)so different on the script editor in the lc versions
Re: difference in script editor, missing a few pixels and a crash
No, I agree with you, that source code pro font leaves a lot to be desired. I actually prefer comic sans myself a lot, reminds me of Calvin and Hobbes 


Re: difference in script editor, missing a few pixels and a crash
Hi Folks
Yes source code pro is now used as the default script editor font. Using a monospaced font in the script editor can make a significant difference to performance so we decided to bundle an open source font designed for coding to be the default. You can of course change this to whatever you want.
As far as the missing pixels goes that does look quite odd so thanks for the report!
Yes source code pro is now used as the default script editor font. Using a monospaced font in the script editor can make a significant difference to performance so we decided to bundle an open source font designed for coding to be the default. You can of course change this to whatever you want.
As far as the missing pixels goes that does look quite odd so thanks for the report!
LiveCode User Group on Facebook : http://FaceBook.com/groups/LiveCodeUsers/