Re: Not many people know this.

In fact, one can "fine tune" this operation to have this sort of effect: put the number of chars in fld "ff" into NF if char NF of fld "ff" = "a" then set the textFont of char NF of fld "ff" to "MonsterMash" else set the textFont of char NF of fld "ff" to "UsualBoring" end if Richmond. On

Re: Not many people know this.

*Mucking around further, I discovered one can set the textFont for ** **a char that does NOT exist, this is extremely useful insofar as ** **one does not have to populate 100s of buttons with "corrective" code:** ** **on mouseUp** ** put "x" after fld "ff"** ** put the number of chars in fld "

Re: Not many people know this.

u r right...did not know this ...cool trick. ..so if i want a fontawesome icon at the beginning of a paragraph. i can do that and not use imagesource. great tip. On Thu, Aug 16, 2018 at 6:43 AM, Richmond Mathewson via use-livecode < use-livecode@lists.runrev.com> wrote: > *Mucking around

Re: Not many people know this.

I thought I had the last tape of me doing that destroyed! DAMN YOU RASPUTIN!!! Bob S > On Aug 16, 2018, at 02:32 , Richmond Mathewson via use-livecode > wrote: > > No: I know that that will not make many of you run out into the road madly > waving your > underpants over your heads shout

Re: Not many people know this.

On 2018-08-16 11:32, Richmond Mathewson via use-livecode wrote: Possibly I am reinventing the wheel here: set the textFont of word 3 to "Charcoal" This IS incredibly useful when one is typing to Mum in Sanskrit (as one does) and wants to use a variant glyph (as one does continuously) as it allo

RE: Not many people know this.

t 16, 2018 8:12 AM To: How to use LiveCode Cc: Mark Waddingham Subject: Re: Not many people know this. On 2018-08-16 11:32, Richmond Mathewson via use-livecode wrote: > Possibly I am reinventing the wheel here: > > set the textFont of word 3 to "Charcoal" > > This IS i

Re: Not many people know this.

Clarence wrote: > So, is this the same thing as the "paragraph" property? I find that > this is also super useful. Related, but different enough to draw attention to. AFAIK all xTalks have supported styled text. It may be that HC 1.0 only provided that for the whole field (I can't recall), bu

Re: Not many people know this.

On 2018-08-16 19:48, Richard Gaskin via use-livecode wrote: I'm not sure if this info has been incorporated into the docs system yet, but the Release Notes for v5.5 offer a solid overview of the new field features (starting on p12), most of which are paragraph-level properties like indent, border

Re: Not many people know this.

On Aug 16, 2018, at 11:48 AM, Richard Gaskin via use-livecode mailto:use-livecode@lists.runrev.com>> wrote: Paragraph-level formatting opens up wholly new opportunities, beyond any xTalk I've ever seen. I'm not sure if this info has been incorporated into the docs system yet, but the Release

Re: Not many people know this.

Of course it was too good to last . . . I merrily filled a field up with a series of letters from 2 different fonts and then did this: * **set the text of fld "f2" to the text of fld "f1"* and all my font stuff disappeared and everything ended up in the textFont of field "f2". So . . . The

Re: Not many people know this.

On Aug 16, 2018, at 1:01 PM, Richmond Mathewson via use-livecode mailto:use-livecode@lists.runrev.com>> wrote: Of course it was too good to last . . . I merrily filled a field up with a series of letters from 2 different fonts and then did this: * **set the text of fld "f2" to the text of fld

Re: Not many people know this.

Sorry, did somebody just give me an excuse to indulge in nostalgia? On 16/08/2018 18:48, Richard Gaskin via use-livecode wrote: AFAIK all xTalks have supported styled text.  It may be that HC 1.0 only provided that for the whole field (I can't recall), It was definitely the case that HC 1.0 on

RE: Not many people know this.

d Gaskin via use-livecode Sent: Thursday, August 16, 2018 10:49 AM To: use-livecode@lists.runrev.com Cc: Richard Gaskin Subject: Re: Not many people know this. Clarence wrote: > So, is this the same thing as the "paragraph" property? I find that > this is also super useful. Rela

Re: Not many people know this.

On Thu, Aug 16, 2018 at 1:21 PM Mark Waddingham via use-livecode < use-livecode@lists.runrev.com> wrote: > > P.S. You can largely thank Trevor for the above additions, in particular > the styledText and metadata - in terms of providing use-cases which led > to their design and implementation. > >

Re: Not many people know this.

On 08/16/2018 11:21 AM, Mark Waddingham via use-livecode wrote: reason we treat that particular 10,000 odd lines of code with a great My goodness. I thought I was the only one who wrote odd lines of code... -- Mark Wieder ahsoftw...@gmail.com ___

Re: Not many people know this.

On 8/16/18 7:49 AM, Richard Gaskin via use-livecode wrote: > but the Release Notes for v5.5 offer a solid overview of the new > field features (starting on p12), I keep that! it is golden. I think they replaced it with a stack showing all the features, I can't find it now. But setting the array

Re: Not many people know this.

re: Stack versioning: I personally do that using Git/GitKraken. Any suggestion how it should work? re: text styles: you can edit the contents of any field (hidden/locked, whatever) in Navigator. You can convert the editor on the fly from showing the styled text to the HTMLtext of the field, which

Re: Not many people know this.

Just a footnote here... there is actually documentation on paragraph styles, in our lessons portal: http://lessons.livecode.com/m/4071/l/58674-how-do-i-style-paragraphs-in-a-field The lessons portal is a rich sour

RE: Not many people know this.

2018 10:41 PM To: How to use LiveCode Cc: Geoff Canyon Subject: Re: Not many people know this. re: Stack versioning: I personally do that using Git/GitKraken. Any suggestion how it should work? re: text styles: you can edit the contents of any field (hidden/locked, whatever) in Navigator. You c

Re: Not many people know this.

What would be the benefit of typing code on only odd numbered lines? Bob S > On Aug 16, 2018, at 17:56 , Mark Wieder via use-livecode > wrote: > >> reason we treat that particular 10,000 odd lines of code with a great > > My goodness. I thought I was the only one who wrote odd lines of code

Re: Not many people know this.

Ah! a replacement for Word you say! That will teach Microsoft! Bob S > On Aug 16, 2018, at 21:42 , Sannyasin Brahmanathaswami via use-livecode > wrote: > > Someday someone should go a menu like inDesign so that you can "do text" > from a WSIWIG menu. > I know Andre has one but he didn't even

Re: Not many people know this.

On 2018-08-17 02:56, Mark Wieder via use-livecode wrote: On 08/16/2018 11:21 AM, Mark Waddingham via use-livecode wrote: reason we treat that particular 10,000 odd lines of code with a great My goodness. I thought I was the only one who wrote odd lines of code... Haha! I didn't even see th

Re: Not many people know this.

I have a habit of saying "ish" and "odd" in that context , so I'm in very good company. And I'm jealous of your hairline ;-) Lagi On Fri, 17 Aug 2018 at 17:09, Mark Waddingham via use-livecode < use-livecode@lists.runrev.com> wrote: > On 2018-08-17 02:56, Mark Wieder via use-livecode wrote

Re: Not many people know this.

It is easier to proof double spaced lines... > What would be the benefit of typing code on only odd numbered lines? > > Bob S > > >>> On Aug 16, 2018, at 17:56 , Mark Wieder via use-livecode >>> wrote: >>> >>> reason we treat that particular 10,000 odd lines of code with a great ___

Re: Not many people know this.

On 08/17/2018 05:51 PM, James At The Hale via use-livecode wrote: It is easier to proof double spaced lines... What would be the benefit of typing code on only odd numbered lines? ...that way I could put a comment after each line (ducking)... -- Mark Wieder ahsoftw...@gmail.com __