Re: [OT][[TL/DR] 6.6 RC2 Release

[Richmond]

On 22/03/14 19:15, PystCat wrote:

Cheese..?  A nice extra sharp cheddar.


A good chunk of Stilton or French blue.




On Mar 22, 2014, at 12:16 PM, "Peter M. Brigham"  wrote:

Our daughter brews a really fine chocolate porter. (No actual chocolate in the 
brew, it's just what it's called.) She and her husband brewed the beer for 
their wedding last year.

This is wandering far afield now. But at least I didn't mention "cheese."   :-)

-- Peter

Peter M. Brigham
pmb...@gmail.com
http://home.comcast.net/~pmbrig


On Mar 22, 2014, at 11:56 AM, Richmond wrote:


On 22/03/14 17:51, Dr. Hawkins wrote:

On Fri, Mar 21, 2014 at 7:49 PM, PystCat  wrote:

One of my two favorite beers... Any ice cold Belgian beer and Guiness.
Nothing else will do.

American Pale Ale, or IPA.  Most of what I brew is dry stout or pale ale.

"Kozel" (= goat), a fairly low alcohol dark beer from the Czech Republic.

"Stolichnaya", a heavy dark stout brewed in Stara Zagora, Bulgaria.

"Sweet Heart Stout", a fairly low alcohol sweet stout brewed in Scotland.

"Samuel Adams" Dark: a stout brewed in Boston, Mass.

___
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: [OT][[TL/DR] 6.6 RC2 Release

[PystCat]

Cheese..?  A nice extra sharp cheddar.

> On Mar 22, 2014, at 12:16 PM, "Peter M. Brigham"  wrote:
> 
> Our daughter brews a really fine chocolate porter. (No actual chocolate in 
> the brew, it's just what it's called.) She and her husband brewed the beer 
> for their wedding last year.
> 
> This is wandering far afield now. But at least I didn't mention "cheese."   
> :-)
> 
> -- Peter
> 
> Peter M. Brigham
> pmb...@gmail.com
> http://home.comcast.net/~pmbrig
> 
>> On Mar 22, 2014, at 11:56 AM, Richmond wrote:
>> 
>>> On 22/03/14 17:51, Dr. Hawkins wrote:
 On Fri, Mar 21, 2014 at 7:49 PM, PystCat  wrote:
 
 One of my two favorite beers... Any ice cold Belgian beer and Guiness.
 Nothing else will do.
>>> American Pale Ale, or IPA.  Most of what I brew is dry stout or pale ale.
>> 
>> "Kozel" (= goat), a fairly low alcohol dark beer from the Czech Republic.
>> 
>> "Stolichnaya", a heavy dark stout brewed in Stara Zagora, Bulgaria.
>> 
>> "Sweet Heart Stout", a fairly low alcohol sweet stout brewed in Scotland.
>> 
>> "Samuel Adams" Dark: a stout brewed in Boston, Mass.
> 
> ___
> 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: [OT][[TL/DR] 6.6 RC2 Release

[Peter M. Brigham]

Our daughter brews a really fine chocolate porter. (No actual chocolate in the 
brew, it's just what it's called.) She and her husband brewed the beer for 
their wedding last year.

This is wandering far afield now. But at least I didn't mention "cheese."   :-)

-- Peter

Peter M. Brigham
pmb...@gmail.com
http://home.comcast.net/~pmbrig

On Mar 22, 2014, at 11:56 AM, Richmond wrote:

> On 22/03/14 17:51, Dr. Hawkins wrote:
>> On Fri, Mar 21, 2014 at 7:49 PM, PystCat  wrote:
>> 
>>> One of my two favorite beers... Any ice cold Belgian beer and Guiness.
>>>  Nothing else will do.
>>> 
>> American Pale Ale, or IPA.  Most of what I brew is dry stout or pale ale.
>> 
>> 
> 
> "Kozel" (= goat), a fairly low alcohol dark beer from the Czech Republic.
> 
> "Stolichnaya", a heavy dark stout brewed in Stara Zagora, Bulgaria.
> 
> "Sweet Heart Stout", a fairly low alcohol sweet stout brewed in Scotland.
> 
> "Samuel Adams" Dark: a stout brewed in Boston, Mass.

___
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: [OT][[TL/DR] 6.6 RC2 Release

[Richmond]

On 22/03/14 17:51, Dr. Hawkins wrote:

On Fri, Mar 21, 2014 at 7:49 PM, PystCat  wrote:


One of my two favorite beers... Any ice cold Belgian beer and Guiness.
  Nothing else will do.


American Pale Ale, or IPA.  Most of what I brew is dry stout or pale ale.




"Kozel" (= goat), a fairly low alcohol dark beer from the Czech Republic.

"Stolichnaya", a heavy dark stout brewed in Stara Zagora, Bulgaria.

"Sweet Heart Stout", a fairly low alcohol sweet stout brewed in Scotland.

"Samuel Adams" Dark: a stout brewed in Boston, Mass.

___
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: [OT][[TL/DR] 6.6 RC2 Release

[Dr. Hawkins]

On Fri, Mar 21, 2014 at 7:49 PM, PystCat  wrote:

> One of my two favorite beers... Any ice cold Belgian beer and Guiness.
>  Nothing else will do.
>

American Pale Ale, or IPA.  Most of what I brew is dry stout or pale ale.


-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
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: 6.6 RC2 Release

[Richmond]

On 03/22/2014 06:30 AM, Dr. Hawkins wrote:

On Thu, Mar 20, 2014 at 9:13 PM, Bob Sneidar wrote:


I think that what you must mean by, "wrong" is, "presently inconvenient to
me",


Actually, I mean it as in, "driving on the left side of the road is wrong"
(unless you're in Britain, or . . . )




I drive a British car in Bulgaria [i.e. one that has the steering wheel 
on the 'wrong' side;
on the right], I also have a car with the steering when on the 'right 
side' (on the left).


As I also visit Britain at least once every year, and drive a car while 
I'm there, I find
that the best way to avoid confusion is always to drive down the middle 
of the road

except in places where there is a divided highway.

Richmond.

___
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: 6.6 RC2 Release

[Dr. Hawkins]

On Thu, Mar 20, 2014 at 9:13 PM, Bob Sneidar wrote:

> I think that what you must mean by, "wrong" is, "presently inconvenient to
> me",


Actually, I mean it as in, "driving on the left side of the road is wrong"
(unless you're in Britain, or . . . )


-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
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: [OT][[TL/DR] 6.6 RC2 Release

[PystCat]

One of my two favorite beers... Any ice cold Belgian beer and Guiness.  Nothing 
else will do.

> On Mar 21, 2014, at 10:09 PM, "Dr. Hawkins"  wrote:
> 
>> On Fri, Mar 21, 2014 at 11:46 AM, PystCat  wrote:
>> 
>> STOP, STOP!  Do you know how much it hurts to snort Tea through your
>> nose..?  :-P
> 
> Another reason drink beer instead (he says sipping on a belgian pale)
> 
> 
> -- 
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> ___
> 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: [OT][[TL/DR] 6.6 RC2 Release

[Dr. Hawkins]

On Fri, Mar 21, 2014 at 11:46 AM, PystCat  wrote:

> STOP, STOP!  Do you know how much it hurts to snort Tea through your
> nose..?  :-P
>

Another reason drink beer instead (he says sipping on a belgian pale)


-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
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: [Waaaaay OT] [OT][[TL/DR] 6.6 RC2 Release

[Richmond]

On 21/03/14 23:05, PystCat wrote:

I would try it but... I really dislike the taste of coffee...  I like the smell 
of it but can't take the taste.

Now... I've been told I make the best coffee in the world, so I proudly made it 
all the time for her enjoyment and my delight to see her smile.  Looking back 
on it, it might have been an incredibly devious ploy told this to me by my wife 
30 years ago so I would always make the coffee.



http://abcnews.go.com/Travel/elephant-dung-coffee-worlds-expensive-exclusive/story?id=17489242

Are you sure of that?

Let's see who gets to Thailand with the pooper-scooper first!

Richmond.

___
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: [OT][[TL/DR] 6.6 RC2 Release

[PystCat]

I would try it but... I really dislike the taste of coffee...  I like the smell 
of it but can't take the taste.

Now... I've been told I make the best coffee in the world, so I proudly made it 
all the time for her enjoyment and my delight to see her smile.  Looking back 
on it, it might have been an incredibly devious ploy told this to me by my wife 
30 years ago so I would always make the coffee. 

Any young bachelors out there take heed and listen closely: When asked to do 
something by a potential mate, make it LOOK like it was your best attempt but 
make sure it's the worst... Or you might forever be damned to do it always.  
Cooking... Cleaning... Whatever you don't want to get stuck doing the rest of 
your life.


> On Mar 21, 2014, at 3:30 PM, Richmond  wrote:
> 
>> On 21/03/14 20:46, PystCat wrote:
>> STOP, STOP!  Do you know how much it hurts to snort Tea through your nose..? 
>>  :-P
> 
> You really ought to try it with badly filtered coffee sometime; the grounds 
> do wonders to your nasal membranes :-P
>> 
 On Mar 21, 2014, at 2:43 PM, Richmond  wrote:
 
 On 21/03/14 20:16, la...@significantplanet.org wrote:
 I'm really glad we're having this very lengthy discussion about email 
 procedure.  It's helping me a lot with my programming.
>>> LOL!
>>> 
>>> Mind you, it could be pointed out that it was your choice to read the 
>>> thread.
>>> 
>>> Maybe I should insert a second comment somewhere further down the thread 
>>> just to really keep things "smoking".
>>> 
>>> Richmond.
> 
>>> 
> 
> 
> ___
> 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: [OT][[TL/DR] 6.6 RC2 Release

[Richmond]

On 21/03/14 20:46, PystCat wrote:

STOP, STOP!  Do you know how much it hurts to snort Tea through your nose..?  
:-P


You really ought to try it with badly filtered coffee sometime; the 
grounds do wonders to your nasal membranes :-P



On Mar 21, 2014, at 2:43 PM, Richmond  wrote:


On 21/03/14 20:16, la...@significantplanet.org wrote:
I'm really glad we're having this very lengthy discussion about email 
procedure.  It's helping me a lot with my programming.

LOL!

Mind you, it could be pointed out that it was your choice to read the thread.

Maybe I should insert a second comment somewhere further down the thread just to really 
keep things "smoking".

Richmond.









___
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: [OT][[TL/DR] 6.6 RC2 Release

[PystCat]

STOP, STOP!  Do you know how much it hurts to snort Tea through your nose..?  
:-P

> On Mar 21, 2014, at 2:43 PM, Richmond  wrote:
> 
>> On 21/03/14 20:16, la...@significantplanet.org wrote:
>> I'm really glad we're having this very lengthy discussion about email 
>> procedure.  It's helping me a lot with my programming.
> 
> LOL!
> 
> Mind you, it could be pointed out that it was your choice to read the thread.
> 
> Maybe I should insert a second comment somewhere further down the thread just 
> to really keep things "smoking".
> 
> Richmond.
> 
> 
> ___
> 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: [OT][[TL/DR] 6.6 RC2 Release

[Richmond]

On 21/03/14 20:16, la...@significantplanet.org wrote:
I'm really glad we're having this very lengthy discussion about email 
procedure.  It's helping me a lot with my programming.


LOL!

Mind you, it could be pointed out that it was your choice to read the 
thread.


Maybe I should insert a second comment somewhere further down the thread 
just to really keep things "smoking".


Richmond.





___
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: [OT][[TL/DR] 6.6 RC2 Release

[larry]

I'm really glad we're having this very lengthy discussion about email 
procedure.  It's helping me a lot with my programming.



- Original Message - 
From: "Peter M. Brigham" 

To: "How to use LiveCode" 
Sent: Friday, March 21, 2014 12:05 PM
Subject: Re: [OT][[TL/DR] 6.6 RC2 Release



On Mar 21, 2014, at 11:20 AM, Richard Gaskin wrote:


Bob Sneidar wrote:

> I think that what you must mean by, “wrong” is, “presently
> inconvenient to me”, but as Richmond pointed out, what is
> inconvenient for one may be standard operating procedure for
> another. I don’t want to belabor the point, but if some committee
> of persons sat around a table and actually wrote an RFC about how
> quoted text MUST be top down in an email or else it was just “wrong”,
> then I am inclined to disregard their notions, and symbolically give
> them the raspberry! Has anyone actually explained to these people
> that they can actually have a LIFE?

 

So while there is a certain err-on-the-side-of-completeness charm to 
quoting an entire, sometimes lengthy, email before replying to a small 
part of it, it seems the result of an organic evolution of our 
information-grazing habits to expect that the original message be trimmed 
to the relevant portion.


That said, it's merely a matter of taste, and perhaps usability, and 
neither trimming nor quoting in full is law.


It benefits the respondent to trim because it helps ensure the response 
will be read.


But as with my long off-topic posts here, the world won't stop if a 
message is overlooked because it's TL/DR.


It only matters to the writer who wants it to be read.

 


Guidelines are guidelines. Many times they make a good deal of sense, but 
they're just a tool, and the goal is to foster smooth communication. How you 
say things should always be in the service of getting your point across. So 
sometimes top quoting makes sense, sometimes bottom quoting, and sometimes 
interrupting the quote with responses to each point is the way to go. No 
algorithm will work all the time, and human judgment based on context is 
ultimately the thing that works best.


-- Peter

Peter M. Brigham
pmb...@gmail.com
http://home.comcast.net/~pmbrig


___
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: [OT][[TL/DR] 6.6 RC2 Release

[Peter M. Brigham]

On Mar 21, 2014, at 11:20 AM, Richard Gaskin wrote:

> Bob Sneidar wrote:
> 
> > I think that what you must mean by, “wrong” is, “presently
> > inconvenient to me”, but as Richmond pointed out, what is
> > inconvenient for one may be standard operating procedure for
> > another. I don’t want to belabor the point, but if some committee
> > of persons sat around a table and actually wrote an RFC about how
> > quoted text MUST be top down in an email or else it was just “wrong”,
> > then I am inclined to disregard their notions, and symbolically give
> > them the raspberry! Has anyone actually explained to these people
> > that they can actually have a LIFE?
> 
>  
> 
> So while there is a certain err-on-the-side-of-completeness charm to quoting 
> an entire, sometimes lengthy, email before replying to a small part of it, it 
> seems the result of an organic evolution of our information-grazing habits to 
> expect that the original message be trimmed to the relevant portion.
> 
> That said, it's merely a matter of taste, and perhaps usability, and neither 
> trimming nor quoting in full is law.
> 
> It benefits the respondent to trim because it helps ensure the response will 
> be read.
> 
> But as with my long off-topic posts here, the world won't stop if a message 
> is overlooked because it's TL/DR.
> 
> It only matters to the writer who wants it to be read.
> 
>  

Guidelines are guidelines. Many times they make a good deal of sense, but 
they're just a tool, and the goal is to foster smooth communication. How you 
say things should always be in the service of getting your point across. So 
sometimes top quoting makes sense, sometimes bottom quoting, and sometimes 
interrupting the quote with responses to each point is the way to go. No 
algorithm will work all the time, and human judgment based on context is 
ultimately the thing that works best.

-- Peter

Peter M. Brigham
pmb...@gmail.com
http://home.comcast.net/~pmbrig


___
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

[OT][[TL/DR] Re: 6.6 RC2 Release

[Richard Gaskin]

Bob Sneidar wrote:

> I think that what you must mean by, “wrong” is, “presently
> inconvenient to me”, but as Richmond pointed out, what is
> inconvenient for one may be standard operating procedure for
> another. I don’t want to belabor the point, but if some committee
> of persons sat around a table and actually wrote an RFC about how
> quoted text MUST be top down in an email or else it was just “wrong”,
> then I am inclined to disregard their notions, and symbolically give
> them the raspberry! Has anyone actually explained to these people
> that they can actually have a LIFE?

Being a bit of a curmudgeon myself (after all, I've earned the honor of 
having food thrown at me during a RevLive conference session on code 
style ), I find it fascinating that a matter of etiquette found its 
way into an RFC.


Social conventions, whether email or others, change over time.

Once upon a time Henry Watson Fowler (author of the esteemed, and later 
sadly watered-down, Dictionary of Modern English Usage) would have had 
fits had he heard the word "irregardless", having devoted a section in 
his book under "L" for "Love of the Long Word", and given that 
"irregardless" came into popular usage largely from its frequent use by 
the fictional Archie Bunker.


But today "irregardless" is in the OED.

Similarly, it was once well respected that of course you would only drop 
by your friend's house on their established visiting day, and on any 
other you would expect only to leave your card with the butler for a 
future appointment.


Few of my friends have a visiting day, and none have a butler.

And so it goes.

When the RFC was written, email was a luxury enjoyed by a relative few. 
 We didn't have our magazines filled with articles on how to manage an 
overflowing In Box and other side-effects of information overload, 
because few had email at all, the Web hadn't been invented, and none of 
us carried access to the entire world around in our pocket.


So while there is a certain err-on-the-side-of-completeness charm to 
quoting an entire, sometimes lengthy, email before replying to a small 
part of it, it seems the result of an organic evolution of our 
information-grazing habits to expect that the original message be 
trimmed to the relevant portion.


That said, it's merely a matter of taste, and perhaps usability, and 
neither trimming nor quoting in full is law.


It benefits the respondent to trim because it helps ensure the response 
will be read.


But as with my long off-topic posts here, the world won't stop if a 
message is overlooked because it's TL/DR.


It only matters to the writer who wants it to be read.

--
 Richard Gaskin
 Fourth World
 LiveCode training and consulting: http://www.fourthworld.com
 Webzine for LiveCode developers: http://www.LiveCodeJournal.com
 Follow me on Twitter:  http://twitter.com/FourthWorldSys


___
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: 6.6 RC2 Release

[Kay C Lan]

On Fri, Mar 21, 2014 at 12:13 PM, Bob Sneidar
wrote:

>
> "Wrong." I have heard that word a lot in my life.
>

Well, I meet a lot of people and I'm conviced that the vast majority of
wrongthinking people are right.
[Mrs. Havoc-Jones]
___
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: 6.6 RC2 Release

[Bob Sneidar]

“Wrong.” I have heard that word a lot in my life. Once it was “wrong” to not 
double space between sentences. It was “wrong” to eat spaghetti with a spoon. 
It was “wrong” to ride my bike on the sidewalk. It was “wrong” to pee with the 
toilet seat down. Okay, that’s still wrong! But you get my drift. “Wrong” is 
sometimes only a way of saying, “This is the way we think people on the whole 
should behave in this specific circumstance”.

I think that what you must mean by, “wrong” is, “presently inconvenient to me”, 
but as Richmond pointed out, what is inconvenient for one may be standard 
operating procedure for another. I don’t want to belabor the point, but if some 
committee of persons sat around a table and actually wrote an RFC about how 
quoted text MUST be top down in an email or else it was just “wrong”, then I am 
inclined to disregard their notions, and symbolically give them the raspberry! 
Has anyone actually explained to these people that they can actually have a 
LIFE?

Now in a list like this, most people who read it I think are fairly familiar 
with the topics they are interested in, and do not really need to see all the 
quoted text, and while I again quite agree that only relative parts *should* be 
quoted, I am a long, long way from telling anyone here how wrong they are to 
quote everything, and while once I griped about the direction they were 
quoting, because I would get mixed quotes from different people who quoted in 
opposite directions making the thread of conversation hopelessly muddled, I 
won’t even go so far as to say THAT is wrong. It’s simply “presently 
inconvenient to me.”

Bob


On Mar 20, 2014, at 19:53 , Dr. Hawkins 
mailto:doch...@gmail.com>> wrote:

I agree that people should select the pertinent text to be quoted before
replying. It's just good email etiquette.


It's more than "good etiquette." it's correct, and not doing it is
incorrect.  This is spelled out in the ancient RFC that defines email.


However, there may be an option to reverse the direction of the quoted
text to place it at the top instead of the bottom of the post.


Top-quoting is not an "option," it's just plain wrong.

It came about from AOL placing the cursor before the text, an abuse
followed by microsoft and gmail.

___
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: 6.6 RC2 Release

[Peter Haworth]

C'mon guys, use a email reader that hides the quoted text unless you click
on it (like gmail) and let's all get on with our lives.

Pete
lcSQL Software 
Home of lcStackBrowser  and
SQLiteAdmin 


On Thu, Mar 20, 2014 at 7:53 PM, Dr. Hawkins  wrote:

> On Wed, Mar 19, 2014 at 8:18 AM, Bob Sneidar  >wrote:
>
> > I agree that people should select the pertinent text to be quoted before
> > replying. It's just good email etiquette.
>
>
> It's more than "good etiquette." it's correct, and not doing it is
> incorrect.  This is spelled out in the ancient RFC that defines email.
>
>
> > However, there may be an option to reverse the direction of the quoted
> > text to place it at the top instead of the bottom of the post.
>
>
> Top-quoting is not an "option," it's just plain wrong.
>
> It came about from AOL placing the cursor before the text, an abuse
> followed by microsoft and gmail.
>
> I filed bugs 11562493 and 11562437 in the very early days of gmail, for not
> instructing users on etiquette and for misplacing the cursor in the
> top-posting position.
>
>
> --
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> ___
> 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: 6.6 RC2 Release

[Warren Samples]

On 03/20/2014 10:02 PM, Dr. Hawkins wrote:

It is quite simply correct, and not doing it is wrong.




Thank you very much for your response. No, I'm not out of my mind and 
your statement is your opinion and nothing more and I heartily disagree. 
The reasoning I gave - maintaining readability through several rounds of 
replies - is valid. Have a good evening.


Warren

___
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: 6.6 RC2 Release

[Dr. Hawkins]

On Wed, Mar 19, 2014 at 10:00 AM, Warren Samples wrote:

> If only we can get people to stop nesting responses within quoted text,
> which can make for dizziness after a couple of rounds of replies.
>
Of course, that's one of your favorite techniques... (Yes, I understand the
> logic, but it only really works for the first reply or two which makes it
> seem to me to be an arrogant strategy. I know this has been discussed here
> before, and I also see the problem is getting worse.)
>

???

Are you out of your mind???

This is not a "preference," or a "technique."

It is quite simply correct, and not doing it is wrong.

It allows multiple sub-topics to be discussed in a thread, and to keep
responses coherent, as opposed to the simplistic list.

Quite seriously, in the old days, we simply flamed people until they
complied with proper format.  Then came on the Eternal September brought on
by AOL led to this foolish notion that it was a matter of preference,
rather than right and wrong.




-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
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: 6.6 RC2 Release

[Dr. Hawkins]

On Wed, Mar 19, 2014 at 8:18 AM, Bob Sneidar wrote:

> I agree that people should select the pertinent text to be quoted before
> replying. It's just good email etiquette.


It's more than "good etiquette." it's correct, and not doing it is
incorrect.  This is spelled out in the ancient RFC that defines email.


> However, there may be an option to reverse the direction of the quoted
> text to place it at the top instead of the bottom of the post.


Top-quoting is not an "option," it's just plain wrong.

It came about from AOL placing the cursor before the text, an abuse
followed by microsoft and gmail.

I filed bugs 11562493 and 11562437 in the very early days of gmail, for not
instructing users on etiquette and for misplacing the cursor in the
top-posting position.


-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
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: 6.6 RC2 Release

[Dr. Hawkins]

On Wed, Mar 19, 2014 at 1:13 AM, Richmond wrote:

> I'm sorry, but I am not going to take responsibility for your decision to
> read the Use-List using a mobile device.
>
> LOL.
>
>
Yet you took the time to quote properly :)


-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
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: 6.6 RC2 Release

[Richmond]

On 19/03/14 21:34, Warren Samples wrote:

On 03/19/2014 12:39 PM, Richmond wrote:

to do this I have had to nest
responses so that each response-let connects to each of your points.



For whose benefit? That was not in any sense necessary. It was your 
preference. You could have just as easily constructed a coherent 
response addressing all the points in a single block. It wouldn't have 
taken advanced writing skills to do. I am confident you are capable of 
this.


What I meant be "arrogant strategy" is that after more than a couple 
of rounds, a thread in which people are nesting comments often becomes 
very difficult to follow and respond to, which may limit further 
responses. Also, useful information can become buried and hard to 
extract, which naturally makes it potentially less useful. I don't 
mean to imply that you or anyone is motivated by these negative 
possibilities, I do wonder, though, how much thought is given to them. 
"Short-sighted" might be another appropriate and less inflammatory 
description.


I have noticed that you are not alone in preferring this approach; I 
only seem to single you out because I was replying to you. Rest 
assured I dislike it just as much when someone else employs it. That's 
what motivated me to say the problem (as I see it) is getting worse.


If I were offended by the 'arrogant strategy' comment I would have been 
dead or locked up in a secure mental hospital years ago,

so don't worry yourself on that one.

Of course my 'nesting' (tweet, tweet, chirrup, chirrup) is a subjective 
decision.


But, in our multicoloured, many-splendoured world, almost everything, 
from how you hold your knife and fork to how you walk down the road,
is bound to offend someone. This is why political correctness is a 
nonstarter, because it is an attempt to offend no-one.


The ONLY way to offend no-one is to keep one's mouth permanently shut; 
at which point other people will think you are stupid, rude or

trying to to be clever for your own good.

I am quite an expert at offending people, having done it all my life, 
and at 52 have got to the stage where I have, quite frankly stopped
worrying about who I offend beyond my nearest and dearest, and, from 
time-to-time those who employ me. I can only imagine the
awful level of stress people put themselves to if they are constantly 
worrying about how they might offend someone.


- daft story follows 



Many years ago (well, about 24) my best friend Charles (who is Indian 
and Black) and I were at a cocktail party at the InterContinental Hotel
in Al Ain (UAE) when an American woman said to me, "Oh, Richmond, is 
this your black friend, I've heard so much about him." then turning,
she realised that Charles was right next to me, so she said, "Oh, I'm so 
sorry, I didn't mean 'black' in an offensive way." To which Charles
replied, "I'm black; that's the way God wants me to be, and I know God 
loves me just as much as he loves you."


We then had a laugh at that poor woman's expense (we were young and 
thoughtless) thinking of how stressed she must have got thinking

she had made a faux pas!

My friend Charles is still my best friend (although, sadly he and his 
family now live in Melbourne so we can only communicate over the
internet), still black, and still with a robust sense of humour and his 
own value in the world. I am still white, red-haired (although going white

in patches), and still offending people on a daily basis.

My kilt, having been eaten by moths last year, has been chucked out.

A new kilt is currently being made for me in Perth (Scotland) both as a 
replacement and to cope with my middle-aged spread,
and will be delivered in time for me to attend my younger son's 
graduation from his prestigious High-School in
Germany; the effect should be most pleasing amongst all those long-faced 
upper-class Prussians.


-


Cheers,

Warren



Best, Richmond.

___
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: 6.6 RC2 Release

[Warren Samples]

On 03/19/2014 12:39 PM, Richmond wrote:

to do this I have had to nest
responses so that each response-let connects to each of your points.



For whose benefit? That was not in any sense necessary. It was your 
preference. You could have just as easily constructed a coherent 
response addressing all the points in a single block. It wouldn't have 
taken advanced writing skills to do. I am confident you are capable of this.


What I meant be "arrogant strategy" is that after more than a couple of 
rounds, a thread in which people are nesting comments often becomes very 
difficult to follow and respond to, which may limit further responses. 
Also, useful information can become buried and hard to extract, which 
naturally makes it potentially less useful. I don't mean to imply that 
you or anyone is motivated by these negative possibilities, I do wonder, 
though, how much thought is given to them. "Short-sighted" might be 
another appropriate and less inflammatory description.


I have noticed that you are not alone in preferring this approach; I 
only seem to single you out because I was replying to you. Rest assured 
I dislike it just as much when someone else employs it. That's what 
motivated me to say the problem (as I see it) is getting worse.


Cheers,

Warren

___
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: 6.6 RC2 Release

[Warren Samples]

On 03/19/2014 03:13 AM, Richmond wrote:


I'm sorry, but I am not going to take responsibility for your decision
to read the Use-List using a mobile device.

LOL.

Richmond.





I don't know that there's any need to be so snarky. It's a fairly common 
request in mailing lists that care be taken to avoid quoting unnecessary 
text in replies, and it doesn't just annoy people on small screen devices.


If only we can get people to stop nesting responses within quoted text, 
which can make for dizziness after a couple of rounds of replies. Of 
course, that's one of your favorite techniques... (Yes, I understand the 
logic, but it only really works for the first reply or two which makes 
it seem to me to be an arrogant strategy. I know this has been discussed 
here before, and I also see the problem is getting worse.)


Warren

___
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: 6.6 RC2 Release

[Richmond]

On 19/03/14 19:00, Warren Samples wrote:

On 03/19/2014 03:13 AM, Richmond wrote:


I'm sorry, but I am not going to take responsibility for your decision
to read the Use-List using a mobile device.

LOL.

Richmond.





I don't know that there's any need to be so snarky. 


This topic (shortening reposts) comes up about every 18 months. Old 
chestnuts tend to make me (at least) snarky.


The useful thing about all the quoted bits from previous stuff in a 
thread is that late-comers to a thread who have not read their way 
through post-after-post can see everything in some sort of context.


While it may be a nifty thing to check the odd item on one's handheld; 
and probably one could get housemaid's thumb/finger from scrolling down 
all the stuff in a long thread; surely the advantage of having the 
context well outweighs that, and a desktop PC and/or laptop is a

far better piece of gear from this sort of thing.

It's a fairly common request in mailing lists that care be taken to 
avoid quoting unnecessary text in replies, 


As I said above; this 'problem' crops up about once every 18 months.

The real 'problem' is that what might be deemed 'unnecessary text' by 
Thee, may be deemed 'necessary text' by Me, and the other

way round.


and it doesn't just annoy people on small screen devices.

If only we can get people to stop nesting responses within quoted 
text, which can make for dizziness after a couple of rounds of 
replies. Of course, that's one of your favorite techniques...


Not mine alone.

(Yes, I understand the logic, but it only really works for the first 
reply or two which makes it seem to me to be 



an arrogant strategy.


I don't entirely understand what you mean by "arrogant strategy".

What you will see is that I have taken your posting seriously, and tried 
to reply seriously; and to do this I have had to nest

responses so that each response-let connects to each of your points.

I know this has been discussed here before, and I also see the problem 
is getting worse.)


Warren

This discussion seems also to be bifurcating into the chestnut about 
long nested texts, and the fag of trawling through them on handhelds.


I can see the gripe about both those points; although the 
contextualisation, to my mind, over-rides the fag.


The thing about using hand-helds to read the Use-list is slightly 
tangential, because, surely, scrolling through anything on
a hand-held is going to get pretty awful after a few minutes; whether 
Use-List or not. I know that scrolling through stuff on my wife's

iPad has convinced:

1. Me not to get one.

2. Her to give it to our older son to use in lectures and at the library 
at university over in Munich.


I cannot stand trackpads either, for exactly the same reason.

Richmond.

___
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: 6.6 RC2 Release

[Bob Sneidar]

I agree that people should select the pertinent text to be quoted before 
replying. It’s just good email etiquette. However, there may be an option to 
reverse the direction of the quoted text to place it at the top instead of the 
bottom of the post.

Bob


On Mar 18, 2014, at 13:24 , Gerry Orkin 
mailto:gerry.or...@gmail.com>> wrote:

Could people please limit the text they include from the message they are 
quoting when replying? A one line response followed by 50 lines of quoted text 
makes scrolling through messages on mobile devices a pain.


Thanks.




Gerry

___
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: 6.6 RC2 Release

[Richmond]

On 18/03/14 22:24, Gerry Orkin wrote:

Could people please limit the text they include from the message they are 
quoting when replying? A one line response followed by 50 lines of quoted text 
makes scrolling through messages on mobile devices a pain.



I'm sorry, but I am not going to take responsibility for your decision 
to read the Use-List using a mobile device.


LOL.

Richmond.

'pain' and to decontextualise the posting>


___
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: 6.6 RC2 Release

[Dr. Hawkins]

On Tue, Mar 18, 2014 at 1:26 PM, Mike Kerner wrote:

> Anybody else see anything particularly interesting in this release?


High-dpi support on the desktop.  This is critical for form generation; a
standard page of paper appears too small for most eyes . . .


-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
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: 6.6 RC2 Release

[Peter Haworth]

On Tue, Mar 18, 2014 at 1:26 PM, Mike Kerner wrote:

> Anybody else see anything particularly interesting in this release?  The
> expansion of the syntax for assert was interesting for me, even if I'm
> still not sure what advantage it holds over existing syntax.
>

Getting the SQLite library up to date from one that was 2 1/2 years old is
"interesting" to me!

Pete
lcSQL Software 
Home of lcStackBrowser  and
SQLiteAdmin 
___
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: 6.6 RC2 Release

[Mike Kerner]

Anybody else see anything particularly interesting in this release?  The
expansion of the syntax for assert was interesting for me, even if I'm
still not sure what advantage it holds over existing syntax.


On Tue, Mar 18, 2014 at 4:24 PM, Gerry Orkin  wrote:

> Could people please limit the text they include from the message they are
> quoting when replying? A one line response followed by 50 lines of quoted
> text makes scrolling through messages on mobile devices a pain.
>
>
> Thanks.
>
>
>
>
> Gerry
>
> On Wed, Mar 19, 2014 at 7:10 AM, Stephen MacLean 
> wrote:
>
> > Hi John
> > From the 13th:
> >>> Everything I've tested so far works fine, but mergMK seems to have a
> problem when when you go to set it's rect to the rect of a graphic that's
> been scaled, it doesn't see it as scaled and is drawn at a quarter of the
> size.
> > Best,
> > Steve
> > On Mar 18, 2014, at 4:07 PM, John Dixon  wrote:
> >> What was the mergMK issue ?
> >>
> >>> Subject: Re: 6.6 RC2 Release
> >>> From: smacl...@madmansoft.com
> >>> Date: Tue, 18 Mar 2014 16:05:56 -0400
> >>> To: use-livecode@lists.runrev.com
> >>>
> >>> Fixed the mergMk issue, thanks
> >>>
> >>> Best,
> >>>
> >>> Steve
> >>
> >>
> >> ___
> >> 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
>



-- 
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

Re: 6.6 RC2 Release

[Gerry Orkin]

Could people please limit the text they include from the message they are 
quoting when replying? A one line response followed by 50 lines of quoted text 
makes scrolling through messages on mobile devices a pain. 


Thanks. 




Gerry

On Wed, Mar 19, 2014 at 7:10 AM, Stephen MacLean 
wrote:

> Hi John
> From the 13th:
>>> Everything I've tested so far works fine, but mergMK seems to have a 
>>> problem when when you go to set it's rect to the rect of a graphic that's 
>>> been scaled, it doesn't see it as scaled and is drawn at a quarter of the 
>>> size. 
> Best,
> Steve
> On Mar 18, 2014, at 4:07 PM, John Dixon  wrote:
>> What was the mergMK issue ?
>> 
>>> Subject: Re: 6.6 RC2 Release
>>> From: smacl...@madmansoft.com
>>> Date: Tue, 18 Mar 2014 16:05:56 -0400
>>> To: use-livecode@lists.runrev.com
>>> 
>>> Fixed the mergMk issue, thanks
>>> 
>>> Best,
>>> 
>>> Steve
>> 
>>
>> ___
>> 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: 6.6 RC2 Release

[Stephen MacLean]

Hi John

>From the 13th:


>> Everything I've tested so far works fine, but mergMK seems to have a problem 
>> when when you go to set it's rect to the rect of a graphic that's been 
>> scaled, it doesn't see it as scaled and is drawn at a quarter of the size. 

Best,

Steve

On Mar 18, 2014, at 4:07 PM, John Dixon  wrote:

> What was the mergMK issue ?
> 
>> Subject: Re: 6.6 RC2 Release
>> From: smacl...@madmansoft.com
>> Date: Tue, 18 Mar 2014 16:05:56 -0400
>> To: use-livecode@lists.runrev.com
>> 
>> Fixed the mergMk issue, thanks
>> 
>> Best,
>> 
>> Steve
> 
> 
> ___
> 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: 6.6 RC2 Release

[John Dixon]

What was the mergMK issue ?

> Subject: Re: 6.6 RC2 Release
> From: smacl...@madmansoft.com
> Date: Tue, 18 Mar 2014 16:05:56 -0400
> To: use-livecode@lists.runrev.com
> 
> Fixed the mergMk issue, thanks
> 
> Best,
> 
> Steve

  
___
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: 6.6 RC2 Release

[Stephen MacLean]

Fixed the mergMk issue, thanks

Best,

Steve

On Mar 18, 2014, at 11:54 AM, Heather Laine  wrote:

> Dear List Members.
> 
> We are pleased to announce the release of LiveCode 6.6 RC2. This release is 
> now considered feature complete. 
> 
> Warning, this is a pre-release with new features which have the potential to 
> cause issues. Please ensure you backup your stacks before testing this 
> release.
> 
> Release Contents
> 
>   •   'assert' command (experimental)
>   •   New showAll fullscreenmode.
>   •   Hi-DPI support for Windows 7/8 and OSX.
>   •   HTTPS through proxy
>   •   Image Filtering Updates
>   •   iOS 7.1 Support
>   •   Graphics Library Update
>   •   OpenSSL & Encryption Updates
>   •   Proxy automatic configuration support
>   •   'secure socket' command
>   •   '#!' now recognised by server
>   •   SQLite support updated and improved
>   •   Stack scaling
>   •   OS 10.4 (Tiger) Support
>   •   54 bug fixes:
>   ◦   11927 - LCInterfaceQueryViewScale returns incorrect scale values
>   ◦   11925 - revBrowser does not use retina resolution on retina 
> Macs.
>   ◦   11924 - matrixMultiply crashes if given non-arrays as input.
>   ◦   11915 - Fullscreen mode not preserved when using \'go in 
> window\'.
>   ◦   11914 - Popping up a stack or using a stack as a menu causes 
> strange problems.
>   ◦   11908 - Images with best resizeQuality print at low resolution.
>   ◦   11903 - Ensure large XML files (those with large text nodes) 
> still parse.
>   ◦   11893 - Attaching an empty stack panel to a combo or option 
> menu causes a crash when opened.
>   ◦   11892 - Image blending only works for srcOver inkMode
>   ◦   11888 - Malformed htmlText can cause an infinite loop.
>   ◦   11885 - Memory leak in iOS causes app to exit
>   ◦   11882 - textStyle box has missing pixel in topleft.
>   ◦   11880 - Tiles with a constant color blend incorrectly when 
> acceleratedRendering is in OpenGL mode.
>   ◦   11874 - BinaryDecode wrong on Android
>   ◦   11867 - Union and intersect commands can give erroneous results 
> if source array is empty or not an array.
>   ◦   11858 - Hidden stacks don't update their position when re-shown
>   ◦   11844 - Stack height limited to screen height
>   ◦   11841 - The effective revAvailableHandlers of an object 
> sometimes contains duplicates
>   ◦   11836 - MouseLoc returns wrong value if pixelScale set to value 
> other than 1
>   ◦   11823 - SQLite enhanced query syntax not enabled.
>   ◦   11819 - Windows with no decorations don't redraw on first open.
>   ◦   11816 - Native Android control rects not scaled when set from 
> preOpenStack handler
>   ◦   11814 - Accelerated rendering causes cards to be rendered in 
> the bottom left of the screen on iOS Retina devices
>   ◦   11813 - \'go in window\' doesn\'t work on mobile
>   ◦   11811 - Cannot take screen snapshot at high resolution.
>   ◦   11789 - mobileComposeMail only blocks the first time on Android.
>   ◦   11785 - Option menu with height > 22 draws incorrectly on OSX 
> with Retina display.
>   ◦   11783 - Setting the fullscreenmode on Windows when not 
> fullscreen causes text to change.
>   ◦   11781 - Visual effects can display in the wrong place on iOS on 
> Retina devices.
>   ◦   11778 - averageDeviation returns incorrect result on Mac, 
> Linux, iOS, Android
>   ◦   11771 - Pasting HTML containing BR doesn't copy into LiveCode 
> correctly from Safari on Mac.
>   ◦   11769 - Copying from a field with paragraph-level metadata 
> causes incorrect RTF output (thus meaning it pastes incorrectly into other 
> apps on Mac).
>   ◦   11754 - Error (invalid bundle) on uploading app to iOS App Store
>   ◦   11753 - Cannot play some video streams on Android
>   ◦   11751 - After selecting an item in an option menu contaning 
> unicode, the label is corrupted (Mac only)
>   ◦   11732 - <> operator is different from 'is not' operator for 
> arrays
>   ◦   11728 - Changing the backdrop color doesn't update properly on 
> Mac.
>   ◦   11721 - Crash when taking a snapshot of the template graphic
>   ◦   11720 - SQLite FTS feature doesn't work on iOS or Mac.
>   ◦   11715 - LiveCode crashes if dragsource object is closed during 
> dragEnd handler
>   ◦   11704 - Patterns cannot be applied to lines.
>   ◦   11703 - iPhoneSetRemoteControlDisplay crashes
>   ◦   11654 - import snapshot doesn't finish until keypress on Lion.
>   ◦   11649 - Android app name can't contain unicode text
>   ◦   11617 - acceleratedRendering will clip the end of

Re: 6.6 RC2 Release

[Kenji Kojima]

Please restore box filtering.
It was very useful for making a mosaic image.
I loved 6.5 of poor quality image too.

Thanks,
--
Kenji Kojima / 小島健治
http://www.kenjikojima.com/



On Mar 18, 2014, at 11:54 AM, Heather Laine  wrote:

> Dear List Members.
> 
> We are pleased to announce the release of LiveCode 6.6 RC2. This release is 
> now considered feature complete. 
> 
> Warning, this is a pre-release with new features which have the potential to 
> cause issues. Please ensure you backup your stacks before testing this 
> release.
> 
> Release Contents
> 
>   •   'assert' command (experimental)
>   •   New showAll fullscreenmode.
>   •   Hi-DPI support for Windows 7/8 and OSX.
>   •   HTTPS through proxy
>   •   Image Filtering Updates
>   •   iOS 7.1 Support
>   •   Graphics Library Update
>   •   OpenSSL & Encryption Updates
>   •   Proxy automatic configuration support
>   •   'secure socket' command
>   •   '#!' now recognised by server
>   •   SQLite support updated and improved
>   •   Stack scaling
>   •   OS 10.4 (Tiger) Support
>   •   54 bug fixes:
>   ◦   11927 - LCInterfaceQueryViewScale returns incorrect scale values
>   ◦   11925 - revBrowser does not use retina resolution on retina 
> Macs.
>   ◦   11924 - matrixMultiply crashes if given non-arrays as input.
>   ◦   11915 - Fullscreen mode not preserved when using \'go in 
> window\'.
>   ◦   11914 - Popping up a stack or using a stack as a menu causes 
> strange problems.
>   ◦   11908 - Images with best resizeQuality print at low resolution.
>   ◦   11903 - Ensure large XML files (those with large text nodes) 
> still parse.
>   ◦   11893 - Attaching an empty stack panel to a combo or option 
> menu causes a crash when opened.
>   ◦   11892 - Image blending only works for srcOver inkMode
>   ◦   11888 - Malformed htmlText can cause an infinite loop.
>   ◦   11885 - Memory leak in iOS causes app to exit
>   ◦   11882 - textStyle box has missing pixel in topleft.
>   ◦   11880 - Tiles with a constant color blend incorrectly when 
> acceleratedRendering is in OpenGL mode.
>   ◦   11874 - BinaryDecode wrong on Android
>   ◦   11867 - Union and intersect commands can give erroneous results 
> if source array is empty or not an array.
>   ◦   11858 - Hidden stacks don't update their position when re-shown
>   ◦   11844 - Stack height limited to screen height
>   ◦   11841 - The effective revAvailableHandlers of an object 
> sometimes contains duplicates
>   ◦   11836 - MouseLoc returns wrong value if pixelScale set to value 
> other than 1
>   ◦   11823 - SQLite enhanced query syntax not enabled.
>   ◦   11819 - Windows with no decorations don't redraw on first open.
>   ◦   11816 - Native Android control rects not scaled when set from 
> preOpenStack handler
>   ◦   11814 - Accelerated rendering causes cards to be rendered in 
> the bottom left of the screen on iOS Retina devices
>   ◦   11813 - \'go in window\' doesn\'t work on mobile
>   ◦   11811 - Cannot take screen snapshot at high resolution.
>   ◦   11789 - mobileComposeMail only blocks the first time on Android.
>   ◦   11785 - Option menu with height > 22 draws incorrectly on OSX 
> with Retina display.
>   ◦   11783 - Setting the fullscreenmode on Windows when not 
> fullscreen causes text to change.
>   ◦   11781 - Visual effects can display in the wrong place on iOS on 
> Retina devices.
>   ◦   11778 - averageDeviation returns incorrect result on Mac, 
> Linux, iOS, Android
>   ◦   11771 - Pasting HTML containing BR doesn't copy into LiveCode 
> correctly from Safari on Mac.
>   ◦   11769 - Copying from a field with paragraph-level metadata 
> causes incorrect RTF output (thus meaning it pastes incorrectly into other 
> apps on Mac).
>   ◦   11754 - Error (invalid bundle) on uploading app to iOS App Store
>   ◦   11753 - Cannot play some video streams on Android
>   ◦   11751 - After selecting an item in an option menu contaning 
> unicode, the label is corrupted (Mac only)
>   ◦   11732 - <> operator is different from 'is not' operator for 
> arrays
>   ◦   11728 - Changing the backdrop color doesn't update properly on 
> Mac.
>   ◦   11721 - Crash when taking a snapshot of the template graphic
>   ◦   11720 - SQLite FTS feature doesn't work on iOS or Mac.
>   ◦   11715 - LiveCode crashes if dragsource object is closed during 
> dragEnd handler
>   ◦   11704 - Patterns cannot be applied to lines.
>   ◦   11703 - iPhoneSetRemoteControlDisplay crashes
>   ◦   11654 - import snapshot doesn't finish until keypress on Lion.
>

6.6 RC2 Release

[Heather Laine]

Dear List Members.

We are pleased to announce the release of LiveCode 6.6 RC2. This release is now 
considered feature complete. 

Warning, this is a pre-release with new features which have the potential to 
cause issues. Please ensure you backup your stacks before testing this release.

Release Contents

•   'assert' command (experimental)
•   New showAll fullscreenmode.
•   Hi-DPI support for Windows 7/8 and OSX.
•   HTTPS through proxy
•   Image Filtering Updates
•   iOS 7.1 Support
•   Graphics Library Update
•   OpenSSL & Encryption Updates
•   Proxy automatic configuration support
•   'secure socket' command
•   '#!' now recognised by server
•   SQLite support updated and improved
•   Stack scaling
•   OS 10.4 (Tiger) Support
•   54 bug fixes:
◦   11927 - LCInterfaceQueryViewScale returns incorrect scale values
◦   11925 - revBrowser does not use retina resolution on retina 
Macs.
◦   11924 - matrixMultiply crashes if given non-arrays as input.
◦   11915 - Fullscreen mode not preserved when using \'go in 
window\'.
◦   11914 - Popping up a stack or using a stack as a menu causes 
strange problems.
◦   11908 - Images with best resizeQuality print at low resolution.
◦   11903 - Ensure large XML files (those with large text nodes) 
still parse.
◦   11893 - Attaching an empty stack panel to a combo or option 
menu causes a crash when opened.
◦   11892 - Image blending only works for srcOver inkMode
◦   11888 - Malformed htmlText can cause an infinite loop.
◦   11885 - Memory leak in iOS causes app to exit
◦   11882 - textStyle box has missing pixel in topleft.
◦   11880 - Tiles with a constant color blend incorrectly when 
acceleratedRendering is in OpenGL mode.
◦   11874 - BinaryDecode wrong on Android
◦   11867 - Union and intersect commands can give erroneous results 
if source array is empty or not an array.
◦   11858 - Hidden stacks don't update their position when re-shown
◦   11844 - Stack height limited to screen height
◦   11841 - The effective revAvailableHandlers of an object 
sometimes contains duplicates
◦   11836 - MouseLoc returns wrong value if pixelScale set to value 
other than 1
◦   11823 - SQLite enhanced query syntax not enabled.
◦   11819 - Windows with no decorations don't redraw on first open.
◦   11816 - Native Android control rects not scaled when set from 
preOpenStack handler
◦   11814 - Accelerated rendering causes cards to be rendered in 
the bottom left of the screen on iOS Retina devices
◦   11813 - \'go in window\' doesn\'t work on mobile
◦   11811 - Cannot take screen snapshot at high resolution.
◦   11789 - mobileComposeMail only blocks the first time on Android.
◦   11785 - Option menu with height > 22 draws incorrectly on OSX 
with Retina display.
◦   11783 - Setting the fullscreenmode on Windows when not 
fullscreen causes text to change.
◦   11781 - Visual effects can display in the wrong place on iOS on 
Retina devices.
◦   11778 - averageDeviation returns incorrect result on Mac, 
Linux, iOS, Android
◦   11771 - Pasting HTML containing BR doesn't copy into LiveCode 
correctly from Safari on Mac.
◦   11769 - Copying from a field with paragraph-level metadata 
causes incorrect RTF output (thus meaning it pastes incorrectly into other apps 
on Mac).
◦   11754 - Error (invalid bundle) on uploading app to iOS App Store
◦   11753 - Cannot play some video streams on Android
◦   11751 - After selecting an item in an option menu contaning 
unicode, the label is corrupted (Mac only)
◦   11732 - <> operator is different from 'is not' operator for 
arrays
◦   11728 - Changing the backdrop color doesn't update properly on 
Mac.
◦   11721 - Crash when taking a snapshot of the template graphic
◦   11720 - SQLite FTS feature doesn't work on iOS or Mac.
◦   11715 - LiveCode crashes if dragsource object is closed during 
dragEnd handler
◦   11704 - Patterns cannot be applied to lines.
◦   11703 - iPhoneSetRemoteControlDisplay crashes
◦   11654 - import snapshot doesn't finish until keypress on Lion.
◦   11649 - Android app name can't contain unicode text
◦   11617 - acceleratedRendering will clip the end of long 
scrolling groups
◦   11462 - Failing to set image data to the image data of self
◦   11442 - Can't quit LiveCode after setting the 
securit