Change to the label property in 6.7

Peter Haworth pete at lcsql.com
Sat Mar 29 21:23:04 EDT 2014


No reminder necessary and one of the reasons I look at dp releases is
exactly what you said, to find things that aren't compatible with my code
and probably other peoples' code too. And yes, it bothers me but that's not
a reason to not test things.  I'm simply stating my opinion about a change
that I had no idea was coming.  I don't disagree with the concept as I said
but I also don't believe its worth breaking backward compatibility to fix
it.

I've already filed a bug on the issue of what happens to the menuHistory
when the label is set to a non-existent value. Hopefully that won't raise
too many other hackles.


Pete
lcSQL Software <http://www.lcsql.com>
Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>


On Sat, Mar 29, 2014 at 5:25 PM, Mark Wieder <mwieder at ahsoftware.net> wrote:

> Pete-
>
> Saturday, March 29, 2014, 4:37:49 PM, you wrote:
>
> > I have to admit that I'm really concerned with the increasing frequency
> of
> > changes that are being made to the behavior of various entities without
> > regard to backwards compatibility.
>
> Do you really need to be reminded that dp builds are released into the
> wild for exactly that purpose? Isn't the reason you're looking at dp1
> to find out if your code is compatible? If this is going to bother you
> then I suggest you wait for actual released code and leave the
> thrashing out of bugs to someone else. I'd rather you didn't do that,
> though, because you seem to be good at finding these edge cases early
> on, which means that they can be fixed and won't be present in later
> releases.
>
> --
> -Mark Wieder
>  ahsoftware at gmail.com
>
> This communication may be unlawfully collected and stored by the National
> Security Agency (NSA) in secret. The parties to this email do not
> consent to the retrieving or storing of this communication and any
> related metadata, as well as printing, copying, re-transmitting,
> disseminating, or otherwise using it. If you believe you have received
> this communication in error, please delete it immediately.
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



More information about the use-livecode mailing list