On Sun, Oct 26, 2014 at 8:28 AM, Mark Wieder mwie...@ahsoftware.net wrote:
Well, that's special.
While I have the Untitled backup drive removed from Spotlight,
Sorry for taking a while to answer this, but yesterday I didn't have my TM
HD available so I couldn't be sure.
What do you mean by
I have in the past disliked Time Machine. In those days I had a regular hard
drive, and it seemed sometimes that it would take the full hour to backup,
meaning that it was backing up continuously, and noticeably affecting the
responsiveness of the system while it was doing that. Now I use SSD
I use Time machine for local backups and all my LC dev files are on Google
Drive so I feel pretty comfortable with recovering any stack files I need.
There's another level of recovery I made available in lcStackBrowser. It's
not made for backups per se, more in the way of keeping temporary
Colin-
Saturday, October 25, 2014, 6:11:57 AM, you wrote:
I have in the past disliked Time Machine. In those days I had a
regular hard drive, and it seemed sometimes that it would take the
full hour to backup, meaning that it was backing up continuously,
and noticeably affecting the
Peter Haworth wrote:
I use Time machine for local backups and all my LC dev files are
on Google Drive so I feel pretty comfortable with recovering any
stack files I need.
That redundancy is probably a good idea. Backup services fail, media
fails, all sorts of things can happen.
Here I
See if this article helps with the time it takes to do TM backups:
http://mactips.dwhoard.com/mactips/other-applications/time-machine-slow
http://mactips.dwhoard.com/mactips/other-applications/time-machine-slow
___
use-livecode mailing list
Andrew-
Friday, October 24, 2014, 10:18:24 PM, you wrote:
Dropbox and backup suggestions aside, I can't help but feel 7.0 was not
ready for primetime. My experience has been giant standalones to cater to
features I don't use, and lackluster performance.
I hear what you're saying, and I'm not
Mark Wieder wrote:
Mark Wieder I'm thinking of switching over to Dolly Drive (for
local storage only, not cloud), so I'd welcome any comments
yea or nay that anyone has on that.
Have you considered OwnCloud? Space limited only by your hard drive
budget, total control, native sync clients
Colin-
Saturday, October 25, 2014, 10:52:21 AM, you wrote:
See if this article helps with the time it takes to do TM backups:
Thanks. I had high hopes for that, but unfortunately that's not what I
see. I do see things like
10:00:36 AM com.apple.backupd Starting standard backup
10:00:37 AM
Part of that article is to do with Spotlight. Are you sure you don’t have
Spotlight set up to index the backup drive?
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
Richard-
Saturday, October 25, 2014, 10:59:09 AM, you wrote:
Have you considered OwnCloud?
Hmmm... thanks for the lead. No, I hadn't. Based on the name I figured
they were just another cloud storage thing. And for a number of
obvious and non-obvious reasons I have no intention of throwing my
Colin-
Saturday, October 25, 2014, 11:27:39 AM, you wrote:
Part of that article is to do with Spotlight. Are you sure you
dont have Spotlight set up to index the backup drive?
Well, that's special.
While I have the Untitled backup drive removed from Spotlight,
apparently Spotlight still has
Mark Wieder wrote:
Richard-
Saturday, October 25, 2014, 10:59:09 AM, you wrote:
Have you considered OwnCloud?
Hmmm... thanks for the lead. No, I hadn't. Based on the name I figured
they were just another cloud storage thing. And for a number of
obvious and non-obvious reasons I have no
I never test the RC versions or the Dev releases. Since I do not produce
commercial apps, I don’t have the need to test for compatibility. There were
other things going wrong before that. The app did not run the way it should. I
have a database setup card I go to that is designed to make a
I figured you might want a copy so I saved it. Do you also need the sqlYoga
library I use? I suppose you can just use the public release. I will need to
send along a copy of the sqLite database I use with it. The whole app depends
on the database of course.
Bob S
On Oct 23, 2014, at 16:49
Very good suggestion. I do have a time machine backup, but it is not in the
office, it is at home so I can lose a days worth of changes that way. I will
look into that.
Bob S
On Oct 23, 2014, at 17:05 , Pi Digital s...@pidigital.co.uk wrote:
Hi Bob
I would like to recommend to you
On Fri, Oct 24, 2014 at 10:33 AM, Bob Sneidar bobsnei...@iotecdigital.com
wrote:
... but I *am* using sqlYoga and I am not sure if I need to be using a 7.0
converted version of that library.
SQL Yoga should behave well with 7.0 gm-1. In prior versions of 7.0 there
were some backwards
Solutions like dropbox are good, but would either need you to manually back
things up, or maybe an Automator script to copy important files over. With Time
Machine I have a less than one hour old backup of any file I might need, not
just the ones that I think I will need, or remembered to copy
I keep all my projects on Time Machine, but current projects are also on
Dropbox, which I often use to share work with customers. File that are
in Dropbox are automatically updated when you change them. There is no
need to update them manually.
--
Best regards,
Mark Schonewille
Bob Sneidar wrote:
I never test the RC versions or the Dev releases. Since I do
not produce commercial apps, I don’t have the need to test
for compatibility.
That's true for those versions you intend to never use. :)
LC is very flexible, and we all do different things with it, so if we
want
After V7 upgrade, but before the crash.
Bob S
On Oct 24, 2014, at 08:52 , Richard Gaskin
ambassa...@fourthworld.commailto:ambassa...@fourthworld.com wrote:
When you say other things going wrong before that, do you mean before the
crash or before v7?
--
Richard Gaskin
Truth is, I develop side projects. It’s never actually been my job description,
although my employers have been happy to use what I produce! :-)
What I develop is primarily for my own use and convenience. I wish I were more
productive in this regard, but after all I have a full time job, during
Bob Sneidar wrote:
Testing developer releases and release candidates is not high
on my priority, but given my recent experience, maybe it should
be. :-)
For me it's made the work more fun.
With any final release, at the moment it's done it's effectively dead, a
static thing that no longer
Colin-
Friday, October 24, 2014, 8:01:56 AM, you wrote:
Solutions like dropbox are good, but would either need you to
manually back things up, or maybe an Automator script to copy
important files over.
Au contraire. Dropbox keeps old versions for up to 30 days
automatically. I don't know the
I understand how the folder synching works, but in my case I have a 750 GB SSD
that may well have many gigabytes of stuff that I don’t want to lose. Having
that backed up to an external 2TB drive every hour gives me some security.
On Oct 24, 2014, at 10:11 PM, Mark Wieder
Colin-
Friday, October 24, 2014, 7:42:19 PM, you wrote:
I understand how the folder synching works, but in my case I have
a 750 GB SSD that may well have many gigabytes of stuff that I dont
want to lose. Having that backed up to an external 2TB drive every
hour gives me some security.
Um.
Dropbox and backup suggestions aside, I can't help but feel 7.0 was not
ready for primetime. My experience has been giant standalones to cater to
features I don't use, and lackluster performance. I know others will
disagree but I devoted the last four to five years to livecode and come out
Hi all.
Well I upgraded to version 7.0.0. I opened a stack I have been working on, but
it started misbehaving. I just had it open and running in version 6.6.4. In the
process of trying to see where things were going wrong, version 7.0.0
unexpectedly quit. Now the stack is corrupted and
I don’t suppose you use a Mac with Time Machine running do you? If you are you
can retrieve a copy from an hour ago.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
NVM I discovered there is a file of the same name ending in a tilde (~) which
is a backup of the corrupted file. I was able to open it in 7.0 and save in the
last legacy format. Unsure what happened initially, but I will be keeping a
copy of the old stack intact for a while before migrating to
Bob Sneidar wrote:
Well I upgraded to version 7.0.0. I opened a stack I have been
working on, but it started misbehaving. I just had it open and
running in version 6.6.4. In the process of trying to see where
things were going wrong, version 7.0.0 unexpectedly quit.
How did this behavior in
Hi Bob.
I'm sorry you experienced in issue. We've not had any reports of stack
corruptions in 7 for some months. We'd be very keen to get a copy of the
corrupted stack and the working format to see if we can work out what
happened. If you'd be happy to share the stack, please sent it privately to
Hi Bob
I would like to recommend to you using Dropbox and putting your stacks into its
folders. This has saved me no end of times as it holds many previous versions
of your files as backups. I now have a premium subscription and get infinite
version backups and remembers even if I change file
can’t restart because the bug is still around
in a stable release.
ÉrIC
-- Original Message --
De: Benjamin Beaumont b...@runrev.com
Objet: Rép : The Bearer Of Bad News
Date: 24 octobre 2014 02:49:27 UTC+3
À: How to use LiveCode use-livecode@lists.runrev.com
Hi Bob.
I'm
34 matches
Mail list logo