On 01/01/2018 07:48 PM, Sannyasin Brahmanathaswami via use-livecode wrote:
Mark recommends using "go in window" on Mobile,
saying this closes stack A while going to open stack B
This works on desktop
put ("stack " & quote & gems & quote) into tDestination
go tDestination # but stack A remains
Mark recommends using "go in window" on Mobile,
saying this closes stack A while going to open stack B
This works on desktop
put ("stack " & quote & gems & quote) into tDestination
go tDestination # but stack A remains open.
but this fails in a backscript
put ("stack " & quote & gems & quote)
Yes, I am actually adjusting the field width individually for each “page.” But
it doesn’t solve the problem of occasional “widows” at the bottom. Thus the
thought about other formatting work arounds.
Thanks, Jacque.
> On Jan 1, 2018, at 3:39 PM, J. Landman Gay via use-livecode
> wrote:
>
>
I wonder if you could figure out a general ratio for the size difference
and adjust the width of the field to correct the text wrap on Windows.
That's about all I can think of.
On 1/1/18 5:04 PM, Peter Bogdanoff via use-livecode wrote:
I think that the size difference is related to the specifi
On 12/31/17 7:31 PM, Nicolas Cueto via use-livecode wrote:
To do "some calculations", I thought of comparing the loc to the
scalefactor. So ran the standalone on three devices, but saw no consistent
corelation between the differing locs and the scalefactor.
So, still no clue what to use for thes
I think that the size difference is related to the specific font used. Georgia
is displaying slightly wider in Windows than Mac. Helvetica seems pretty
consistent. A Chinese font I use is much smaller in Windows.
Changing Georgia from 16 to 15 is too drastic a change for me, so I need to
keep t
On 1/1/18 2:39 AM, Peter Bogdanoff via use-livecode wrote:
My page layout is fixed — no user settings of font face or size. Also the card
height doesn’t have room for text fields to get taller. And there was the
design decision not to show scroll bars.
Text also often has “widows” at the botto
For removing a single property while leaving the rest intact, I have a
library routine rmProp.
on rmProp prop, tgt
--remove a property from the basic property set
local props
if tgt is empty then
put the long id of me nto tgt
end if
put the customProperties of tgt into props
repeat for each
On Sun, Dec 31, 2017 at 5:31 PM, Nicolas Cueto via use-livecode <
use-livecode@lists.runrev.com> wrote:
>
> To do "some calculations", I thought of comparing the loc to the
> scalefactor. So ran the standalone on three devices, but saw no consistent
> corelation between the differing locs and the
On Mon, Jan 1, 2018 at 8:03 AM, Graham Samuel via use-livecode <
use-livecode@lists.runrev.com> wrote:
>The thing is, this used to work, probably in the LC 7 series.
I think that is the error here--it shouldn't be possible to delete the
stack containing a target while that target's script is runni
Try using a send in time to do the deletion? Also, with the settings you
currently have, closing the stack SHOULD remove it from memory once any
running scripts are complete.
On Mon, Jan 1, 2018 at 9:03 AM, Graham Samuel via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Happy New Year t
Happy New Year to all!
I have a bit of script that says
delete stack “myStack”
This runs in a mainstack (not the one I’m trying to delete, “myStack”, which
I’ll call the target), but the path by which this script was invoked was
started in a menu item in the target. I get error 377 “stack loc
My page layout is fixed — no user settings of font face or size. Also the card
height doesn’t have room for text fields to get taller. And there was the
design decision not to show scroll bars.
Text also often has “widows” at the bottom of the field when the text was
formatted for Mac but is di
13 matches
Mail list logo