Re: how to clear residual garbage in a stack?

2018-05-25 Thread J. Landman Gay via use-livecode
I haven't actually tried it but would it work to just put empty into the 
field before deleting the card? That would be sort of a "clean as you go" 
approach.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On May 25, 2018 9:26:21 PM Neville Smythe via use-livecode 
 wrote:


So now we have confirmed the 
“delete-card-with-unshared-textfield-leaves-unreferenced-text-which-compact-does-not-remove” 
bug (thanks to Brian and Richard) the question remains how to actually 
remove the garbage.


As Brian says deleting the background groups will remove the residual text; 
you then  have the task of replacing the groups. I have found that a 
simpler method: turning on sharedText, then turning it back off and 
replacing text also works.


So, a recipe is
1. Copy the target stack, don’t work on the original
2. Go through the stack (and its substacks) to find background groups which 
have fields with sharedText false (this is an outer loop for each stack)

3. Find all cards which such groups
4. Save the text from every found field from every found card into an array
5. Turn on sharedText for each field
6. Visit each card and put empty into each found field (not sure if this 
step is necessary, but I think it is)

7. compact the stack
8. Turn off sharedText for each field
9. Visit each card to replace the individual text saved in the array
10.Save the stack.

Sounds complex but the process took only a couple of seconds to clean up my 
 9MB stack with 325 cards + lots of substacks and lots of groups. It saved 
1.5MB, not as much as I was hoping but still worthwhile. That’s 15% off the 
time Windows 10 users have wait for save to finish.


This is not a workaround for the bug. It is a fix for affected stacks.

Neville Smythe
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode





___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Windows 10 and LC9.0

2018-05-25 Thread Sean Cole (Pi) via use-livecode
Tool Palette - BROKEN
Script Editor - BROKEN
Project Browser - BROKEN
Geometry Manager - BROKEN
Inspector - BROKEN
Message Box - BROKEN
Dictionary/Guide - USELESS
LiveCode = UNFIT FOR PURPOSE

Is there ANY part of this Freakin' software that actually frakin works??

KEVIN! Stop adding 'new' stuff and FIX THE DAMNED PROGRAM!! Don't release
stuff as 'STABLE' things that don't actually work and then expect us to
keep paying for it. You're affecting other peoples livelihood and stability
here! I should be a clear example to you of that very fact!

It's no wonder I went frekin mental! £^&%**^@(*@&^%£%@%@...

Sean Cole
*Pi Digital Productions Ltd*
www.pidigital.co.uk
+44(1634)402193
+44(7702)116447
'Don't try to think outside the box. Just remember the truth: There is no
box!'
'For then you realise it is not the box you are trying to look outside of,
but it is yourself!'

eMail Ts & Cs    Pi Digital
Productions Ltd is a UK registered limited company, no. 5255609

On 25 May 2018 at 23:13, Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:

> On 05/25/2018 12:05 PM, John Burtt via use-livecode wrote:
>
> Also fixed is the bug that it was almost impossible to place new controls
>>> from the Tools palette to the IDE stack using drag-and-drop. It had been
>>> an
>>> uncontrollable trial-and-error thing. Often enough I had to try several
>>> times to "hit" the stack window and place the control So, I am happy
>>> about
>>> the fix very much.
>>>
>>
>> Not fixed on a Mac. Totally unreliable.
>> I don't even try anymore. Have to use the menu.
>>
>
> Ouch. That's depressing. I wasn't aware of that, but it's been many years
> now since I've used the tools palette. May I suggest PowerTools?
>
> http://www.ahsoftware.net/PowerTools/PowerTools.lc
>
> --
>  Mark Wieder
>  ahsoftw...@gmail.com
>
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: how to clear residual garbage in a stack?

2018-05-25 Thread Neville Smythe via use-livecode
So now we have confirmed the 
“delete-card-with-unshared-textfield-leaves-unreferenced-text-which-compact-does-not-remove”
 bug (thanks to Brian and Richard) the question remains how to actually remove 
the garbage.

As Brian says deleting the background groups will remove the residual text; you 
then  have the task of replacing the groups. I have found that a simpler 
method: turning on sharedText, then turning it back off and replacing text also 
works.

So, a recipe is
1. Copy the target stack, don’t work on the original
2. Go through the stack (and its substacks) to find background groups which 
have fields with sharedText false (this is an outer loop for each stack)
3. Find all cards which such groups
4. Save the text from every found field from every found card into an array
5. Turn on sharedText for each field
6. Visit each card and put empty into each found field (not sure if this step 
is necessary, but I think it is)
7. compact the stack
8. Turn off sharedText for each field
9. Visit each card to replace the individual text saved in the array
10.Save the stack.

Sounds complex but the process took only a couple of seconds to clean up my  
9MB stack with 325 cards + lots of substacks and lots of groups. It saved 
1.5MB, not as much as I was hoping but still worthwhile. That’s 15% off the 
time Windows 10 users have wait for save to finish.

This is not a workaround for the bug. It is a fix for affected stacks.
  
Neville Smythe
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Was: URGENT: MergGoogle no longer works on iOS: CLIENTS VERY UNHAPPY

2018-05-25 Thread William Prothero via use-livecode
Sean:
I have never met you except through this listserve and, if my memory serves, on 
the Direct-L listserve, where you’ve been a generous, respected and positive 
contributor.

The main takeaway I hope you have from this is that the folks on this list 
value you and care about your well-being and we all cringe when something like 
what happened to you, happens to anybody else. I’ve found that, in this world, 
“Sh**t" happens” and there isn’t a heck of a lot we can do about it except try 
hard to not feel like it’s a personal failure. In my case, a botched biopsy 
resulted in a 3 mo hospital stay, close to fatal, which I’m still recovering 
from. It makes me really value the time I have, my wife, my projects, my 
friends,  and sunny days.

Among my friends, we sometimes give “esteem baths”. Please take this outpouring 
of concern and even some $$ as evidence of our esteem and caring for you as a 
colleague and online friend.

Best wishes to you,
Bill

William A. Prothero
Prof Emeritus
University of California, Santa Barbara
Santa Barbara, CA
http://earthlearningsolutions.org


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Was: URGENT: MergGoogle no longer works on iOS: CLIENTS VERY UNHAPPY

2018-05-25 Thread Richard Gaskin via use-livecode

Hello Sean -

Very glad to read your post here.

There are only a couple things that may be useful to address here, but 
chief among them is gratitude for your open discussion of depression.


Culturally we too often stigmatize depression, anxiety, and a whole host 
of other conditions, unable to talk about them as easily as we talk 
about a broken leg or other more strictly physical things.


I believe every conversation about such conditions is a force for good 
in the world, making it easier for folks to express their own stories 
and for others to understand what the experience is like to be able to 
become more effective in supporting our friends.


We don't always get it right, but through healthy open dialog we can all 
learn how to be of ever better service to one another.




> I’ve not been able to face anyone or anything. I was not happy that
> the police had been called. I was not happy that my wife found out
> that way. I was definitely not happy that people had tried contacting
> my 14yr old son after cyber ploughing my social accounts.

That last part might have been me, and if so I owe you an explanation:

Through friends and family I've had experience with both suicidal 
ideation and actuality, so like many here I took your words quite seriously.


Somehow from that experience something in my instincts told me you'd be 
okay.  Still, as you probably know, the common protocol for anyone 
encountering such ideation is to respond as though it's a likelihood, 
because the stakes cannot be higher and it is something for which there 
is no Undo.


I tried to follow my instincts, but a nagging doubt had me checking 
regional news sources in case I was wrong.  When several days had passed 
and I'd found nothing relevant that was good.  But I also saw nothing 
from you online, not even on LinkedIn; I log in daily anyway, and when 
you post there it's normally a welcome part of my feed.


On LinkedIn your company is listed as having two employees.  You and I 
are already connected, so I took the liberty of clicking "Connect" for 
the second one, in hopes that I might ask only whether they've been in 
touch with you recently.


I did notice that the other Pi employee has the same last name.  I had 
assumed it was your brother.  If that was your son I certainly meant no 
intrusion, nor would have written anything alarming.


As it is the request was never responded to, so I've had no contact with 
anyone on this until replying to you now.




I've had my own challenges with family and such in recent years, so I 
have at least a sense of some of the burdens you've faced.  I know how 
sometimes things can be overwhelming.  I'm glad your here, both on this 
planet and on this list.  And as you've seen, no matter if you may not 
notice yourself, you've made enough of a strongly favorable impression 
among the others here that they see you as part of their extended 
family, happy to lend a hand as they would any good neighbor.


--
 Richard Gaskin
 Fourth World Systems



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Was: URGENT: MergGoogle no longer works on iOS: CLIENTS VERY UNHAPPY

2018-05-25 Thread Mark Wieder via use-livecode

Sean-

Others have chimed in quite well here, so I'll just add a few comments.

On 05/25/2018 09:07 AM, Sean Cole (Pi) via use-livecode wrote:

> // GoFundMe //
> This, too, is overwhelming. A little disturbing too as it was embarked on
> by people who know very little about me

Mmm... that's where you're wrong. From the time you joined the 
discussions here you've been an active part of the community, at times 
an excellent source of information, at others a welcome gadfly. There 
are a lot of folks in the community here that I know only through email 
and list conversations, and I have no idea what their personas are like. 
And for the most part I don't care. I think the response here was simply 
that one of our own was in trouble. This has nothing to do with you on a 
personal level, and everything to do with you on a personal level.


> It is necessary, though,

Not really, but thanks for the background.

> // Lessons Learned //
> That’s the second time a LiveCode app has put me in this position.

Been there, done that. More times than you.
Points in the LC rant are well taken.

> Their decision to have the next
> conf over in the far west shows their loyalty to, again, only a small 
part

> of the community, the rich and those already in America. Global?!?

Well, the last couple have been in Edinburgh, and while I love the place 
dearly, it's certainly not cheap to fly over from California. But we do 
it. Because I wouldn't miss a chance to network with folks during the 
conference. And remote access to the conference sessions is (almost) 
always offered if you can't make it in person.


--
 Mark Wieder
 ahsoftw...@gmail.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Windows 10 and LC9.0

2018-05-25 Thread Mark Wieder via use-livecode

On 05/25/2018 12:05 PM, John Burtt via use-livecode wrote:


Also fixed is the bug that it was almost impossible to place new controls
from the Tools palette to the IDE stack using drag-and-drop. It had been an
uncontrollable trial-and-error thing. Often enough I had to try several
times to "hit" the stack window and place the control So, I am happy about
the fix very much.


Not fixed on a Mac. Totally unreliable.
I don't even try anymore. Have to use the menu.


Ouch. That's depressing. I wasn't aware of that, but it's been many 
years now since I've used the tools palette. May I suggest PowerTools?


http://www.ahsoftware.net/PowerTools/PowerTools.lc

--
 Mark Wieder
 ahsoftw...@gmail.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Was: URGENT: MergGoogle no longer works on iOS: CLIENTS VERY UNHAPPY

2018-05-25 Thread Mike Bonner via use-livecode
 Curry-  don't know if such a thing would help your situation, but i'm
attaching a photo of my lift.  Its simply a relatively small i-beam solidly
anchored, a trolly to match, a 2000lb hoist (overkill) and a very simple,
self designed sling hooked to a home made spreader bar.  Lower it, sling in
front, spreader bar in back under my arms, push the button, and voila' I'm
levitating, at which point its easy to peter pan back and forth across the
room.  (Though I look like i'm ready to be processed at a butcher shop)
Compared to the cost of a "professional" ceiling lift, the cost was around
8K less before install costs (because you apparently can't just buy parts
here and DIY.)  Photo isn't great but here it is if LC will let it post.
Ignore the mess.

No go on attaching the photo, so heres the dropbox.
https://www.dropbox.com/s/5eckjh1hocpqeqx/IMG_2091.JPG?dl=1
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Was: URGENT: MergGoogle no longer works on iOS: CLIENTS VERY UNHAPPY

2018-05-25 Thread Curry Kenworthy via use-livecode


Mike:

> The most recent hit to my pride was the loss of ability
> to self transfer into my walk in tub

Ah, a fellow traveler indeed! I haven't been able to use my own 
insurmountable tub yet, still doing sponge baths.


Sean:

> I certainly don’t feel right putting in my invoice for
> the 3-4 months work for this stage of the app as it didn’t work
> when they actually needed it.

Always invoice monthly. It's better for everyone. Invoices actually help 
clients see the progress and the work involved, and stay on budget.


I've had at least $12,000 USD but probably closer to 15K in nonpayment 
over the years. That's hard to stomach! Especially when you're seriously 
handicapped, and the blood/sweat for every hour of work is more 
substantial than people realize. There are some people who deliberately 
avoid payment to increase profit or experiment with other people's 
money, but others misunderstand the dev process or just have cashflow 
problems themselves. I try to be understanding of others as they are 
understanding of me. (To paraphrase a famous saying.) But oh yes, it has 
an impact.


Things don't always work out perfectly behind the scenes either. One 
time (FieldTrip) I was delayed for weeks just trying to get a piece of 
info. LC had advised me of a certain upcoming feature that would impact 
addons, so to use the project funds wisely I wanted to make sure that I 
coded it right the first time and took advantage of it. I wanted to wait 
on that before starting the code. But for some reason I could get the 
actual info, no matter who I asked. It was weird; usually info comes 
readily and speedily from LC, precisely the opposite! An unfortunate and 
mysterious fluke. Finally I gave up on getting that info, but then had a 
big health issue and a change in the project partnership/funding, so the 
project timeline and my rep both took a hit, people were disappointed. 
Not fun. Sometimes these things just happen.


But life goes on! The world as a whole is not a terribly gentle place, 
but good people make ALL the difference. And we have some incredibly 
good people here.


> Certainly, my trust in third-party add-ons has gone
> and I will never again rely on them.

LiveCode started as an addon, didn't it? A very welcome one at that! No 
matter where you go, you'll find that all code products tend to draw 
upon other code. The big boys too? Oh yes.


Working over the years with Microsoft Office products I've come to 
understand not only how much code libraries are used, but also how often 
even the "standard" and open-source ones have issues. People who idolize 
Apple, OpenOffice, Google, or Microsoft don't realize the flaws in the 
code bases, but yes, they have bugs and limitations, sometimes in their 
own code and sometimes in the libraries they use. I've had to work 
around Apple and OO bugs/limitations.


One general problem is that backward-compatibility has been abandoned 
and even politicized/demonized by some of the big players. (Hello Mr. 
Jobs.) BC is actually just part of a bigger concept. I don't have the 
correct word for that concept handy (Richard?) but when we build upon 
other frameworks (like FB, Google, or LiveCode itself), it helps if the 
APIs and keywords do not change rapidly. A sound foundation. That way 
"middle" code can be designed to last. If the big guys wantonly break 
code, it's an incredible waste that the consumer (or someone, sometimes 
us) has to pay. I know, this is not what you're hearing from everyone, 
it's not trendy, not the buzzword, but there it is. A well-designed API 
can be relatively stable even as the code behind it constantly evolves. 
We're going to keep seeing a lot more headaches and financial impacts of 
this upside-down and possibly unsustainable approach until some of the 
more well-connected in the tech world decide to change the trend again.


Best wishes,

Curry Kenworthy

Custom Software Development
LiveCode Training and Consulting
http://livecodeconsulting.com/


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Was: URGENT: MergGoogle no longer works on iOS: CLIENTS VERY UNHAPPY

2018-05-25 Thread Mike Bonner via use-livecode
 Hey Sean,

While its true that the full details of what was going on weren't
available, there were 2 things that stood out to me from your previous
writings.  Large amounts of distress, and a monetary connection to the
distress.  I can't help with the distress directly, but it just makes sense
to me that sending a bit of financial care your way might help smooth out
this rough patch.  I myself have had to face down my pride issues and
accept help in the past.. well actually all the time due to my health
stuff.  If not for the care of people around me, my position would be much
much worse. The most recent hit to my pride was the loss of ability to self
transfer into my walk in tub, (a thing I learned the hard way.)  People who
care about me got together, designed, and installed a ceiling lift that
works amazingly well.  And I can do an engine swap in my bathroom.  (Its a
mite over-engineered.)  Just one example of people being awesome.

One thing I've taken to heart is a simple saying.  "Accepting the gift,
honors the giver."

If it will help, I'd be honored to assist a bit more, but now that we've
heard from you, I would prefer to leave that to your discretion.  If you
wish, you are welcome to send a direct email to me.

Take care of yourself,

Mike
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Windows 10 and LC9.0

2018-05-25 Thread John Burtt via use-livecode
Some of these bugs are not specific to Windows machines. Neither are they 
dependent on the speed of the machine. I see these everyday and I'm using a 
very fast MacBook Pro.
> 
> Another real problem is when lots of controls are selected (maybe more than
> 10). Moving the selection using arrow keys is a pain. Even moving the
> selected controls with the mouse can make the system unusable. It can take
> 30 seconds to move even one pixel. Grouping controls and moving the group
> is the only option in such case and then working well. This has been the
> same problem in previous versions.

   I get this. One big pain.
> 
> Also fixed is the bug that it was almost impossible to place new controls
> from the Tools palette to the IDE stack using drag-and-drop. It had been an
> uncontrollable trial-and-error thing. Often enough I had to try several
> times to "hit" the stack window and place the control So, I am happy about
> the fix very much.

   Not fixed on a Mac. Totally unreliable.
   I don't even try anymore. Have to use the menu.
> 
> There has been a problem with the "Find and Replace" window in previous
> versions. This problem still exists. Do not touch the window in trying to
> resize it. It will then suddenly shrink to a strange width and becomes
> unusable. The only way to change this is a restart of LiveCode. Just never
> resize this window!!! (I am not going to touch the IDE stacks)

   Not this exactly, but I can usually resize the message box one time. From 
then on, it is not resizable unless i close and reopen it again. And LC likes 
to open some of my saved stacks at the default size of new stacks. I have to 
script a preOpenCard handler to handle the resizing, or do it myself over and 
over again.
> 
> What is now a new problem with 9.0, and a bit of an annoyance, is the fact
> that the property inspector does not keep the resized value when changing
> when selecting another control. Each time, the window falls back to some
> default size and then it must be resized again, or the scroll bar must be
> used. Again, it is not critical but hinders work-flow very much. For
> example, I prefer to look at layer numbers in the property inspector, and
> just go through each control with an open property inspector without having
> to resize the window or scroll it all the time.

   This happens on my machine too. 

   John


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Was: URGENT: MergGoogle no longer works on iOS: CLIENTS VERY UNHAPPY

2018-05-25 Thread Heather Laine via use-livecode
Sean. Thank you for writing. I'm so relieved to hear you are still alive. 

At the end of the day, this is what matters. Everything else can be fixed, 
recovered, moved on from.

Just wanted to say that.

Best

Heather


Heather Laine
Customer Services Manager
LiveCode Ltd
www.livecode.com



> On 25 May 2018, at 17:07, Sean Cole (Pi) via use-livecode 
>  wrote:
> 
> Dear All
> 
> 
> This is going to be a long one so I’ll break it down into sections to make
> it easier to read and get the points across (hopefully).
> 
> // Thanks //
> First off, a great deal of thanks has to go out to everyone who contacted
> both during and after the incident on May 2nd. It is overwhelming to see
> the attempts of support offered over the last couple of weeks. Thank you,
> each one of you.
> 
> 
> // GoFundMe //
> This, too, is overwhelming. A little disturbing too as it was embarked on
> by people who know very little about me or the facts behind the situation.
> Indeed, some of those provided here and on the GFM site were distorted from
> the truth of the matter. I would never have asked for this or expected
> it... but the generosity demonstrated by so many in the community is so
> very much appreciated.
> 
> It is necessary, though, to set a few matters straight to make sure all
> understand what actually took place and why things got the way they did.
> 
> 
> // Background //
> On a personal note, I’ve suffered from clinical depression, diagnosed and
> medicated since ‘03. During that time I have had 5 serious mental (nervous)
> breakdowns. Only one of these had been work-related. What I suffered this
> time was only a half breakdown it transpires and has been ‘easier’ to
> recover from. My wife, Judith, has been a major contributing factor in this.
> 
> The project is one that if been working on since April ‘17 on and off, a
> few weeks at a time. It’s for a tv production company that produces game
> shows in the UK who required a working prototype of a game for development,
> testing, production and pitching purposes. This is the second one I was
> producing for them. The last stage of its production started around
> February with final tweaks and bug fixes along with a couple of new
> features. It all went well and the client had planned to set up a day to
> film a working pilot episode. I continued to bug fix leading up to the day
> till the 2nd of May 3am, the morning of the gig. I went to bed at that time
> happy that everything was working fine.
> 
> /*
> Bear in mind that somewhere in the middle of April 2018, Adobe had also
> changed their policy for oAuth which had repercussions on another client’s
> software who codes in LC5.0.2 (because he prefers to ‘own’ software rather
> than ‘rent’ it). I created a library for him to access Adobe Sign but
> failed from 5.0.2 because it only uses TLS1.0 and Adobe require TLS1.1 or
> 1.2. I was able to fix this with a mini hack of LC5.0.2.
> */
> 
> 
> // The Incident //
> It turns out, however, that at 00:01 PDT (8am BST I think) of May 2nd
> Google changed something key to the App. Due to various security risks,
> Google had decided to deprecate the use of webviews for authenticating
> oAuth entry. Our app used GoogleSheets as a simple way to enable the client
> to update key features of the app live, specifically, questions, categories
> and running orders. The App, which would run live and display on the
> projected screen in front of the contestants, would call on the GSheet with
> updated data through the demo.
> 
> From between 8am and 10am UK time when I eventually woke up, the client had
> evidently been desperately texting, emailing and trying to call me to let
> me know the App wasn’t working anymore. It had been working at first then
> suddenly wasn’t. They would only get a screen that said it could no longer
> authenticate entry and login to Google services. This, of course, baffled
> me as it had all been working fine up to just 7hrs before.
> 
> As the desktop version appeared not to be affected (as I had found after a
> lot of testing that morning) so I used it to create an up to date database
> internally in the app and upload as an enterprise app for them to install.
> This gave them the ability to at least start using it although without the
> ability to update and change the order of events dynamically using the
> Google Sheets method. This was a key part of making it work.
> 
> 
> // The Repercussions //
> Once I got to the studio it was evident how much this had affected
> production. It had all become very clunky with little to no fluidity or
> slickness we would have had if it were working properly. The
> director/producer was understandably perplexed and irritated. It now meant
> that every time an answer was given and a step through the game occurred we
> had to rebuild the application with manually updated data and get each
> device to download the latest version of the app. The game is usually very
> fast paced 

RE: Windows 10 and LC9.0

2018-05-25 Thread Clarence Martin via use-livecode
I agree. I have seen this more times than I like.

-Original Message-
From: use-livecode  On Behalf Of
Curry Kenworthy via use-livecode
Sent: Friday, May 25, 2018 10:43 AM
To: use-livecode@lists.runrev.com
Cc: Curry Kenworthy 
Subject: Re: Windows 10 and LC9.0


Roland said:

 > The kluge is turning off everything that is offered to support  > script
hiliting and debugging such as bracket completions, etc.

This is one of the reasons I used LiveCode 6.7, and not 8 or 9, for my LC
Conference presentation. When displaying code to others, nice to have the
script coloration turned on! :)

 > Opening LiveCode 9.0 on my computer (8MB RAM, 2 years old,  > Acer
Aspire) takes about 30 seconds.

Every time LC starts, I'm guessing it also runs "Setup" (which shows as
"Installer" in Task Manager) to check for LC updates.

And something there is SERIOUSLY messed up! Over time you can wind up with
multiple Setup processes hung in memory per LC version, and this can happen
for multiple versions. Big system drag.

So I've gotten in the habit of deleting the Setups (not the real
installers) and another way is turning off all update features in
Preferences. That helps with LC startup and system performance.

Has anyone done bug report on this?

 > For this reason, I would like to see much  > more attention towards
Windows and Android.

Yep!

I fully endorse Richard's suggestion for the LC team to spend some weekly
time on Windows. Hopefully a real native installation, but in any case, the
Windows session needs to be kept running for days (or at least one full day)
as it does for a real user, not just for minutes.

I could add a similar suggestion - to have the team spend some time using LC
itself, that is using the IDE. Perhaps spending a couple hours weekly in the
IDE working on a continuing project stack, not just a few minutes on a test
stack from scratch. That intimacy with the IDE will pay off! Use 6.7 as a
reference point of what you had before in terms of features and polish.

Best wishes,

Curry Kenworthy

Custom Software Development
LiveCode Training and Consulting
http://livecodeconsulting.com/


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Windows 10 and LC9.0

2018-05-25 Thread Curry Kenworthy via use-livecode


Roland said:

> The kluge is turning off everything that is offered to support
> script hiliting and debugging such as bracket completions, etc.

This is one of the reasons I used LiveCode 6.7, and not 8 or 9, for my 
LC Conference presentation. When displaying code to others, nice to have 
the script coloration turned on! :)


> Opening LiveCode 9.0 on my computer (8MB RAM, 2 years old,
> Acer Aspire) takes about 30 seconds.

Every time LC starts, I'm guessing it also runs "Setup" (which shows as 
"Installer" in Task Manager) to check for LC updates.


And something there is SERIOUSLY messed up! Over time you can wind up 
with multiple Setup processes hung in memory per LC version, and this 
can happen for multiple versions. Big system drag.


So I've gotten in the habit of deleting the Setups (not the real 
installers) and another way is turning off all update features in 
Preferences. That helps with LC startup and system performance.


Has anyone done bug report on this?

> For this reason, I would like to see much
> more attention towards Windows and Android.

Yep!

I fully endorse Richard's suggestion for the LC team to spend some 
weekly time on Windows. Hopefully a real native installation, but in any 
case, the Windows session needs to be kept running for days (or at least 
one full day) as it does for a real user, not just for minutes.


I could add a similar suggestion - to have the team spend some time 
using LC itself, that is using the IDE. Perhaps spending a couple hours 
weekly in the IDE working on a continuing project stack, not just a few 
minutes on a test stack from scratch. That intimacy with the IDE will 
pay off! Use 6.7 as a reference point of what you had before in terms of 
features and polish.


Best wishes,

Curry Kenworthy

Custom Software Development
LiveCode Training and Consulting
http://livecodeconsulting.com/


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Was: URGENT: MergGoogle no longer works on iOS: CLIENTS VERY UNHAPPY

2018-05-25 Thread Sean Cole (Pi) via use-livecode
Dear All


This is going to be a long one so I’ll break it down into sections to make
it easier to read and get the points across (hopefully).

// Thanks //
First off, a great deal of thanks has to go out to everyone who contacted
both during and after the incident on May 2nd. It is overwhelming to see
the attempts of support offered over the last couple of weeks. Thank you,
each one of you.


// GoFundMe //
This, too, is overwhelming. A little disturbing too as it was embarked on
by people who know very little about me or the facts behind the situation.
Indeed, some of those provided here and on the GFM site were distorted from
the truth of the matter. I would never have asked for this or expected
it... but the generosity demonstrated by so many in the community is so
very much appreciated.

It is necessary, though, to set a few matters straight to make sure all
understand what actually took place and why things got the way they did.


// Background //
On a personal note, I’ve suffered from clinical depression, diagnosed and
medicated since ‘03. During that time I have had 5 serious mental (nervous)
breakdowns. Only one of these had been work-related. What I suffered this
time was only a half breakdown it transpires and has been ‘easier’ to
recover from. My wife, Judith, has been a major contributing factor in this.

The project is one that if been working on since April ‘17 on and off, a
few weeks at a time. It’s for a tv production company that produces game
shows in the UK who required a working prototype of a game for development,
testing, production and pitching purposes. This is the second one I was
producing for them. The last stage of its production started around
February with final tweaks and bug fixes along with a couple of new
features. It all went well and the client had planned to set up a day to
film a working pilot episode. I continued to bug fix leading up to the day
till the 2nd of May 3am, the morning of the gig. I went to bed at that time
happy that everything was working fine.

/*
Bear in mind that somewhere in the middle of April 2018, Adobe had also
changed their policy for oAuth which had repercussions on another client’s
software who codes in LC5.0.2 (because he prefers to ‘own’ software rather
than ‘rent’ it). I created a library for him to access Adobe Sign but
failed from 5.0.2 because it only uses TLS1.0 and Adobe require TLS1.1 or
1.2. I was able to fix this with a mini hack of LC5.0.2.
*/


// The Incident //
It turns out, however, that at 00:01 PDT (8am BST I think) of May 2nd
Google changed something key to the App. Due to various security risks,
Google had decided to deprecate the use of webviews for authenticating
oAuth entry. Our app used GoogleSheets as a simple way to enable the client
to update key features of the app live, specifically, questions, categories
and running orders. The App, which would run live and display on the
projected screen in front of the contestants, would call on the GSheet with
updated data through the demo.

From between 8am and 10am UK time when I eventually woke up, the client had
evidently been desperately texting, emailing and trying to call me to let
me know the App wasn’t working anymore. It had been working at first then
suddenly wasn’t. They would only get a screen that said it could no longer
authenticate entry and login to Google services. This, of course, baffled
me as it had all been working fine up to just 7hrs before.

As the desktop version appeared not to be affected (as I had found after a
lot of testing that morning) so I used it to create an up to date database
internally in the app and upload as an enterprise app for them to install.
This gave them the ability to at least start using it although without the
ability to update and change the order of events dynamically using the
Google Sheets method. This was a key part of making it work.


// The Repercussions //
Once I got to the studio it was evident how much this had affected
production. It had all become very clunky with little to no fluidity or
slickness we would have had if it were working properly. The
director/producer was understandably perplexed and irritated. It now meant
that every time an answer was given and a step through the game occurred we
had to rebuild the application with manually updated data and get each
device to download the latest version of the app. The game is usually very
fast paced but this had brought it to a near standstill taking all of the
excitement out of it.

The longer it went on the worse and worse I felt. I had little to no time
to come up with an alternative solution and just needed it fixed. But with
Monte 12hrs away and LiveCode £600-£1000 away with only the likely response
of “Nothing we can do till Monte wakes up”, I knew the likelihood of a fix
was 100% not going to come.

To give an idea of what was affected, an hours show like this would usually
take about 2-3hrs to film. This took them 6-7hrs. Considerations are the
studio 

Re: Signing MacOS Standalones

2018-05-25 Thread Paul Dupuis via use-livecode
I am not sure - the "no identity" seems like you may have not added your
code signing certificate to AppWrapper.

To verify, you have an Apple Developer account. From the Developer
account, you have downloaded a code signing certificate for signing OSX
desktop apps (Apple issues different certificates for signing desktop
app and iOS apps). I'm sorry, but I do not remember the specifc steps to
add your certificate to AppWrapper, but in the past, Ohanaware email
support has been really good. Have you contacted them?


On 5/25/2018 8:40 AM, Ray via use-livecode wrote:
> Paul thanks again for your suggestion here.  I finally got some time
> and a Mac to try this but I ran into problems.  I get a "no identity
> found" error from AppWrapper with no support as to how to find 'my
> identity'.  I did find some information on Stack Overflow at:
>
> https://stackoverflow.com/questions/16036571/codesign-gives-always-no-identity-found-error-via-terminal
>
>
> but it's pretty cryptic and ultimately impossible to follow.  In my
> opinion this whole thing seems like one big extortion scheme on the
> part of Apple Computers.  To the best of my knowledge Microsoft does
> not impose anything like this on Windows developers.  Exasperating
> matters, Apple routinely changes things up thus making it difficult
> for an organization such as Livecode to provide an accurate
> procedure.  Nonetheless, if we can no longer save a standalone for
> MacOS we taken a major step backward, have we not?
>
> Please let me know what your thoughts are on this.
>
> Thanks!
>
> Ray Horsley
>
>
> On 5/19/2018 5:54 PM, Ray via use-livecode wrote:
>> Many thanks Paul - I'll give this a try and post how it works out.
>>
>>
>> On 5/19/2018 1:47 PM, Paul Dupuis via use-livecode wrote:
>>> You will still have to join Apple Developer to purchase a certificate,
>>> but then use AppWrapper (http://www.ohanaware.com/appwrapper/)
>>>
>>> On 5/19/2018 5:19 AM, Ray via use-livecode wrote:
 Does anybody have steps to sign Mac OS standalones?  I've discovered
 Apple 10.12 or higher now sabotages unsigned standalones and it's a
 rather cryptic process to join the Apple dev club, create a
 certificate, and then sign an LC standalone, evidently using Terminal.

 Thanks in advance!

 Ray Horsley

 ___
 use-livecode mailing list
 use-livecode@lists.runrev.com
 Please visit this url to subscribe, unsubscribe and manage your
 subscription preferences:
 http://lists.runrev.com/mailman/listinfo/use-livecode
>>>
>>>
>>> ___
>>> use-livecode mailing list
>>> use-livecode@lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
>>
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Update to SublimeText LiveCode Script linter

2018-05-25 Thread Trevor DeVore via use-livecode
On Fri, May 25, 2018 at 9:58 AM, Mike Kerner via use-livecode <
use-livecode@lists.runrev.com> wrote:

> so far so good here other than the version tag being a commit early...


?

-- 
Trevor DeVore
ScreenSteps
www.screensteps.com
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Update to SublimeText LiveCode Script linter

2018-05-25 Thread Mike Kerner via use-livecode
so far so good here other than the version tag being a commit early...

On Fri, May 25, 2018 at 10:51 AM Trevor DeVore via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Hi,
>
> The LiveCode Script linter for SublimeText has been updated. The update
> includes fixes required in order to work with the latest SublimeLinter. It
> also fixes an issue that would keep the linter from working if you
> installed from Package Control. Instructions on installing the linter can
> be found on GitHub:
>
> https://github.com/trevordevore/sublimelinter-contrib-livecodelint
>
> --
> Trevor DeVore
> ScreenSteps
> www.screensteps.com
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>


-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Update to SublimeText LiveCode Script linter

2018-05-25 Thread Trevor DeVore via use-livecode
Hi,

The LiveCode Script linter for SublimeText has been updated. The update
includes fixes required in order to work with the latest SublimeLinter. It
also fixes an issue that would keep the linter from working if you
installed from Package Control. Instructions on installing the linter can
be found on GitHub:

https://github.com/trevordevore/sublimelinter-contrib-livecodelint

-- 
Trevor DeVore
ScreenSteps
www.screensteps.com
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Signing MacOS Standalones

2018-05-25 Thread Ray via use-livecode
Paul thanks again for your suggestion here.  I finally got some time and 
a Mac to try this but I ran into problems.  I get a "no identity found" 
error from AppWrapper with no support as to how to find 'my identity'.  
I did find some information on Stack Overflow at:


https://stackoverflow.com/questions/16036571/codesign-gives-always-no-identity-found-error-via-terminal

but it's pretty cryptic and ultimately impossible to follow.  In my 
opinion this whole thing seems like one big extortion scheme on the part 
of Apple Computers.  To the best of my knowledge Microsoft does not 
impose anything like this on Windows developers.  Exasperating matters, 
Apple routinely changes things up thus making it difficult for an 
organization such as Livecode to provide an accurate procedure.  
Nonetheless, if we can no longer save a standalone for MacOS we taken a 
major step backward, have we not?


Please let me know what your thoughts are on this.

Thanks!

Ray Horsley


On 5/19/2018 5:54 PM, Ray via use-livecode wrote:

Many thanks Paul - I'll give this a try and post how it works out.


On 5/19/2018 1:47 PM, Paul Dupuis via use-livecode wrote:

You will still have to join Apple Developer to purchase a certificate,
but then use AppWrapper (http://www.ohanaware.com/appwrapper/)

On 5/19/2018 5:19 AM, Ray via use-livecode wrote:

Does anybody have steps to sign Mac OS standalones?  I've discovered
Apple 10.12 or higher now sabotages unsigned standalones and it's a
rather cryptic process to join the Apple dev club, create a
certificate, and then sign an LC standalone, evidently using Terminal.

Thanks in advance!

Ray Horsley

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode