No matter what you think of the Free Software Foundation, happy Software
Freedom Day.
http://www.softwarefreedomday.org/
--
Mark Wieder
ahsoftw...@gmail.com
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to
On Sat, Sep 19, 2015 at 3:23 PM, Brahmanathaswami wrote:
> splashScreenEngine --> Mainstack
>
> model, so that your substacks can all save data...what about setting a
> customProp with a time stamp in the stack when data changes?
>
My mainstack stays hidden, and launches
After reading the announcements, I am looking forward to the LiveCode 8 Global
Jam and helping to prepare LiveCode 8 for release through reporting bugs.
As I’ve already reported a handful of bugs relating to LiveCode 8, I thought
I’d take a look and see how many LiveCode 8 bugs there are in
> On 9/19/15, 1:59, R.H. wrote:
> > Why not there is a field that can easily be set to display
> > international date and time formats and automatically would default to
> > local standards without having to script a lot and redoing the same
> > work over and over again? Why not a field can be
As always, thank you Michael!
SKIP KIMPEL
On Fri, Sep 18, 2015 at 10:49 AM, Michael Doub wrote:
> I made some adjustments to take into account the new reserved words of 7.1
> and 8.0. You can find the current version here:
>
>
Thanks Roland for the email. What you have described was exactly what Visual
Basic programmers were saying in the early 90s. The solution to the VB problem
was the ability to create COM objects.
What you described as your primary frustrations will evaporate with LC8. You
will be able to
No one answered your question. I have noticed there are differences in the
way you ping an address when on windows or when on mac or unix. Livencode
has a nice hostAddressToName("127.0.0.1") and
hostNameToAddress(*domainName, [callback]*)
Write something to ping it first before connecting too.
Assuming you follow the
splashScreenEngine --> Mainstack
model, so that your substacks can all save data...what about setting a
customProp with a time stamp in the stack when data changes?
Then you just track
repeat for with z = 1 ot the number of substacks
# do stuff here with the
# the
Is there a practical way to automatically track the change dates for
substacks?
I'm about to end up with something like 100 of them (one for each judicial
district)
At the moment, I have routines that step through all of my cards every time
I bump the revision, but it would be nice to be able to