Thanks Alex.
The text could be Unicode or ASCII, depending on the source, so I’m assuming
the former to be on the safe side.
I did think of checking the character number but whilst the ASCII range is
neat, identification of Unicode capital letter codes seem to be complex.
Perhaps I’ll start wi
Thanks Geoff, I did play with Split, but one of the reasons for numbering is to
make any identical lines unique. With split, for any that are not, all but one
is deleted. So definitely not the result I wanted.
I’ll sacrifice the progress bar and see where that leaves me.
Thanks folks.
> On 2
> David G. wrote:
> Thanks Geoff, I did play with Split, but one of the reasons for numbering
> is to make any identical lines unique. With split, for any that are not,
> all but one is deleted. So definitely not the result I wanted.
I am not Geoff (who played with the simple array methods I sug
Thanks to both Brian and Jacqueline
Of course, no one's code is perfect and errors do occur, particularly in the
early going. Interesting that this "fix/issue" deals with an error occurring
*in* the standalone as the standalone is being built.
Anyway, if there is an error which the standalone
Has anyone else tried the native Android button and field widgets? When I
use the field widget, text entered into the field isn't displayed. I
figured out it was placed below the bottom edge, out of view. There isn't a
way to adjust the textheight so I can't make it visible. This is a single
li
We already know that this is not possible by "ordinary" controls
because the browser widget has a native layer.
(Except we"bundle" your controls in a floating window.)
But there is one way more (I use it for updating my Textedit
widget).
Of course you can overlay a browser widget with a browser w
Thanks for this, although I’m not sure I understand. In fact I am sure I
don’t.I know how amazingly fast the array method is, I use it elsewhere in
the same stack, and it is great.
I also don’t understand the distinction between line numbering and indexing.
If I was guessing, I would go
Nope, i'm still not using them
Op 28-10-2018 om 18:04 schreef J. Landman Gay via use-livecode:
Has anyone else tried the native Android button and field widgets?
When I use the field widget, text entered into the field isn't
displayed. I figured out it was placed below the bottom edge, out of
well that answer of me was a bit short.
But i like the answer/ask.
And i'm using a normal field but on top of that i placed an equal size
transparent graphic.
The mouseup goes thru transparent parts which in this case was convenient.
I don't know exactly anymore why i did it, but it prevente
Typically you need to handle field placement yourself in script, moving
the controls up on keyboardActivated and back down on
keyboardDeactivated. However, there's an unintentional side-effect when
setting acceleratedRendering to true in a stack; when the keyboard shows
up, the whole card scrol
David,
I think you are correct - there is no magic version of split or array
that will do what you want.
You require to keep the line ordering completely unchanged - and
Hermann's superfast method can't meet that need.
The best solution (AFAIK) will be the one Mark Hsu and/or Jacqueline
al
You're right, split deletes duplicates. In fact, I use it as a quick way
to do just that.
I don't see any way to add line numbers without looking at each line.
But you could keep a counter in a variable and put the text into an
array with the counter integer as the key. That might be faster th
That's for the answer, regardless of length. ;)
The scripted native field still works so I can use that. There is no
replacement for the native button though.
On 10/28/18 2:04 PM, JJS via use-livecode wrote:
well that answer of me was a bit short.
But i like the answer/ask.
And i'm using a
>> David G. wrote:
>> Thanks Geoff, I did play with Split, but one of the reasons for numbering
>> is to make any identical lines unique. With split, for any that are not,
>> all but one is deleted. So definitely not the result I wanted.
From that previous answer I concluded you intend to index
> Alex T. wrote:
> You require to keep the line ordering completely unchanged -
> and Hermann's superfast method can't meet that need.
> JLG wrote:
> You're right, split deletes duplicates. In fact, I use it as a quick way
> to do just that.
You are both spendidly wrong:
Could you please simply
What's interesting with that is once again a comparison LC 6 against LC 9.
I tested with 1 lines of text (King James bible, Genesis up to 5|16) and
*non-wrapping fields*, separator tab:
LC 9.0.1 needs in average 370 ms for numbering, 330 ms for denumbering,
LC 6.7.11 needs in average 170 ms
Hi.
Today i was informed by a customer that my app BRx Converter is not able to
write data to the preference folder ~/library/preferences.
The app normally writes some registration info after successful registration to
that folder. After that the app is switched from demo to full mode.
But unde
My apologies Hermann. I had not been following the original thread
closely, and got confused by the embedded quoting in the later messages.
I was looking at Geoff's code - not yours - and he explicitly said "
And of course if retaining the order isn't critical "
So I agree your array method d
On Sun, Oct 28, 2018 at 5:27 PM Alex Tweedly via use-livecode <
use-livecode@lists.runrev.com> wrote:
> My apologies Hermann. I had not been following the original thread
> closely, and got confused by the embedded quoting in the later messages.
> I was looking at Geoff's code - not yours - and he
(That said, yeah, repeat for each line is going to be faster)
On Sun, Oct 28, 2018 at 5:37 PM Geoff Canyon wrote:
>
>
> On Sun, Oct 28, 2018 at 5:27 PM Alex Tweedly via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> My apologies Hermann. I had not been following the original thread
Hermann:
You are sooo DARN CREATIVE! I’m awed.
Bill
> On Oct 28, 2018, at 10:54 AM, hh via use-livecode
> wrote:
>
> We already know that this is not possible by "ordinary" controls
> because the browser widget has a native layer.
> (Except we"bundle" your controls in a floating window.)
>
> B
On 10/27/18 11:40 AM, Mike for GDC via use-livecode wrote:
> I am new to LC and have learned much so far but I am having an issue with
> the proper scaling of my app on different size screens. I have created the
> app with the dimensions of 913 w X 636 h. All looks great on the desktop.
I've spe
excellent demo thank you..just out of curiosityis it just on
my system ? or the right click grab of the widget doesn'twork?
On Sun, Oct 28, 2018 at 8:51 PM, William Prothero via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Hermann:
> You are sooo DARN CREATIVE! I’m awed.
>
Alex,
you and JLG are important LiveCoders. What you say has double weight.
>From that alone you should double check what you claim to be true.
Wrong assertions are no argument against a method but speed is one,
of course.
Anyway, it is fine that David G. has now a fast way to do his work.
_
> Tom G. wrote:
> ...just out of curiosityis it just on my system ? or the right click
> grab of the widget doesn't work?
Sorry, I wrote this while updating my TextEdit widget (which will allow to
grab the widget). But the browser widget doesn't pass "mouseDown", so the
mouseDown handler here
On 10/28/18 9:15 PM, hh via use-livecode wrote:
Alex,
you and JLG are important LiveCoders. What you say has double weight.
From that alone you should double check what you claim to be true.
Well, at least I have finally become "splendid" at something.
I can't decide whether you are being rud
26 matches
Mail list logo
