Re: full justification in a text field

2022-02-10 Thread Curry Kenworthy via use-livecode



Curt:

> text with full justification in a field?

Paul:

> no justified option. There is a REALLY old enhancement request
> at https://quality.livecode.com/show_bug.cgi?id=4714

Howdy,

I know how to do this perfectly, and would love to add
full justification to WordLib if there's demand/budget.

Anyone else interested?

Best wishes,

Curry Kenworthy

WordLib: Import MS Word and OpenOffice files in LiveCode!
"Dominate documents with WordLib and LC"
http://livecodeaddons.com/wordlib.html

Innovative Christian LiveCode Training and Consulting
"Better Methods, Better Results"
http://livecodeconsulting.com/

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Notarize Helper Stack in LC lesson updated

2022-02-10 Thread General 2018 via use-livecode
Hi ,

Yes, that was the issue - I was thinking the bundle ID could be the same for 
the product series and the version name and version number dictated the 
difference.

Once again thanks for the help on this.

Regards Camm

> On 10 Feb 2022, at 10:53, matthias rebbe via use-livecode 
>  wrote:
> 

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: (area used by) Keyboard in iOS 15.x

2022-02-10 Thread Mark Smith via use-livecode
Sorry, it appears I attached the wrong link. Hopefully this one works better!!

https://www.dropbox.com/s/2igqdbroxy5onf7/Test%20Layout%2013.livecode.zip?dl=0 




> On Feb 10, 2022, at 10:08 PM, Mark Smith  wrote:
> 
> Hello everyone, 
> 
> Once again thanks to the many of you who provided advice and suggestions. 
> They were really very helpful in coding up this full working example. In the 
> interests of sharing I have posted an example into a dropbox account, and 
> will upload a copy to the forums at some point. This example takes a “dummy” 
> layout of my Organize app (nothing is being saved, most features are not 
> included) and redraws the main screen to fit the target device using just 
> iPhoneSafeAreaInsets() and "the effective working screenRect" and nothing 
> else (no fullscreenmode for example). It works remarkably well. I have tested 
> it on a physical SE, 6S, 11, 12 and 13 mini and it adapts to each screen as 
> you would expect. It is remarkably satisfying to see it adapt to changes in 
> the keyboard size (predictive, not predictive) on the fly. No special code 
> was required to do this. 
> 
> You’ll need to compile the example for iPhone and use a developer profile to 
> install it on an iPhone device. The simulator does not really provide a 
> useful simulation primarily because it does not simulate the behaviour of the 
> keyboard very well (however, if you just want to see how the layout adapts, 
> it is perfectly fine for that). Its possible I have not developed the most 
> efficient method of coding the layout. If you have any suggestions, I’d be 
> most grateful to receive them.
> 
> UI tips:
> 1. tapping once on white space below the dg entries dismisses the keyboard 
> (so does the “down arrow” when it appears in the header bar).
> 2. tapping twice adds a new blank line (or inserts the cursor into an 
> existing one) (so does the “+” sign in the header bar).
> 
> The rest should be obvious, I hope. All of the layout is in the card script. 
> All of the dg code is in the dg handler and behavior script. 
> Finally, if you have any questions, please feel free to send them on.
> 
> All the best,
> Mark
> 
> https://www.dropbox.com/s/nmri0dy5j5qtc8c/test.livecode.zip?dl=0 
> 
> 
> 
> 
>> On Dec 27, 2021, at 12:05 PM, Mark Smith > > wrote:
>> 
>> Thank you Sean and Jacque, 
>> 
>> I’ve not had a chance to work on a complete solution but thought I would 
>> make a test run to see what “the effective working screenrect” was returning 
>> and as the following indicates, it does in fact take into consideration the 
>> keyboard. I just coded up one line to  run whenever the status of the 
>> keyboard changed and tried it both with and without the “predictive” option 
>> turned on. As you can see, it was very sensitive to this change…
>> 
>> without predictive:
>> 
>> 9:37:14 PM keyboardActivated 0,0,375,451
>> 9:37:15 PM keyboardDeactivated 0,0,375,667
>> 9:37:18 PM keyboardActivated 0,0,375,451
>> 9:37:19 PM keyboardDeactivated 0,0,375,667
>> 9:37:19 PM keyboardActivated 0,0,375,451
>> 9:37:23 PM keyboardDeactivated 0,0,375,667
>> 
>> 
>> with predictive: 
>> 
>> 9:56:54 PM keyboardActivated 0,0,375,407
>> 9:56:55 PM keyboardDeactivated 0,0,375,667
>> 9:56:55 PM keyboardActivated 0,0,375,407
>> 9:56:57 PM keyboardDeactivated 0,0,375,667
>> 
>> In my particular case not all 4 value are immediately useful. For example, I 
>> have a fixed header and footer that need to be accommodated so the correct 
>> “useable” rect for me is:
>> 
>> 0,69, 377, 618 (for no predictive)
>> 0,69,377,456 ( for predictive)
>> 
>> but this can easily be accommodated since the header/footer values don’t 
>> change. The beauty is I now have a rect lower bound (ie. keyboard height) 
>> that actually reflects where the keyboard is. 
>> 
>> Brilliant!! Thank you both,
>> 
>> Mark
>> 
>> Sean, I tried iPhoneSafeAreaInsets() but it appears it returns a constant 
>> set of values regardless of keyboard position on my iPhone 12
>> 
>> 11:51:22 AM keyboardActivated 0,47,0,34
>> 11:51:22 AM keyboardDeactivated 0,47,0,34
>> 11:51:26 AM keyboardActivated 0,47,0,34
>> 11:51:26 AM keyboardDeactivated 0,47,0,34
>> 
>> And didn’t change when I added / subtracted “predictive”. So, just the 
>> available usable space at the top and bottom of the screen. I haven’t 
>> adjusted my app yet to fully take advantage of the larger screen on a 12 (it 
>> was developed on a 6S) but when I get to more response design this will be 
>> useful to know where the usable top and bottom are. 
>> 
>> Cheers!!
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> On Dec 25, 2021, at 5:25 PM, Sean Cole via use-livecode 
>>> mailto:use-livecode@lists.runrev.com>> 
>>> wrote:
>>> 
>>> Another addendum to this I just noticed is in the latest RC, LC9.6.6RC1,
>>> which has iphoneSafeAreaInsets for 

Re: (area used by) Keyboard in iOS 15.x

2022-02-10 Thread Mark Smith via use-livecode
Hello everyone, 

Once again thanks to the many of you who provided advice and suggestions. They 
were really very helpful in coding up this full working example. In the 
interests of sharing I have posted an example into a dropbox account, and will 
upload a copy to the forums at some point. This example takes a “dummy” layout 
of my Organize app (nothing is being saved, most features are not included) and 
redraws the main screen to fit the target device using just 
iPhoneSafeAreaInsets() and "the effective working screenRect" and nothing else 
(no fullscreenmode for example). It works remarkably well. I have tested it on 
a physical SE, 6S, 11, 12 and 13 mini and it adapts to each screen as you would 
expect. It is remarkably satisfying to see it adapt to changes in the keyboard 
size (predictive, not predictive) on the fly. No special code was required to 
do this. 

You’ll need to compile the example for iPhone and use a developer profile to 
install it on an iPhone device. The simulator does not really provide a useful 
simulation primarily because it does not simulate the behaviour of the keyboard 
very well (however, if you just want to see how the layout adapts, it is 
perfectly fine for that). Its possible I have not developed the most efficient 
method of coding the layout. If you have any suggestions, I’d be most grateful 
to receive them.

UI tips:
1. tapping once on white space below the dg entries dismisses the keyboard (so 
does the “down arrow” when it appears in the header bar).
2. tapping twice adds a new blank line (or inserts the cursor into an existing 
one) (so does the “+” sign in the header bar).

The rest should be obvious, I hope. All of the layout is in the card script. 
All of the dg code is in the dg handler and behavior script. 
Finally, if you have any questions, please feel free to send them on.

All the best,
Mark

https://www.dropbox.com/s/nmri0dy5j5qtc8c/test.livecode.zip?dl=0 




> On Dec 27, 2021, at 12:05 PM, Mark Smith  wrote:
> 
> Thank you Sean and Jacque, 
> 
> I’ve not had a chance to work on a complete solution but thought I would make 
> a test run to see what “the effective working screenrect” was returning and 
> as the following indicates, it does in fact take into consideration the 
> keyboard. I just coded up one line to  run whenever the status of the 
> keyboard changed and tried it both with and without the “predictive” option 
> turned on. As you can see, it was very sensitive to this change…
> 
> without predictive:
> 
> 9:37:14 PM keyboardActivated 0,0,375,451
> 9:37:15 PM keyboardDeactivated 0,0,375,667
> 9:37:18 PM keyboardActivated 0,0,375,451
> 9:37:19 PM keyboardDeactivated 0,0,375,667
> 9:37:19 PM keyboardActivated 0,0,375,451
> 9:37:23 PM keyboardDeactivated 0,0,375,667
> 
> 
> with predictive: 
> 
> 9:56:54 PM keyboardActivated 0,0,375,407
> 9:56:55 PM keyboardDeactivated 0,0,375,667
> 9:56:55 PM keyboardActivated 0,0,375,407
> 9:56:57 PM keyboardDeactivated 0,0,375,667
> 
> In my particular case not all 4 value are immediately useful. For example, I 
> have a fixed header and footer that need to be accommodated so the correct 
> “useable” rect for me is:
> 
> 0,69, 377, 618 (for no predictive)
> 0,69,377,456 ( for predictive)
> 
> but this can easily be accommodated since the header/footer values don’t 
> change. The beauty is I now have a rect lower bound (ie. keyboard height) 
> that actually reflects where the keyboard is. 
> 
> Brilliant!! Thank you both,
> 
> Mark
> 
> Sean, I tried iPhoneSafeAreaInsets() but it appears it returns a constant set 
> of values regardless of keyboard position on my iPhone 12
> 
> 11:51:22 AM keyboardActivated 0,47,0,34
> 11:51:22 AM keyboardDeactivated 0,47,0,34
> 11:51:26 AM keyboardActivated 0,47,0,34
> 11:51:26 AM keyboardDeactivated 0,47,0,34
> 
> And didn’t change when I added / subtracted “predictive”. So, just the 
> available usable space at the top and bottom of the screen. I haven’t 
> adjusted my app yet to fully take advantage of the larger screen on a 12 (it 
> was developed on a 6S) but when I get to more response design this will be 
> useful to know where the usable top and bottom are. 
> 
> Cheers!!
> 
> 
> 
> 
> 
> 
> 
>> On Dec 25, 2021, at 5:25 PM, Sean Cole via use-livecode 
>> mailto:use-livecode@lists.runrev.com>> wrote:
>> 
>> Another addendum to this I just noticed is in the latest RC, LC9.6.6RC1,
>> which has iphoneSafeAreaInsets for discerning the safe area from furniture
>> like the notch and so on. I haven't tested this but that may also include
>> things like the keyboard and predictive areas. I just thought it was worth
>> a mention here.
>> 
>> Regards
>> Sean
>> 
>> On Fri, 24 Dec 2021 at 20:44, J. Landman Gay via use-livecode <
>> use-livecode@lists.runrev.com > wrote:
>> 
>>> On 12/24/21 2:16 PM, Sean Cole via use-livecode wrote:
 Just adding to what Jacquie 

RE: full justification in a text field

2022-02-10 Thread Ralph DiMola via use-livecode
I was just trying to make text break at slashes today. I put a zero width 
space(U+200B) after every slash. Although LC did break the lines properly the 
space was not rendered as zero width. It was more like a thin space and a half 
and looked terrible. Is this an engine bug? 

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net


-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of 
Peter Bogdanoff via use-livecode
Sent: Thursday, February 10, 2022 2:50 PM
To: How to use LiveCode
Cc: Peter Bogdanoff
Subject: Re: full justification in a text field

You’re welcome.

What I really wanted to do is to use a narrower space character, such as the 
"thin space, U+2009" which would allow much better alignment of the right 
margin. That character does display in LiveCode.

https://en.wikipedia.org/wiki/Whitespace_character 

But that seems to require modifying the htmlText to insert that character. 
Maybe someone knows how to set/insert the htmlText of a character without 
messing with the html directly.

Peter Bogdanoff

> On Feb 10, 2022, at 1:03 PM, Curt Ford via use-livecode 
>  wrote:
> 
> Peter, that works really well. Looks like it does require a monospaced font 
> (I tried it with Monaco, looks good), so I'm not sure if my current client 
> will want this approach, but it's nice to have a relatively simple native 
> solution. Thanks so much!
> 
> Curt
> --
> Sent from Postbox 
>  campaign=reach> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: full justification in a text field

2022-02-10 Thread Peter Bogdanoff via use-livecode
You’re welcome.

What I really wanted to do is to use a narrower space character, such as the 
"thin space, U+2009" which would allow much better alignment of the right 
margin. That character does display in LiveCode.

https://en.wikipedia.org/wiki/Whitespace_character 

But that seems to require modifying the htmlText to insert that character. 
Maybe someone knows how to set/insert the htmlText of a character without 
messing with the html directly.

Peter Bogdanoff

> On Feb 10, 2022, at 1:03 PM, Curt Ford via use-livecode 
>  wrote:
> 
> Peter, that works really well. Looks like it does require a monospaced font 
> (I tried it with Monaco, looks good), so I'm not sure if my current client 
> will want this approach, but it's nice to have a relatively simple native 
> solution. Thanks so much!
> 
> Curt
> -- 
> Sent from Postbox 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


full justification in a text field

2022-02-10 Thread Curt Ford via use-livecode
Peter, that works really well. Looks like it does require a monospaced 
font (I tried it with Monaco, looks good), so I'm not sure if my current 
client will want this approach, but it's nice to have a relatively 
simple native solution. Thanks so much!


Curt
--
Sent from Postbox 


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Script Compiler - One More Question

2022-02-10 Thread Curry Kenworthy via use-livecode



Me:

> How do you plan to avoid a repeat of the LC 7 bug onslaught?

Heather:

> Curry - please email support and we will be happy to help with this.

Thanks! But I don't see this as a private 1-on-1 support issue;
if it's not a general/public approach, not sure it could help.
So for my purposes, I believe that answers the question.
(I'll save us both the time and skip the support ticket.)

Back to work

Best wishes,

Curry Kenworthy

Custom Software Development
"Better Methods, Better Results"
Innovative Christian LiveCode Training and Consulting
http://livecodeconsulting.com/

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Script Compiler - One More Question

2022-02-10 Thread Heather Laine via use-livecode
Curry - please email support and we will be happy to help with this.

Best Regards,

Heather

Heather Laine
Customer Services Manager
LiveCode Ltd
www.livecode.com



> On 10 Feb 2022, at 16:31, Curry Kenworthy via use-livecode 
>  wrote:
> 
> 
> Script Compiler - One More Question:
> 
> After the survey there was an email "Your Questions Answered."
> I put a concern in the survey, just without a question mark!
> 
> (And I don't recall any survey directions specifying
> that concerns/comments should be worded as questions.)
> 
> It's easy to add a question mark:
> 
> Deja vu of LC 7. Big new changes + new engineers = LOTS OF BUGS! After all 
> these years, we are just recently starting to turn the tide on LC 6-9 bugs. 
> How do you plan to avoid a repeat of the LC 7 bug onslaught?*
> 
> Knowing that would help me decide my level of interest/support.
> Good project if such problems can be avoided; and vice versa.
> 
> * The proposed changes also deeply involve the non-compiled engine;
> to clarify, I'm primarily concerned about the non-compiled product.
> (All the more so, since it's impacted whether we use compiler or not!)
> 
> Thanks!
> 
> Best wishes,
> 
> Curry Kenworthy
> 
> Custom Software Development
> "Better Methods, Better Results"
> Innovative Christian LiveCode Training and Consulting
> http://livecodeconsulting.com/
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Script Compiler - One More Question

2022-02-10 Thread matthias rebbe via use-livecode
Isn't that a question you should ask the people of Livecode Ltd. directly?

> Am 10.02.2022 um 17:31 schrieb Curry Kenworthy via use-livecode 
> :
> 
> 
> Script Compiler - One More Question:
> 
> After the survey there was an email "Your Questions Answered."
> I put a concern in the survey, just without a question mark!
> 
> (And I don't recall any survey directions specifying
> that concerns/comments should be worded as questions.)
> 
> It's easy to add a question mark:
> 
> Deja vu of LC 7. Big new changes + new engineers = LOTS OF BUGS! After all 
> these years, we are just recently starting to turn the tide on LC 6-9 bugs. 
> How do you plan to avoid a repeat of the LC 7 bug onslaught?*
> 
> Knowing that would help me decide my level of interest/support.
> Good project if such problems can be avoided; and vice versa.
> 
> * The proposed changes also deeply involve the non-compiled engine;
> to clarify, I'm primarily concerned about the non-compiled product.
> (All the more so, since it's impacted whether we use compiler or not!)
> 
> Thanks!
> 
> Best wishes,
> 
> Curry Kenworthy
> 
> Custom Software Development
> "Better Methods, Better Results"
> Innovative Christian LiveCode Training and Consulting
> http://livecodeconsulting.com/
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Script Compiler - One More Question

2022-02-10 Thread Curry Kenworthy via use-livecode



Script Compiler - One More Question:

After the survey there was an email "Your Questions Answered."
I put a concern in the survey, just without a question mark!

(And I don't recall any survey directions specifying
that concerns/comments should be worded as questions.)

It's easy to add a question mark:

Deja vu of LC 7. Big new changes + new engineers = LOTS OF BUGS! After 
all these years, we are just recently starting to turn the tide on LC 
6-9 bugs. How do you plan to avoid a repeat of the LC 7 bug onslaught?*


Knowing that would help me decide my level of interest/support.
Good project if such problems can be avoided; and vice versa.

* The proposed changes also deeply involve the non-compiled engine;
to clarify, I'm primarily concerned about the non-compiled product.
(All the more so, since it's impacted whether we use compiler or not!)

Thanks!

Best wishes,

Curry Kenworthy

Custom Software Development
"Better Methods, Better Results"
Innovative Christian LiveCode Training and Consulting
http://livecodeconsulting.com/

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Notarize Helper Stack in LC lesson updated

2022-02-10 Thread matthias rebbe via use-livecode
Hi Camm,

Could it be that both standalones have the same Bundle Identifier 
(NSBundleIdentifier). You can find the value in LC's standalone settings ->Mac 
at the bottom.
Seems that not the Bundle Name but the Bundle Identifier is responsible for 
that relocation behaviour.

More information could be found here
https://scriptingosx.com/2017/05/relocatable-package-installers-and-quickpkg-update/

Regards,
Matthias



> Am 09.02.2022 um 23:35 schrieb General 2018 via use-livecode 
> :
> 
> One more slight issue …
> 
> I have 2 apps with standalone CFBundleNames :-
> 
> Myapp 1.0.0 Free
> 
> Myapp 2.0.0
> 
> Though they have different CFBundleNames they will not install on the same 
> machine.
> Delete either and one installs fine to Applications.
> 
> Any CF settings conflict or still issue with above names ?
> 
> Regards Camm
> 
>> On 9 Feb 2022, at 21:56, General 2018 via use-livecode 
>>  wrote:
>> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: full justification in a text field

2022-02-10 Thread Peter Bogdanoff via use-livecode
I’ve taken a quick stab at this ...

This script adds spaces between words of a line to get it close to the full 
width of the field to create a quick & dirty faux fully-justified field.
In operation, It converts each visible line of text to a LiveCode line 
(delineated by CRs) so the final text has a CR after each visible line. Then it 
uses the formattedWidth property of each line to determine its current width, 
then adds spaces between words to fill out the full width of the line. 

Note that the final width of the text is determined by tMaxWidth, which is 
based on the widest visible line of the field. But that could be changed to use 
the width property of the field itself, minus any V scrollbars.

Peter Bogdanoff


on mouseUp
   set lockscreen to true
   # Add CRs to the end of each line 
   put the formattedText of field "Text2" into field "Text2"
   
   # Find longest line of text. This will determine the overall width of the 
text.
   # This probably should be modified to simply get the width property of the 
field itself.
   put 0 into tMaxWidth
   repeat with x = 1 to the number of lines of field "Text2"
  put the formattedWidth of line x of field"Text2" into tWidth
  if tWidth > tMaxWidth then put tWidth into tMaxWidth
   end repeat
   
   # Format each line
   put tMaxWidth - 5 into tMaxWidth # This number can be adjusted for best 
results

   repeat with x = 1 to (the number of lines of field "Text2" - 1) # Don't 
format last line
  put 100 into maxRepeats # Max number of spaces that can be added to a line
  if line x of field "Text2" is empty then next repeat  
  if the formattedWidth of line x of field"Text2" >= tMaxWidth then next 
repeat
  
  put the number of words of line x of field "Text2" into tWordNum
  if char -1 of word tWordNum of line x of field "Text2" is "." then next 
repeat # Last word of a paragraph
  repeat with z = 1 to maxRepeats
 repeat with y = 1 to (tWordNum - 1) # Don't add spaces after the last 
word of a line
put space after word y of line x of field "Text2"
if the formattedWidth of line x of field "Text2" >= tMaxWidth then 
exit repeat
 end repeat
 if the formattedWidth of line x of field"Text2" >= tMaxWidth then put 
maxRepeats into z
  end repeat
   end repeat
end mouseUp


> On Feb 9, 2022, at 10:28 PM, Tom Glod via use-livecode 
>  wrote:
> 
> Hello Curt,
> 
> The only thing you can do is adjust the font size to maximize the use of
> the width of the field.with the don't wrap enabled. :)
> Remember the margins can be adjusted individually. like so 0,5,5,0
> Also, there is a problem with the margins when the font gets too small. in
> those cases, it helps to have "showborder" enabled, even if the borderwidth
> is set to 0.
> 
> All the best,
> 
> Tom
> 
> Founder & Developer @ MakeShyft R.D.A 
> Build Software with AppStarterStack  for
> Livecode
> Save Time with The Time Saver's Toolbox 
> 
> On Wed, Feb 9, 2022 at 5:50 PM Paul Dupuis via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> 
>> On 2/9/2022 5:24 PM, Curt Ford via use-livecode wrote:
>>> This seems like an awfully basic question, but is it possible to have
>>> text with full justification in a field?
>>> 
>>> I've looked at using WordLib, but this client's text has lots of fussy
>>> formatting (background colors, different colors for individual
>>> characters) that didn't come through well.
>>> 
>>> Thanks for any ideas,
>>> 
>>> Curt
>> 
>> See the Dictionary entry for textAlign:
>> 
>> set the textAlign [of line] of {button | field} to {left | center | right}
>> 
>> There is no justified option. There is a REALLY old enhancement request
>> at https://quality.livecode.com/show_bug.cgi?id=4714
>> 
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode