On February 26, 2018 9:40:58 PM Richard Gaskin via use-livecode
wrote:
There are many ways that imagined scenario might for all I know be
accounted for in the way Dropbox is written. But there may also be
other scenarios that can produce the same corrupted result that I
haven't thought of.
On 02/26/2018 07:38 PM, Richard Gaskin via use-livecode wrote:
Consider this scenario with stack files, for example:
Mark writes a stack, then I open it, then you open it. You and I are
both making changes, and I save mine a few seconds before you save
yours. In that scenario, what's on disk
Knapp Martin wrote:
> Thanks for the in-depth reply. Are there known issues with saving LC
> stacks to Dropbox? I was thinking of Roland's issue with corruption
> and Phil's suggested fix of watching the file with the tilde character
> before allowing a quit to complete. I have an app where users
On 02/26/2018 05:14 PM, Richard Gaskin via use-livecode wrote:
Knapp Martin wrote:
> Richard, could you elaborate on the issues with Dropbox?
I first came across it in a search at Google for "dropbox sqlite",
looking for tips on making the most of that relationship. What I found
was a long
Thanks for the in-depth reply. Are there known issues with saving LC stacks to
Dropbox? I was thinking of Roland's issue with corruption and Phil's suggested
fix of watching the file with the tilde character before allowing a quit to
complete. I have an app where users create documents (stacks)
Knapp Martin wrote:
> Richard, could you elaborate on the issues with Dropbox?
I first came across it in a search at Google for "dropbox sqlite",
looking for tips on making the most of that relationship. What I found
was a long series of support forum and blog posts filled with horror
storie
Richard, could you elaborate on the issues with Dropbox? Is there a recommended
procedure for dealing with it?
Marty
On Feb 26, 2018, at 11:07 AM, Richard Gaskin via use-livecode
wrote:
> Stack file corruption is very rare with LiveCode. It has happened now and
> then, but is rare enough (a
I was using java jdk1.8.0_121.jdk
Even though documentation says it should work (any above 1.6 should work)
It an attempt of get to jdk1.8.0_152.jdk, I had installed Java 9, inadvertently.
To make a long story short, I installed sdkman to manage my Java
(very cool, http://sdkman.io/)
Any ended
Stack file corruption is very rare with LiveCode. It has happened now
and then, but is rare enough (and of course serious enough) to merit
attention by the LC team.
Even if we can mitigate the issue by altering your code, the main
question remains: why does a save operation become interrupte
Hi Roland,
This is the only reply of yours that I see.
On 2/26/18 4:13 AM, R.H. via use-livecode wrote:
Thanks, Phil and Tom
I already replied, but I cannot see my first reply to your answers.
Did it appear in the list?
Phil:
"quitMe" should be sent before 'saveMe' is executed, because th
Ali Lloyd wrote:
> Essentially my point of view is that a properties property should
> return all properties. Otherwise it can't really work with widgets.
Would it simplify things if what is needed for widgets is done for
widgets, and the current data derived from engine-native objects remains
It would be nice if we had more consistent locations to check for feedback,
without special cases and provisos. For example, returning a value from a
function and a command (forget "for value" and "for error") populate it or
the result depending on whether we are using a command or a function. On
Hi all,
Read about new developments in LiveCode open source and the open source
community in today's edition of the "This Week in LiveCode" newsletter!
Read issue #118 here: https://goo.gl/NzB8We
This is a weekly newsletter about LiveCode, focussing on what's been
going on in and around
Hi Christer,
>There was an error while saving the standalone application
>..then about 20 ines of groups of numbers and different command logs.
Without seeing the logs it is difficult to guess what is wrong.
Another thing to note is that when using a new Xcode version, you have to
make s
Combination Xcode 9.2 and LC 8.1.9 creating iOS app states:
There was an error while saving the standalone application
..then about 20 ines of groups of numbers and different command logs.
However, it sloowly starts in simulator, directly from LC - provided that you
select only one device from t
Thanks, Phil and Tom
I already replied, but I cannot see my first reply to your answers.
Did it appear in the list?
Phil:
>> "quitMe" should be sent before 'saveMe' is executed, because the 'save'
command is blocking. It would prevent 'quitMe' from being sent until (in
this case) 1 second after
Let me improve this a bit.
On 2/23/18 4:19 PM, Phil Davis via use-livecode wrote:
Roland,
I believe Tom is exactly right. I would restructure your two closing
handlers like this:
local sMyFilename
on closeStack
put the filename of me into sMyFilename
saveMe
send "quitMe" in 1
It always give a "q" as that is the Unicode name for "q".
Richmond.
On 26.02.2018 01:55, J. Landman Gay via use-livecode wrote:
On 2/25/18 1:57 PM, Richmond Mathewson via use-livecode wrote:
I want to send a rawKeyDown signal that fakes typing on the key on my
keyboard
that has the underlyin
18 matches
Mail list logo
