> On 22 Aug 2017, at 2:58 pm, Brian Milby via use-livecode
> wrote:
>
>
> I think there may be a strategy to avoid a large part of the ID collision
> issue.Wouldn't need full on UUIDs, just assign a range to each developer
> working the UI.Upon import
I think there may be a strategy to avoid a large part of the ID collision
issue.Wouldn't need full on UUIDs, just assign a range to each developer
working the UI.Upon import they could even be collapsed down to the natural
order range or left as is.It would require the
The real interesting thing is now for me how to lock the screen
in LC Builder? I couldn't find a way to do that. Who knows?
This interacts with LC Script, timed widgets (clocks, animations)
want their own screen updates ...
___
use-livecode mailing
On 08/21/2017 10:28 AM, Mark Waddingham via use-livecode wrote:
On 2017-08-19 04:41, J. Landman Gay via use-livecode wrote:
Except when it doesn't. There seems to be an override in the lock
count if any unlock uses a visual effect. I'm not sure if that's on
purpose or not.
Internally there is
On 8/21/17 5:47 PM, prothero--- via use-livecode wrote:
I didn't realize that the lockscreen command only applied to the handler that
sets it.
No, it doesn't (or shouldn't) apply only to the handler that sets it.
Does this mean that each script has to set lockscreen if it needs it?
It's a
This exactly. Globally on or globally off. Just unlock and lock again to update.
It is moot, but I would prefer it.
Sent from my iPhone
> On Aug 21, 2017, at 6:47 PM, prothero--- via use-livecode
> wrote:
>
> I didn't realize that the lockscreen command only
On 8/21/17 4:38 PM, Monte Goulding via use-livecode wrote:
On 22 Aug 2017, at 1:41 am, J. Landman Gay via use-livecode
wrote:
Monte's external works great on newer Android devices but seems to crash on
older ones. That's why I had to replace it with a hacked
I didn't realize that the lockscreen command only applied to the handler that
sets it.
Does this mean that each script has to set lockscreen if it needs it? If
lockscreen was either globally true or not, you could do:
On doscreenstuff1
Set lockscreen to true
Handler1
Handler2
> On 22 Aug 2017, at 3:17 am, Mark Waddingham via use-livecode
> wrote:
>
> work stopped on it when we reached a dead end with the dVCS 'stack dir' idea
> - based on ideas Monte developed in lcVCS.
I can’t recall getting an explanation of what the dead end was
> On 22 Aug 2017, at 1:41 am, J. Landman Gay via use-livecode
> wrote:
>
> Monte's external works great on newer Android devices but seems to crash on
> older ones. That's why I had to replace it with a hacked up fake in my
> Android object library. There's a
On 08/21/2017 12:54 PM, J. Landman Gay via use-livecode wrote:
# do different things based on calling context.
That's exactly the opposite of what behaviors are for.
I'm not sure I follow the underlying reasoning here
Thank you. That was my reaction as well.
B- what problem are you
On 8/21/17 2:53 PM, Jonathan Lynch via use-livecode wrote:
I just watched the eclipse where I live, while debating flat earth believers
online. Some irony there, I suppose.
I watched it too, dropped everything to do it. Amazing. We didn't get
totality here but it was about 80%.
I read
I don't understand quite what you're trying to do. If this is a
behavior, the calling context is "me" or the "long name of me", isn't
it? Also, why store it? It's always there.
I'm likely missing something.
On 8/21/17 1:35 PM, Sannyasin Brahmanathaswami via use-livecode wrote:
Back at it
I just watched the eclipse where I live, while debating flat earth believers
online. Some irony there, I suppose.
It reminded me of the time another programmer told me LiveCode was a toy. Years
later when asked by management to duplicate the functions of an app I created
so that those
On 8/21/17 1:28 PM, Jonathan Lynch via use-livecode wrote:
I agree with Bill. If you lock a door twice on a car, it is still just locked.
One unlock will open it up. That seems more intuitive.
Initially it's more intuitive, but if it were done this way you couldn't
have handlers that manage
Back at it here with attempst to make "generic" behaviors as text only stacks
that can serve as slaves "all over the place"
So this is all about the calling context/target.
I wonder If I am working too hard here, may be useful to have the calling
context ready for a dispatch, to parse the
I agree with Bill. If you lock a door twice on a car, it is still just locked.
One unlock will open it up. That seems more intuitive.
Sent from my iPhone
> On Aug 21, 2017, at 2:19 PM, prothero--- via use-livecode
> wrote:
>
> Seems like it would be much
Seems like it would be much simpler if lockscreen just kept the screen locked
until unlockscreen was invoked, but there was an update screen command when
forced updates were needed. No counters to keep track of.
Best
Bill
William Prothero
http://ed.earthednet.org
> On Aug 21, 2017, at 10:40
I used to have an example, I struggled with the problem until I figured out
the reason, and then I modified the script to work around it. It actually
didn't happen in the IDE, only on Android. (I didn't test on iOS.) Now I
can't remember what the original problem script was. But I'll see if I
Yes, they're easy to implement, but they don't match the specs for any
modern OS and they're very old school. If you want native appearance they
are inappropriate.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
I would have to recreate it as my production stack has already been gone
through, and it seems to be working as advertised, which would argue against it
being an engine issue. I'll see if I can create a sample stack in the next
couple days. Right now I have a couple service calls to go out on
On 2017-08-19 04:41, J. Landman Gay via use-livecode wrote:
Except when it doesn't. There seems to be an override in the lock
count if any unlock uses a visual effect. I'm not sure if that's on
purpose or not.
Internally there is a counter - and only one - the engine uses it too
when it needs
On 2017-08-21 17:41, J. Landman Gay via use-livecode wrote:
Monte's external works great on newer Android devices but seems to
crash on older ones. That's why I had to replace it with a hacked up
fake in my Android object library. There's a pull request in git for a
native toast that is waiting
On 2017-08-21 19:13, Jonathan Lynch via use-livecode wrote:
It is on iOS. Turning it on and off as needed has worked perfectly, so
it is no problem. Thanks for explaining!
Okay - so obviously it hasn't 'got any better' since iOS4 which was when
we added acceleratedRendering mode... This is
On 2017-08-21 18:09, Brian Milby via use-livecode wrote:
What about something like
import into [objectRef] from array [arrayRef]
OR
update [objectRef] from array [arrayRef]
where the array would be in the format of the export and the object
would
be an existing object.
There are a
It is on iOS. Turning it on and off as needed has worked perfectly, so it is no
problem. Thanks for explaining!
Sent from my iPhone
> On Aug 21, 2017, at 12:54 PM, Mark Waddingham via use-livecode
> wrote:
>
>> On 2017-08-21 18:51, Jonathan Lynch via
On 2017-08-21 18:51, Jonathan Lynch via use-livecode wrote:
Hi Bob- I can report that accelerated rendering "steals" resources
from the browser widget. I have to turn it off when displaying a 3D
map in the browser widget, then turn it back on for scrolling groups.
Otherwise, the map renders in a
On 2017-08-21 18:41, Bob Sneidar via use-livecode wrote:
Hi all.
Since acceleratedRendering is a stack property, does it only apply to
a given stack, and not, for example to a sub stack? What would the
advantage be of having it off? If none, why even have it?
It is per stack, and not
Hi Bob- I can report that accelerated rendering "steals" resources from the
browser widget. I have to turn it off when displaying a 3D map in the browser
widget, then turn it back on for scrolling groups. Otherwise, the map renders
in a very clunky way, with large sections very distorted.
It
I meant to say, why not just have it on permanently?
Bob S
> On Aug 21, 2017, at 09:41 , Bob Sneidar via use-livecode
> wrote:
>
> Hi all.
>
> Since acceleratedRendering is a stack property, does it only apply to a given
> stack, and not, for example to a
Hi all.
Since acceleratedRendering is a stack property, does it only apply to a given
stack, and not, for example to a sub stack? What would the advantage be of
having it off? If none, why even have it?
Bob S
___
use-livecode mailing list
I like the dialogs on iOS. Simple, not offensive, clean.
Sent from my iPhone
> On Aug 21, 2017, at 12:32 PM, Bob Sneidar via use-livecode
> wrote:
>
> Awww! Take it back! I use em all the time. Someone clicks the delete button,
> I ask them if they are sure
I was hoping for a command that left the screen lock set but forced an update
of the screen. That way I wouldn't have to unlock/relock and depend on there
only being one screen lock pending.
Bob S
> On Aug 21, 2017, at 08:51 , J. Landman Gay via use-livecode
>
Awww! Take it back! I use em all the time. Someone clicks the delete button, I
ask them if they are sure that is what they want to do.
Bob S
> On Aug 21, 2017, at 08:41 , J. Landman Gay via use-livecode
> wrote:
>
> Answer dialogs aren't appropriate for any
What about something like
import into [objectRef] from array [arrayRef]
OR
update [objectRef] from array [arrayRef]
where the array would be in the format of the export and the object would
be an existing object.
I've been looking at the code and think that it would be straightforward to
I was unaware of that too. It doesn't sound right.
On August 21, 2017 10:10:27 AM Bob Sneidar via use-livecode
wrote:
Yup. My troubles came when I had a handler unlock the screen 5 times
straight and I do not lock the screen to that many levels. It still did
Monte's external works great on newer Android devices but seems to crash on
older ones. That's why I had to replace it with a hacked up fake in my
Android object library. There's a pull request in git for a native toast
that is waiting for review and as soon as it's available I will switch to
Hello,
I wanted to migrate my domain from http to https, but I fail with my
Livecode programs, which communicate with some php programs in one directory
on my domain (see my previous post).
Since I am not able to combine the rewrite htaccess in my domain root with
an authentication htaccess in
Hi Bob - just an idea for a progress indicator - you could advance a progress
indicator through a browser widget. This would work even when the screen is
locked, allowing you to show progress while not having unlock and lock each
time.
The widget requires a fair bit of overhead, so that might
Yup. My troubles came when I had a handler unlock the screen 5 times straight
and I do not lock the screen to that many levels. It still did no unlock the
screen, so now it may be that one handler cannot unlock another handler's lock
screen, which I was unaware of.
Bob S
> On Aug 18, 2017,
I used the rewrite conditions to https from Matthias in the root of my
domain and build a new LC 8.1.5 standalone including the revsecurity.dll.
like Tom pointed out, but I still get an error.
The return value of my php is surprisingly some garbage html code instead of
my php return value and "the
If you get chartonum for these characters, are they also different?
Sent from my iPhone
> On Aug 21, 2017, at 9:01 AM, jonathandly...@gmail.com wrote:
>
> Pressing the key harder makes a difference? How could that not be a hardware
> thing?
>
> Sent from my iPhone
>
>> On Aug 21, 2017, at
On 2017-08-21 14:55, Jonathan Lynch via use-livecode wrote:
This mislayering is with browser widgets that are grouped into
different groups. Would that make a difference?
Quite possibly! The engine does extra work to handle grouped widgets
which use a native layer (it has to synthesize the
Pressing the key harder makes a difference? How could that not be a hardware
thing?
Sent from my iPhone
> On Aug 21, 2017, at 7:39 AM, Tiemo Hollmann TB via use-livecode
> wrote:
>
> Hi, have you ever experienced the following phenomenon?
>
> A customer of me
This mislayering is with browser widgets that are grouped into different
groups. Would that make a difference?
Sent from my iPhone
> On Aug 21, 2017, at 8:24 AM, Mark Waddingham via use-livecode
> wrote:
>
>> On 2017-08-21 03:53, Jonathan Lynch via use-livecode
On 2017-08-21 03:53, Jonathan Lynch via use-livecode wrote:
I have been using "answer", "ask", and the mobile picker because they
appear on top. However, these system dialogs are not always pretty,
especially on Android. Is there another option? I tried using a
browser widget, but that does not
Does the browser -need- to be visible during the message? If not, hide it
first. If so, display a temp screenshot of it during your message.
~Roger
On Aug 20, 2017 9:53 PM, "Jonathan Lynch via use-livecode" <
use-livecode@lists.runrev.com> wrote:
What is the best way to send a message to
Hi, have you ever experienced the following phenomenon?
A customer of me tells me that pressing a Umlaut key (äüö) on a German
keyboard sometimes shows the correct Umlaut in my LiveCode program, but
sometimes only hieroglyphs. Sometimes the correct char shows up after having
hit multiple times /
Thanks Mark
Sent from my iPhone
> On Aug 21, 2017, at 6:38 AM, Mark Waddingham via use-livecode
> wrote:
>
>> On 2017-08-21 02:25, Jonathan Lynch via use-livecode wrote:
>> LC gives us multiple ways to connect to online databases. Is TSnet
>> always the best
I will check that out - thanks Dave
Sent from my iPhone
> On Aug 21, 2017, at 5:18 AM, Dave Kilroy via use-livecode
> wrote:
>
>
> Jonathan - how about a toast? (on Android that is), I haven’t tested it but I
> would assume it would appear above a browser…
>
On 2017-08-21 02:25, Jonathan Lynch via use-livecode wrote:
LC gives us multiple ways to connect to online databases. Is TSnet
always the best performing method?
Generally if you are accessing databases over the internet then fronting
them with an HTTP-based gateway is by far the 'best'
On 2017-08-21 12:06, Monte Goulding via use-livecode wrote:
On 21 Aug 2017, at 7:58 pm, Mark Waddingham via use-livecode
wrote:
I think its been suggested before that a 'loadStack' message might be
quite useful (perhaps it should be 'createStack' - we have
> On 21 Aug 2017, at 7:58 pm, Mark Waddingham via use-livecode
> wrote:
>
> I think its been suggested before that a 'loadStack' message might be quite
> useful (perhaps it should be 'createStack' - we have 'deleteStack' which is
> probably sufficient for the
On 2017-08-21 01:31, Monte Goulding via use-livecode wrote:
Right now you need to handle preOpenStack in stack A and setup the
hierarchy because stack B does not retain the behavior property when
saved and does not get any kind of message when used as a behavior. It
may actually be a good idea
Jonathan - how about a toast? (on Android that is), I haven’t tested it but I
would assume it would appear above a browser…
Monte did an external some time ago (mergAndroid I think) that I’m pretty sure
included support for toasting :)
Kind regards
Dave
55 matches
Mail list logo