On 2017-08-11 18:49, Curry Kenworthy via use-livecode wrote:
Richmond, this may be rare but I'm 100% in agreement with you! My
device, my management. I don't have the right to do something illegal
or endanger others, but otherwise, I call the shots.
Indeed - you are free to do whatever you
On 2017-08-11 18:54, Richmond Mathewson via use-livecode wrote:
Now putting a LiveCode standalone onto an iPad that does thing that
Apple doesn't like isn't always the same thing as putting things onto
an iPad that is unsafe.
I've already pointed out that you can put whatever you want onto
On 2017-08-11 18:00, Mike Kerner via use-livecode wrote:
That's not what I'm saying. What I'm saying is while telling everyone
to
control themselves is good, removing these capabilities from LC is bad,
so
if the time comes where it is necessary to do something to stop someone
from behaving
On 2017-08-11 17:40, Mark Wieder via use-livecode wrote:
On 08/11/2017 02:51 AM, Mark Waddingham via use-livecode wrote:
Naming loops in a syntactic way certainly sounds like a useful thing
to do:
I should point out here that Robert Cailliau has complained about the
lack of named loops
On 2017-08-11 16:44, Richmond Mathewson via use-livecode wrote:
I cannot quite see how people are prepared to go on buying Apple iPads
when
there are such draconian restrictions as to what one can run on them.
While the Android "thing" may not be much better, at last one can
side-load almost
On 2017-08-11 17:26, Mark Wieder via use-livecode wrote:
On 08/11/2017 02:24 AM, Mark Waddingham via use-livecode wrote:
Not quite on topic for the thread, but this interested in me in terms
of - what are the use cases?
Somewhat similar to Ralph's use cases, this paradigm comes up quite
On 2017-08-11 16:35, Mike Kerner via use-livecode wrote:
Unless I read your post incorrectly, mark, "Do" works just fine, at
least
Yes it does - the point I was making was that breaking the rules in the
App Store could end up with us having to restrict what the LiveCode
engine can do when
On 2017-08-11 14:57, Mark Waddingham via use-livecode wrote:
The question of course is 'how fast could we get long id parsing to
be' (as that is the bottleneck here, or at least appears to be).
Okay so I got stuck on what I am *meant* to be doing, so spent a little
time trying to answer
On 2017-08-11 14:56, Lagi Pittas via use-livecode wrote:
I thought you didn't agree with USING next repeat as a structured way
of
programming - Reading and understanding before my Brain was in gear.
Sorry - I should have made that more clear - 'next repeat' and 'exit
repeat' are definitely
On 2017-08-11 11:12, Mark Waddingham via use-livecode wrote:
On 2017-08-10 21:10, Richard Gaskin via use-livecode wrote:
How might I measure the benefits of long ID caching?
Here is perhaps a better set of simple benchmarks to compare approaches
to lookup (related to ids, anyway
On 2017-08-11 12:20, Jonathan Lynch via use-livecode wrote:
I know the reviewers at app stores are not always careful, but
something like an LC player would surely get their notice.
Review, from my understanding, is heavily automated (it has to be - if
you think of the scale of the App Stores
On 2017-08-11 12:51, Lagi Pittas via use-livecode wrote:
Hi Mark,
I Beg to Differ about Next Repeat.
"It's not wat you do it's the way that you do it" comes to mind
Someone who writes spaghetti code can do it very well in any language
but
its much more difficult without the structure
On 2017-08-11 12:43, Richmond Mathewson via use-livecode wrote:
I am in trouble because I cannot work out why this is not working:
on scrollbarDrag NVAL
put "NVAL,0,0" into KARRAY["color"]
put 50 into KARRAY["opacity"]
set the coloroverlay of img "BB" to KARRAY
end scrollbarDrag
Try:
On 2017-08-10 21:33, Dr. Hawkins via use-livecode wrote:
In fact, what I would *like* is modern Fortran style labelling or
something
like that, and the ability to the those labels to controls like next
and
exit. This, however, would accomplish so much with so little.
Thinking out loud here
On 2017-08-10 03:38, Jonathan Lynch via use-livecode wrote:
Actually, I had forgotten to set the layermode of the group.
Now the number of passes on my Mac is 47 and on the android it is 31.
This still seems rather close. I expected the slow android device to
be like a quarter as fast.
How
On 2017-08-10 19:38, Ralph DiMola via use-livecode wrote:
To make this even more flexible:
repeat for each line tLine in tLines with [counter] tIndex [start]
[{1}|x]
[step] [{1}|y]
end repeat
Not quite on topic for the thread, but this interested in me in terms of
- what are the use
On 2017-08-11 10:41, Richmond Mathewson via use-livecode wrote:
It may not, but the stack does export images with a .lcjpng suffix . .
. and the question is what for?
Perhaps so it can be loaded again by code which knows how to decompress
them as images in LiveCode? After all you have to
On 2017-08-10 21:10, Richard Gaskin via use-livecode wrote:
How might I measure the benefits of long ID caching?
It isn't long ids which are cached - it is ids.
I made a few adjustments, tweaked a few things to remove some overheads
which aren't relevant here:
private function MarkObjRef1
On 2017-08-11 09:29, Richmond Mathewson via use-livecode wrote:
In theory that sounds both impressive and useful . . .
But, what, apart from your stack can read the format/compression
method properly.
I think Hermann's suggestion is a bespoke way of reducing resource size
for built apps and
Okay so the thread from which this post came has some glaringly large
and obvious incorrect statements in it so I think it wise I correct
them.
First of all being able to submit apps to the App Stores which exist
today is critically important to our ecosystem - those App Stores come
with
t; Bob S
>
>
>> On Aug 10, 2017, at 10:32 , Mark Waddingham via use-livecode
>> <use-livecode@lists.runrev.com> wrote:
>>
>> The reason you get that error is because at present the popup button command
>> requires there to be a mouseStack. So if you cmd-
On 2017-08-09 20:48, Trevor DeVore via use-livecode wrote:
I think this bug report has a recipe for the issue you are seeing:
http://quality.livecode.com/show_bug.cgi?id=18030
This has been around for a long time. I don’t know of a workaround
other
than fully qualifying all object
On 2017-08-09 05:39, Sannyasin Brahmanathaswami via use-livecode wrote:
The more we separate our code/libraries/behaviors from the binary UI,
the more I find myself trying to dispatch call backs or other messages
back to the group/card/stack that has a behavior and not the
individual control:
On 2017-08-10 09:32, Ali Lloyd via use-livecode wrote:
Jacque recently showed me the speed difference between explicitly
writing out the element of an object reference:
get the width of btn 1 of cd 2 of stack "MyStack"
...vs other forms like long IDs:
put the long is of btn 1 of cd 2
On 2017-08-10 01:47, Monte Goulding via use-livecode wrote:
Thinking about this some more I wonder if a stringified representation
and string representation type could be paired with the object
reference so that if you got say the abbreviated id then that would be
the stringified representation
On 2017-08-09 18:50, Richard Gaskin via use-livecode wrote:
Imagine the frustration of passing an invalid object reference to
something like the delete command, and rather than reporting that it
couldn't do what it asked you it just arbitrarily deleted some other
object instead without
On 2017-08-09 19:15, Bob Sneidar via use-livecode wrote:
OIC. I was under the impression that the C math libraries deal with
numbers of high precision better than Livecode does, perhaps
themselves generating errors on overflow. Maybe that is not the case.
C itself does no error checking/bounds
On 2017-08-09 19:11, Mark Wieder via use-livecode wrote:
The problem I've run into is more at a higher level, dealing with
number parsing and runtime overflow detection before truncating input
parameters down to unsigned integers and calling the math library.
Well there's two things here...
On 2017-08-09 18:56, Bob Sneidar via use-livecode wrote:
Btw, I should mention that the way numbers work in LiveCode has become
one of my biggest 'pet peeves' over the last year or so. The current
way things work is too simplistic really - it hides the very important
distinction between
On 2017-08-09 18:29, Mark Wieder via use-livecode wrote:
Looking into the engine code, by the time you get to the actual bitXor
code, the input arguments are already unsigned integers. Since I was
passing 20-hex-digit values to bitXor, I would have expected some kind
of runtime warning or error
On 2017-08-09 18:29, Mark Wieder via use-livecode wrote:
Looking into the engine code, by the time you get to the actual bitXor
code, the input arguments are already unsigned integers. Since I was
passing 20-hex-digit values to bitXor, I would have expected some kind
of runtime warning or error
On 2017-08-09 18:14, Mark Wieder via use-livecode wrote:
Oops. OK - point sheepishly taken. Is that the definition of integer
in the dictionary? The "integer" entry just says "if the value
contains digits (and an optional minus sign) and no other characters,
it is an integer", which is as
On 2017-08-09 11:36, hh via use-livecode wrote:
Mark wrote:
but I'm annoyed that the IDE doesn't give me an overflow warning if I
try
to perform an operation on a number that's bigger than 0x.
Instead, it just happily trims it down to an unsigned integer and
proceeds
to give me a
On 2017-08-08 17:59, Mark Wieder via use-livecode wrote:
On 08/08/2017 08:49 AM, hh via use-livecode wrote:
JLG wrote:
In what circumstance would it be necessary to quote the property
name?
Use "&" in a key, for example the "G" of me
Is there any use case where punctuation in a property
On 2017-08-08 17:49, hh via use-livecode wrote:
From a viewpoint of the "get property /set property" syntax
"unexpected results" sounds convincing here, but, TMHO, it is
exactly what I would expect from a **viewpoint of array syntax**.
on mouseUp
local catness
put "minimal" into catness
On 2017-08-08 17:46, Bob Sneidar via use-livecode wrote:
famous last words. :-)
Indeed - perhaps a slight case of over-optimism on my part...
:'(
Mark.
--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps
On 2017-08-08 17:41, Richmond Mathewson via use-livecode wrote:
I can send a command to a button like this:
send "mouseUp" to btn "BASH"
BUT I want to fake having the altKey pressed as well:
pseudocode
send "mouseUp" with altkey(down) to btn "BASH"
can it be done?
Yes.
and if so, how?
On 2017-08-08 17:33, Mark Waddingham via use-livecode wrote:
(Of course, I'm now going to go off and see if you can use quoted
variables in other places - I bet that's going to a 50/50 chance in
every
place!)
Okay - so:
the of ...
Is the *only* place where a check to make sure something
andman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On August 8, 2017 10:17:29 AM Mark Waddingham via use-livecode
<use-livecode@lists.runrev.com> wrote:
On 2017-08-08 17:09, J. Landman Gay via use-livecode wrote:
In what ci
en defined.
I think the latter is probably something which is unlikely to hurt
anyone if
tweaked though...
Warmest Regards,
Mark.
On August 8, 2017 6:05:21 AM Mark Waddingham via use-livecode
<use-livecode@lists.runrev.com> wrote:
What doesn't work at the moment is if you have
On 2017-08-08 12:43, hh via use-livecode wrote:
Two examples for testing ambiguity.
[a]
set "8.1" of me to "I dreamt to be quoted"
set 8.1 of me to "I dreamt to be 8.2"
put the customProperties of me into cp
put cp["8.1"] &" : "& cp[8.1] &" : "& cp[8+1/10]
Test and then interchange the
On 2017-08-03 05:39, Monte Goulding via use-livecode wrote:
Er… why if you know the name wouldn’t you type it unquoted? Are you
really suggesting to put any expression there? The property/function
ambiguity with `the` will make our heads explode!
For the reason Dr Hawkins originally asked
Also using the query functions which allow iteration over the result set will
minimise data transfer at any one point in time (assuming it's a decent client
driver).
Warmest Regards,
Mark.
Sent from my iPhone
> On 7 Aug 2017, at 19:45, Bob Sneidar via use-livecode
>
far as I know anyways. unless thats completely wrong.
>
> Here is the link again...
>
> https://www.rethinkdb.com/docs/writing-drivers/
>
> Thanks for making me aware of the past efforts with RethinkDB.
>
> On Sat, Aug 5, 2017 at 4:36 PM, Mark Waddingham via use-livecode &l
The best way is to ask 'us' (as in the engineers that have worked on the
entirety of the LiveCode source base for many years). This isn't any different
from any other open source project which has 1.5m lines of code (I don't think
at least...).
We can certainly provide an insight at where to
Err - given that revDB is an *SQL* database wrapper and MongoDB is not an SQL
database you can imagine that creating an abstraction layer to deal with both
might be 'quite' hard - if not impossible.
So, given that we've now been open source for over four years and as such that
code has been
Erdős is considered one of the most prolific mathematicians of the 20th century.
His most famous quote is 'a mathematician is a machine for turning coffee into
theorems'.
He drank a lot of coffee.
He also took a lot of amphetamines.
Warmest Regards,
Mark.
Sent from my iPhone
> On 3 Aug
I'm not sure the learning of C and its relatively difficulty was the point here.
Find me a book on C which teaches you how to create a window, show a button and
have that button pop up a modal dialog which says 'hello world' on Android,
HTML5, iOS, Linux, Mac and Windows then *that* would be
Sorry - release the source-code of things you write in LiveCode you distribute
to others.
Warmest Regards,
Mark.
Sent from my iPhone
> On 3 Aug 2017, at 00:21, Mark Waddingham via use-livecode
> <use-livecode@lists.runrev.com> wrote:
>
> Just to pay reference to the comm
Just to pay reference to the comment about LiveCode - I missed it the first
time around...
We (LiveCode Ltd.) did not 'give away' LiveCode. We released it under a
software license that has strings.
The GPL requires (subject to interpretation by lawyers - and a court of law)
you to also
File an enhancement - it's not something we have gotten round to doing yet but
a 'flattened path' api was always on the cards to do but we hadn't gotten
around to it yet.
Warmest Regards,
Mark.
P.S. 'Flattening' is the term used to describe the process of turning paths
into sequences of line
On the Monday he turned up with a big box of chocolates for me and an apology.
>
> I will be forever grateful to the Livecode team that they have saved me from
> having to learn C++.
>
> Richmond.
>
>> On 8/2/17 9:07 pm, Mark Waddingham via use-livecode wrote:
>> I
Indeed - and (if I remember correctly) - one purpose of devils advocate is to
ensure the other side justifies its case 'sufficiently' (for some definition of
sufficiently - usually a great deal harder when pedanticism kicks in!).
I'm off to have another G!
Warmest Regards,
Mark.
Sent from my
You can put the name of the property into a local var and use that (unless I
misunderstood the problem).
Ali's suggestion is however the very pragmatic one - there are always going to
be cases where var names might conflict with other things 'in context' and
require disambiguation. (Although
Richard just said what I was thinking but much much better!
Warmest Regards,
Mark.
Sent from my iPhone
> On 2 Aug 2017, at 23:03, Richard Gaskin via use-livecode
> wrote:
>
> Richmond Mathewson wrote:
>
> > No, I don't think we have to respect Apple's policy
to me of interest.
>
> All the best,
> Erik
>
>
>
>
> -Original Message-
> From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
> Of Mark Waddingham via use-livecode
> Sent: Wednesday, August 2, 2017 10:34 PM
> To: How to use
Heh - sometimes it takes a relative tome of justification to arrive at a simple
explanation!
However the beauty of Bézier curves is that arcs are just a small subset of
what they can represent 'well enough'.
For moving along an arbitrary (Bézier - you can represent a straight line
segment as
Whilst that may be true - a significant part of LiveCode's business comes from
the US... As does our support for Apple devices.
Of course, Apple probably don't care (why would they? Hackintoshes are not
Macs). However, Apple did think it reasonable to outlaw anything other than
Obj-C and JS
If you evaluate the second expression in that merge in the context (i.e. Same
handler) of the call to merge does it throw an error?
If a compile or runtime error occurs in any [[ ... ]] bracketed part of the
merge string, then it gets rendered literally and not the value of it (as it
can't be
Heh - I'll say one thing for kilts... in the blistering heat of Arizona (I
think it peaked at 42 Celsius) - it was a lot more comfortable outside than
shorts or trousers! (The black long sleeved shirt less so - but life's not
perfect!)
Warmest Regards,
Mark.
Sent from my iPhone
> On 2 Aug
A general arc (which an oval is an example of) is represented in LiveCode like
elsewhere as a maximum of four cubic Bézier curves.
These Bézier curves are then flattened to polynomials relative to a notion of
'flatness' - which means that the you iterate (using the de Casteljeu method)
until
Bézier curves are a polynomial - usually quadratic (2nd degree) or cubic (3rd
degree) but the model extends to arbitrary order.
With four cubic Bézier curves (so 8 quadratic) you can make an exceptionally
good approximation to an oval - but it is not exact.
Indeed (anyone who might have a
Indeed - freedom of speech and all.
However, I have to side with Richard here - this forum is about LiveCode and
not anything else. Sure we have 'OT' discussions now and again but generally
they either 'peter out' or are suggested that this is not the appropriate forum
(the latter in this
Hah! I missed the IDE bit - 99.99% of the IDE is written in LCS (some widgets
in LCB).
Pretty much the only bits which aren't are done script introspection features
(e.g. revAvailableHandlers), the core standalone building part (which fettles
with executables on each platform) and the
Increasingly less - and in contrast the amount that could be done in LC instead
of C++ continues to increase (far more slowly than I'd like - but hey, if
wishes were horses...)
Indeed, a lot of the 'heavy lifting' seen in the engine comes down to either
the core abstractions which the LiveCode
> On 31 Jul 2017, at 16:39, Mark Wieder via use-livecode
> <use-livecode@lists.runrev.com> wrote:
>
>> On 07/29/2017 09:23 PM, Mark Waddingham via use-livecode wrote:
>>
>> P.S. One other possibility I've toyed with is doing LCS->BYTECODE, then
>> BYTECOD
I don't think there is anyway we can deny that the transition from 6.x to 7.x
caused a lot of regressions.
This is why we have a strict policy of handling maintenance releases now - i.e.
we work very hard to ensure each maintenance version is strictly better than
before.
I know of a number of
Hi Herman,
This is all very useful information I must confess.
I guess I'm wary of just extrapolating potential performance from piecing
together results from very different underlying architecture (e.g emterpreter
vs no emterpreter) over bastions different html5 engine iterations.
Of course
Indeed our split isn't perfect - so there's a list of things we can and cannot
do - depending on which engine version is needed to support the changes - this
forces a good process (because it forces thought on it).
The submodule link is a version dependence - it's just hard to think of it like
On 2017-07-30 11:13, hh via use-livecode wrote:
Wow. You say (using stars) it would make sense to implement wait
in HTML5 for some features that do _not_ (yet) work in HTML5.
Will be a great enhancement side-effect. I look forward to that.
I don't think that was the implication. The
matthiasrebbe.eu <http://matthiasrebbe.eu/>
>
>> Am 30.07.2017 um 10:20 schrieb Mark Waddingham via use-livecode
>> <use-livecode@lists.runrev.com <mailto:use-livecode@lists.runrev.com>>:
>>
>> The solution here is to use revBrowserOpen.
>>
; report for the browser external.
>
> Or is it more realistic that if i report it as a bug that the browser
> external is fixed earlier than bug 20200?
>
>
> Matthias Rebbe
> +49 5741 31
> matthiasrebbe.eu <http://matthiasrebbe.eu/>
>
>> Am 30.07.
On 2017-07-30 01:04, Monte Goulding via use-livecode wrote:
I’m actually not sure I see the connection between the ide submodule
and the 8.1.6-rc-2.
Heh - the connection is indirect, however it is definitely there!
**The goal:
We want to do A/B testing on LiveCode's 'first run' experience.
So LiveCode has long has this feature called 'wait' - it is one of those
seemingly innocuous things which, from the surface seems simple (it
allows you to wait for something - it's great when syntax is aptly
named!) however it is perhaps one of the deepest language features we
have.
I think
On 2017-07-30 05:43, J. Landman Gay via use-livecode wrote:
There may be a minor difference when acceleratedRendering is on, but
not enough to really help much. I'll see if I can extract a group.
It's one from Swami's project, built dynamically, and all the images
are referenced, so it isn't as
from my iPhone
> On 29 Jul 2017, at 23:17, J. Landman Gay via use-livecode
> <use-livecode@lists.runrev.com> wrote:
>
>> On 7/29/17 8:07 PM, Mark Waddingham via use-livecode wrote:
>> So if you have a completely static scrolling group (i.e. one you can layout
>>
On 2017-07-30 01:06, Matthias Rebbe via use-livecode wrote:
Mark,
I cannot use the widget because of bug #20200.
I was hoping you were going to say 'because I hadn't thought to'
(although, I must confess that was a fanciful notion, having observed
your attention to detail over the years).
On 2017-07-30 02:35, J. Landman Gay via use-livecode wrote:
Isn't this the "datagrid scrolling" issue we just funded? The layout
has groups inside a container group.
No - not quite.
From what Dan said - he has a *fixed* layout - i.e. a group with 200
subgroups. Todd has used this approach
So - quick outline...
Set the layermode of the group to scrolling.
Make sure it is just a bare group - no scrollbars, no border.
Set the layermode of the other controls to static.
Set the acceleratedRendering of the stack to true.
Hopefully that should have some effect.
Warmest Regards,
On 2017-07-30 00:53, Monte Goulding via use-livecode wrote:
On 30 Jul 2017, at 8:49 am, Mark Waddingham via use-livecode
<use-livecode@lists.runrev.com> wrote:
However, the IDE submodule is set to stay (despite various discussions
about merging it internally - I've always said no, a
On 2017-07-30 00:44, Matthias Rebbe via use-livecode wrote:
stack "Untitled 1": execution error at line n/a (External handler
execution error: creation failed) near "creation failed"
Am i missing something?
It might be a bug - there's been a fair amount of churn in CEF stuff in
recent
On 2017-07-30 00:10, Mark Wieder via use-livecode wrote:
Have I mentioned lately how much I hate submodules?
Have I mentioned lately how much I hate submodules? ;)
Actually, submodules actually do their job really quite well. They
aren't ideal, but they do enforce modularity (hence the name
On 2017-07-29 23:10, Monte Goulding via use-livecode wrote:
Hmm… I don’t do that and I seem to get along ok. Indeed in the newer
versions of Xcode I can witch branches then regenerate the config and
Xcode is fine with that.
Interesting - maybe something subtle has changed in recent months
On 2017-07-29 13:10, Jonathan Lynch via use-livecode wrote:
So... if we use the wait command, and deploy to HTML5, the engine
converts it to JavaScript with extra functions because the engine
added in asynchronous timeouts? And you preserve all the variable
values of the source LC script across
On 2017-07-29 23:00, Monte Goulding via use-livecode wrote:
Ah, yes, it doesn’t do anything if the sdk is already linked in.
There’s a few things I’d like to change about that script. One is it
should link in any SDKs that are in the cache or found in the other
xcode app bundles rather than just
On 2017-07-29 22:51, Monte Goulding via use-livecode wrote:
As we get more contributors gitter will become more active and you
will be able to answer many of the questions for each other. There’s
little point expecting a great deal of chatter if there’s only half a
dozen people outside the
On 2017-07-29 09:11, james--- via use-livecode wrote:
Well imagine my surprise to see three (and now four) user list digests
waiting for me this morning.
Hopefully that wasn't entirely down to me - although I did send 30+
emails to the use-list yesterday...
Going through them and enjoying
On 2017-07-29 21:00, Mark Wieder via use-livecode wrote:
Yeah. That's what I was trying to say.
I know - I just thought I'd take the opportunity to be a little more
blunt about it since you gave me the hook to do so - i.e. gitter is not
a route to get direct tech support from our engineers
I use Firefox for dev'ing on the html5 engine as it tends to be at the
forefront of 'what is to come' and also I find it's dev console somehow more
responsive and 'better' than Chrome's and Safari's when dealing with huge blob
of JS that the html5 engine is.
For everything else I use Chrome.
9/2017 01:44 AM, Mark Waddingham via use-livecode wrote:
>> P.S. None of us tend to sit on gitter.io - we can only process so many
>> simultaneous inputs - however gitter does send email notifications when
>> someone posts something on there and usually it doesn't take too lon
On 2017-07-29 07:11, Brian Milby via use-livecode wrote:
Is it possible to compile the LiveCode IDE on Mac OS 10.12.6?
Yes - some of us (at LiveCode) use 10.11, some 10.12. We also have a
10.9 machine which is more of a 'hot-desk'. (One of our test machines is
10.10 IIRC, so we have all
On 2017-07-29 09:53, Richmond Mathewson via use-livecode wrote:
I would suppose I need that software to "phone home" and check itself
against a list (text document)
or something so that only 5 copies can function "out there", and if a
6th version phones home it
will do a "Peter Graves" and
On 2017-07-29 07:11, J. Landman Gay via use-livecode wrote:
On 7/28/17 7:29 PM, Mark Waddingham via use-livecode wrote:
P.S. At some point I'll write at length about the 'wait' problem in
HTML5. Whilst I try not to let myself be kept awake at night by
engineering problems related to work
s for functions. What
> functionality do you access to induce a wait?
>
> Sent from my iPhone
>
>> On Jul 28, 2017, at 8:29 PM, Mark Waddingham via use-livecode
>> <use-livecode@lists.runrev.com> wrote:
>>
>> Hi Hermann,
>>
>> First of a
Yes - the commercial version of LiveCode server (available through your
LiveCode account area) can use protected stacks.
Warmest Regards,
Mark.
Sent from my iPhone
> On 28 Jul 2017, at 20:36, Todd Fabacher via use-livecode
> wrote:
>
> Can we call a password
>> On Jul 28, 2017, at 14:14 , Mark Waddingham via use-livecode
>> <use-livecode@lists.runrev.com> wrote:
>>
>> Again this is general and not specific. The case Richmond put forward is
>> very much a case of over-reach from my point of view (it is quite possible
Hi Hermann,
First of all please don't take any offence at my email as none was
intended.
I was mainly trying to explain that whilst there are many things the
HTML5 engine does not do, which means many stacks will not work without
changes/workarounds (indeed, somewhat significant ones) -
This is why all lawyers (barring any who subscribe to this list) ought to be
> dragged through the mud and run out of town.
>
> Bob S
>
>
>> On Jul 28, 2017, at 11:32 , Mark Waddingham via use-livecode
>> <use-livecode@lists.runrev.com> wrote:
>>
>> The reas
On 2017-07-28 20:40, Richmond Mathewson via use-livecode wrote:
Ooer . . . and how, pray tell, does one tease out what one learnt in
one loaction from what one learnt in another?
I appreciate that in the realm of teaching (the example you gave) the
area is a little grey.
However, in the
On 2017-07-28 20:17, Richard Gaskin via use-livecode wrote:
I think we're closer on this than might have originally seemed:
Indeed - on this and most things I think.
I've always assumed that you tend to ask certain questions, or phrase
things in a certain in way to give us (well, me,
601 - 700 of 966 matches
Mail list logo