Graham Samuel wrote:
> Well, I am happy to be wrong, so I repeated exactly what you did, of
> course using my own bit of styled text. It didn’t work - partly
> because I can only select the text in the field itself in ‘run’ mode,
> but I can only see the Inspector in ‘edit’ mode. When I switch be
Just saw an improvement in my code that *should* make it happy to work with
Unicode characters…
local OkayChars = ""
function CleanASCII3 DerText if OkayChars = "" then -- construct OkayChars
string as needed repeat with K1 = 32 to 126 put numToChar (K1) after
OkayChars end repeat
While Bob Sneidar's function should do the job of scrubbing weird characters
from text, am unsure why he felt the need to construct that massive pCustomList
variable. Seems to me that it would be simpler, and perhaps quicker, to do this
instead:
function cleanASCII2 DerASCII put "" into DerRezu
Graham,
If you click the lock icon on the property inspector while you’re in edit mode,
the PI for that object will remain open when you switch back to run mode.
Hope this helps.
Devin
> On May 19, 2020, at 3:10 PM, Graham Samuel via use-livecode
> wrote:
>
> Well, I am happy to be wrong,
Well, I am happy to be wrong, so I repeated exactly what you did, of course
using my own bit of styled text. It didn’t work - partly because I can only
select the text in the field itself in ‘run’ mode, but I can only see the
Inspector in ‘edit’ mode. When I switch between the two modes, I can’t
I was trying the same thing in LC 9.6 (dp4) and it works here. It works both
when selecting the text in the text pane in the navigator or selecting text in
the field itself.
Regards
Tore Nilsen
> 19. mai 2020 kl. 19:53 skrev Richard Gaskin via use-livecode
> :
>
> I just tried this recipe:
>
Graham Samuel wrote:
> To an ordinary LC developer, if you can change the properties of the
> initial text (to a different size for example) without overtly
> selecting it, then the same behaviour can be expected from the IDE
> when trying to change text you’ve pasted in. It may or may not be
> s
Well, Tore, I think this is a rather purist view! To an ordinary LC developer,
if you can change the properties of the initial text (to a different size for
example) without overtly selecting it, then the same behaviour can be expected
from the IDE when trying to change text you’ve pasted in. It
I had to write a function that returns only true ASCII printable characters
because when I performed a drag/drop operation from a searchable PDF, I
discovered that Acrobat puts all kinds of hidden characters in the text that
really messes with LC. It’s a simple function:
FUNCTION cleanASCII pSt
I am not sure this is a bug. When you use the normal paste function you
actually paste in styled text. New text, following the text you pasted in will
inherit the styling of the last character of the text you pasted into the
field. This then would work the same way as if you selected some text i
Yep, that was it! I had pasted some text from elsewhere. The text **looks**
perfectly normal (and the count of characters is the same as in the visual
representation of them, so none apparently hidden), but in some way it must
mess up the functioning of the Property Inspector. As Ralph confirms,
Works OK on Mac and PC here LC 9.6 rc1. I created new stack put in a label
field. I did not change the default text. Could it be the actual text you put
in the field causing the PI problem for you?
Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net
-Original
Graham Samuel wrote:
> I’m using LC 9.6.0 rc1 on a Mac. Just now I did something very simple
> that didn’t work. I created a label field, opened the Property
> Inspector for the field and changed its text - that worked. Then I
> attempted to change the font size - that didn’t work. The appearance
13 matches
Mail list logo
