> Am 12.03.2020 um 01:08 schrieb Sean Cole (Pi) via use-livecode
> :
>
> Tired and ill. My business is constantly lagging behind my competitors
> because we're always on the backfoot waiting for LC to frikin' work! I'm
> going to end up losing all my new customers again since the last LC epic
>
On 2020-03-11 22:36, Richard Gaskin via use-livecode wrote:
Querying the fontNames includes:
(Default)
(Styled Text)
(Menu)
(Text)
(Message)
(Tooltip)
(System)
These are not font names, but constants the engine accepts so that we
can have good-looking, HIG-savvy UIs on multiple platforms.
But
On 2020-03-11 23:38, Paul Dupuis via use-livecode wrote:
I filled a bug report on this back in February:
https://quality.livecode.com/show_bug.cgi?id=22564
Mark Waddingham declared it was not a bug but a documentation issue,
so I filed and enhancement request:
On 3/12/2020 3:46 AM, Mark Waddingham via use-livecode wrote:
On 2020-03-11 23:38, Paul Dupuis via use-livecode wrote:
I filled a bug report on this back in February:
https://quality.livecode.com/show_bug.cgi?id=22564
Mark Waddingham declared it was not a bug but a documentation issue,
so I
> Am 12.03.2020 um 17:08 schrieb hh via use-livecode
> :
>
> Some people are very angry about deficiencies of LC, what I can understand
> from
> their view, and *we should hear what they have to say*.
>
Why. Posting here won´t change anything.
> Especially when they get angry about the
Hi Mark,
> Am 12.03.2020 um 17:47 schrieb Mark Waddingham via use-livecode
> :
> ...
> A couple of weeks ago (or maybe longer?)
yep, about four weeks ago.
> Klaus noticed a really strange problem with text extraction from a PDF
> printed using LiveCode on macOS - specifically digits did not
J. Landman Gay wrote:
> I wonder if the crashes are a problem with a different OS (I'm
> on Mac,) or something about your stack. I haven't had any debugging
> crashes since the fix was implemented.
...
> I know typing can be very slow on Windows but it
> isn't bad on Mac.
I had an confounding
On 3/12/2020 12:22 PM, hh via use-livecode wrote:
Indeed, the current implementation of
(Default),(Menu),(Message),(Styled Text),(System),(Text),(Tooltip)
is not very useful.
For example (System) at size 13 on MacOS 10.15 is on Windows 10
at about (System) at size 12. So one needs nevertheless
> > hh wrote:
> > Some people are very angry about deficiencies of LC, what I can understand
> > from
> > their view, and *we should hear what they have to say*.
>
> Matthias wrote:
> Why. Posting here won´t change anything.
The uselist is not a LC-praising list. As long as we have the freedom
> > hh wrote:
> > The uselist is not a LC-praising list. As long as we have the freedom of
> > speech everybody can say whether he is contented with LC or not.
>
> Bob S. wrote:
> I was not aware we had such freedoms on this list! For instance, if I begin
> to speak of fermented dairy products, I
hh wrote:
>> Bob S. wrote:
>> I was not aware we had such freedoms on this list! For instance, if I
>> begin to speak of fermented dairy products, I will certainly be
>> censured!
>> And well I should be!!!
>
> I wonder why you want to speak of fermented dairy products in order to
> express
I also see the red dot misalignment (still using 9.5.1 rc 1). Since I use LC
virtually every day to make changes and fixes to the app we use, I cannot
really participate in DP's.
Bob S
> On Mar 12, 2020, at 11:17 , J. Landman Gay via use-livecode
> wrote:
>
> On 3/11/20 9:50 PM, Sean Cole
Paul Dupuis wrote:
> I *do* find that cross-platform UI design and implementation to still
> be the hardest thing to do in LiveCode (on a relative scale of course,
> since LiveCode overall is easy)
>
> I would just like to be able to say in a preferences box for my app
> that I am deploying to
On 3/11/20 9:50 PM, Sean Cole (Pi) via use-livecode wrote:
9.5.1 and 9.6 dp2 are still exhibiting breakpoint crashes. Not
as often as before but, still, there are occurrences. And for some very odd
reason an early sign it's going to become a problem I notice the line
numbers don't scroll with
LC = Less Cheese ;-)
Rick
> On Mar 12, 2020, at 2:16 PM, Richard Gaskin via use-livecode
> wrote:
>
> It went on for so many days Heather eventually stepped in and kindly asked us
> to please stop the cheese conversation so those interested in LiveCode could
> have more LC and less cheese
As to my contentedness with LC, let me say that without LC, my options would be
Javascript, Python or a host of other script based languages, or else some
variant of C. That is to say I would be out of options because I simply am too
lazy and otherwise occupied with my real job to justify the
On 2020-03-12 15:53, Paul Dupuis via use-livecode wrote:
So here is the simple use-case I ran into. We have a field with an
editor toolbar for rich content editing in an app. The field is set to
(Text) upon start up, as in:
set the textFont of fld "X" to "(Text)"
So that the font is initially
I was not aware we had such freedoms on this list! For instance, if I begin to
speak of fermented dairy products, I will certainly be censured! And well I
should be!!!
Also, and seriously, Freedom of Speech is something that is unique to a handful
of cultures. It is by no means global.
Bob
Bob Sneidar wrote:
> I was not aware we had such freedoms on this list! For instance, if I
> begin to speak of fermented dairy products, I will certainly be
> censured! And well I should be!!!
>
> Also, and seriously, Freedom of Speech is something that is unique to
> a handful of cultures. It
Sean Cole wrote:
> On Thu, 12 Mar 2020 at 00:17, Richard Gaskin via use-livecode <
> use-livecode at lists.runrev.com> wrote:
>
>> I had thought the problem at that time was that your app was using
>> Google's older auth method, before they switched to OAth2.
>
> Correct. But not the oAuth Lib
On 3/12/2020 12:47 PM, Mark Waddingham via use-livecode wrote:
On 2020-03-12 15:53, Paul Dupuis via use-livecode wrote:
So here is the simple use-case I ran into. We have a field with an
editor toolbar for rich content editing in an app. The field is set to
(Text) upon start up, as in:
set the
+10
> On Mar 12, 2020, at 09:41 , matthias rebbe via use-livecode
> wrote:
>
> Posting here about a real problem/bug makes sense, because others might jump
> in and confirm the same experience or might help to solve the problem
> As always, a good recipe, if possible, makes it even easier to
Another approach might be to find a font or subset of fonts that looks the same
on all platforms and use that. You may have to pay for the font(s) but you gain
consistency.
Bob S
> On Mar 12, 2020, at 10:23 , Paul Dupuis via use-livecode
> wrote:
>
> Yes, it does. Lacking a detailed
monte has previously said that merggoogle is using a c-library.
the "need" for merggoogle is to not rewrite the existing code and/or write
a new library from scratch. otherwise i wouldn't need to issue an rfq to
have someone write a library. i could have it done for free.
or i would be overrun
On 3/12/20 12:39 PM, hh via use-livecode wrote:
The uselist is not a LC-praising list. As long as we have the freedom of speech
everybody can say whether he is contented with LC or not. And nothing written
does
change anything*with LC*, also not your positive-only (and excellent) posts ...
Some people are very angry about deficiencies of LC, what I can understand from
their view, and *we should hear what they have to say*.
Especially when they get angry about the whitewashing of bugs by some list
members.
What's wrong that's wrong, no matter who tries to whitewash bugs or even
Indeed, the current implementation of
(Default),(Menu),(Message),(Styled Text),(System),(Text),(Tooltip)
is not very useful.
For example (System) at size 13 on MacOS 10.15 is on Windows 10
at about (System) at size 12. So one needs nevertheless a platform
switch.
Thanks for chiming in, Mark. Would it be helpful to have a bug report
on this, or should I wait to see what you find in your code review?
--
Richard Gaskin
Fourth World Systems
Mark Waddingham wrote:
On 2020-03-11 22:36, Richard Gaskin via use-livecode wrote:
Querying the fontNames
see the rfq i posted. there are a variety of issues in merggoogle
1. mac/ios only
2. doesn't seem to work in newer versions of lc for some reason (works in
9.0.1, for instance, but not in 9.5.x)
3. google is going to shut off...something...that merggoogle is using in
september. i don't know what
Mike Kerner wrote:
> 6. there doesn't seem to be any interest in updating merggoogle.
It'll be good to hear from Monte on this, but I'd guess the reason
merGoogle isn't actively supported is because the meat of it is handling
authentication, and the REST API itself if pretty straightforward.
i'm kind-of annoyed. i have spent enough of my company's funds and my
personal time doing lc sessions for beginners. the two years before the lc
global sessions, we had a similar level of communication from hq as we do
now.
there is a difference between complaining and flameing
badgering over
Well said, Jacqueline!
Bill
William A. Prothero
Santa Barbara, CA. 93105
http://earthlearningsolutions.org/
> On Mar 12, 2020, at 11:58 AM, J. Landman Gay via use-livecode
> wrote:
>
> On 3/12/20 12:39 PM, hh via use-livecode wrote:
>> The uselist is not a LC-praising list. As long as we have
On 3/12/2020 3:24 PM, Richard Gaskin via use-livecode wrote:
With more substantial content (web authoring, printed materials, etc.)
the user cares very much, and the likelihood of ever wanting the
OS-specific default font is low, so assigning your own default font
explicitly would work well
On 2020-03-12 17:23, Paul Dupuis via use-livecode wrote:
Yes, it does. Lacking a detailed technical understanding of the
ridiculous complexity of the macOS (or Windows for that matter), is
one reason we used/use HyperCard, SuperCard, MetaCard, Revolution,
LiveCode for the past 25+ years for our
it really has been, by multiple people, over multiple years. i'm not going
to repeat myself, or them.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
interesting. i didn't realize the oauth routines were in an lcs library.
it's only 423 lines, and a lot of that is documentation.
On Thu, Mar 12, 2020 at 4:08 PM Ralph DiMola via use-livecode <
use-livecode@lists.runrev.com> wrote:
> I have another type of slowdown on Win 10 that I can't get an
Mike Kerner wrote:
> there is a difference between complaining and flameing
> badgering over the status of qr's shouldn't be necessary. badgering
> over comms shouldn't be necessary.
Agreed, but there have been two posts with abstractions about
"communications" and neither has expressed what
I have another type of slowdown on Win 10 that I can't get an exact recipe
for because it doesn't happen every time. Open up the stack and everything
is fast then open up the SE make some changes (no testing breakpoints used)
and the card renders and then LC hangs for 10 to 40 seconds(not
> Richard G. wrote at Mike K.:
> The rest of us are having conversations with none other than the lead
> engineer, right here on this list this morning.
Yes the CTO was in the last two weeks probably more often here than in the
last two years before that two weeks. But he's now more often
> Matthias wrote:
> I did NOT refer to any personal problems. So please do not impute
> such an intention to me.
Sorry Matthias, I obviously misinterpreted "your problems last year".
Hopefully Sean Cole didn't also misinterpret this.
___
use-livecode
> Am 13.03.2020 um 00:09 schrieb hh via use-livecode
> :
>
>> Matthias wrote:
>> I did NOT refer to any personal problems. So please do not impute
>> such an intention to me.
>
> Sorry Matthias, I obviously misinterpreted "your problems last year".
> Hopefully Sean Cole didn't also
Not just dropped APIs.
It starts already with Apple deciding if the functionality of an iOS App is
worth to be approved for the Appstore or not.
I had created 3 apps for a customer which were not accepted by Apple by the
"lack" of functionality. At least that was the reason they told us,
Hi all
Thank you for all your kind words. Sorry, you said ‘no’ sarcasm. Oops. My bad.
I had posted this originally to the dev-livecode list but I thought
(accurately) I wouldn’t get a reponse from that. I’m sooo sorry (oops, I did it
again) that this is viewed potentially by newbies. Although
No offence taken at all, Matthias. I felt you hit ‘the nail’ on the head, not
me. ;)
I do regret bringing up my last ‘incident’ at all. It’s a bit of a splinter
that just won’t go away for me and hard not to be reminded of far to often when
I face the near same issues of failure I did back
Pi Digital wrote:
> I had posted this originally to the dev-livecode list but I thought
> (accurately) I wouldn’t get a reponse from that.
Yep, the dev list has been more or less retired since LC went open
source. I'm not sure why it's still even up, except that a few people
wanted it when
> Am 12.03.2020 um 23:15 schrieb hh via use-livecode
> :
>
>
> What I woud like to see is that Sean Cole(pi digital) can write here his
> opinion without being attacked just for writing that: No content-based
> attack, but using the most nasty kind of attack, using (supposed) personal
>
I hesitate to opine, but there's so much here. I think anytime a product is
dependent on a Google API, long term support is uncertain. For example,
recently Google dropped support for Google Docs. The copier companies have
written plugins to their copiers SPECIFICALLY to work with Google Docs.
This one was okay. :) You sound a little more relaxed.
I frequently have the same frustrations as you do, but knowing a little
about the team helps moderate my posts. I think this long thread could have
been shorter if you had just said what roadblocks in particular are
preventing you from
The clue is in the subject heading, Jacque. At least, I thought it was plain
enough. The script editor and HTML issues I mentioned were just ‘mind wind’ in
the process of bemoaning the speed of uptake to current OS and Xcode support.
Here’s the big issue. Essential updates that all users are
Sean Cole wrote:
> I've added updates to this bug relating to the script editor issues
> and crashes
>
> https://quality.livecode.com/show_bug.cgi?id=22389
Thank you, Sean. I'm signed onto the report, and will add any notes I
can if I see this on my Mac.
--
Richard Gaskin
Fourth World
On 3/12/20 9:12 PM, Sean Cole (Pi) via use-livecode wrote:
I was able to reproduce the issue (continually) so I did another screen
recording. It's either the auto-type suggestion thing or it's the error
bullet it puts on the numbers (which would then tie up with the breakpoint
and other SE
I've added updates to this bug relating to the script editor issues and
crashes
https://quality.livecode.com/show_bug.cgi?id=22389
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage
I see now. I confess that I stopped reading the subject itself after a
while when the thread took off on a tangent. You make a valid point. LC
actually did what you describe when 64-bit started to be required on OS X.
They released a rapid update and made the deadline but it was close. I
heard
I was able to reproduce the issue (continually) so I did another screen
recording. It's either the auto-type suggestion thing or it's the error
bullet it puts on the numbers (which would then tie up with the breakpoint
and other SE errors). Interesting!
Sean
On Fri, 13 Mar 2020 at 03:47, Sean
54 matches
Mail list logo
