Re: The Long Name peculiarities

2012-06-19 Thread Peter M. Brigham
On Jun 19, 2012, at 1:20 PM, J. Landman Gay wrote: > On 6/19/12 12:15 PM, Richmond wrote: >> On 06/19/2012 08:10 PM, Peter M. Brigham wrote: >>> On Jun 19, 2012, at 11:51 AM, Bob Sneidar wrote: >>> I kept running out of memory though. >>> Yeah, that happens more and more to me as time goes o

Re: The Long Name peculiarities

2012-06-19 Thread Richmond
On 06/19/2012 08:20 PM, J. Landman Gay wrote: On 6/19/12 12:15 PM, Richmond wrote: On 06/19/2012 08:10 PM, Peter M. Brigham wrote: On Jun 19, 2012, at 11:51 AM, Bob Sneidar wrote: I kept running out of memory though. Yeah, that happens more and more to me as time goes on Ha, Ha, Ha; tr

Re: The Long Name peculiarities

2012-06-19 Thread J. Landman Gay
On 6/19/12 12:15 PM, Richmond wrote: On 06/19/2012 08:10 PM, Peter M. Brigham wrote: On Jun 19, 2012, at 11:51 AM, Bob Sneidar wrote: I kept running out of memory though. Yeah, that happens more and more to me as time goes on Ha, Ha, Ha; tried to shove a RAM module in my ear last week .

Re: The Long Name peculiarities

2012-06-19 Thread Richmond
On 06/19/2012 08:10 PM, Peter M. Brigham wrote: On Jun 19, 2012, at 11:51 AM, Bob Sneidar wrote: I kept running out of memory though. Yeah, that happens more and more to me as time goes on Ha, Ha, Ha; tried to shove a RAM module in my ear last week . . . . -- Peter Peter M. Brigham p

Re: The Long Name peculiarities

2012-06-19 Thread Richmond
On 06/19/2012 06:51 PM, Bob Sneidar wrote: Ooohh Commodore Basic! My first digital love! That was fun! I kept running out of memory though. Bob On Jun 19, 2012, at 8:45 AM, Tim Jones wrote: On Jun 19, 2012, at 8:36 AM, Bob Sneidar wrote: Whoa! You can use a single letter as a function nam

Re: The Long Name peculiarities

2012-06-19 Thread Peter M. Brigham
On Jun 19, 2012, at 11:51 AM, Bob Sneidar wrote: > I kept running out of memory though. Yeah, that happens more and more to me as time goes on -- Peter Peter M. Brigham pmb...@gmail.com http://home.comcast.net/~pmbrig ___ use-livecode mailing l

Re: The Long Name peculiarities

2012-06-19 Thread Peter Haworth
Thanks Peter, I will give this a try. Pete lcSQL Software On Tue, Jun 19, 2012 at 5:47 AM, Peter M. Brigham wrote: > As a work-around, here's a handler that I use from time to time, and it > could be modified for your purpose:

Re: The Long Name peculiarities

2012-06-19 Thread Bob Sneidar
Ooohh Commodore Basic! My first digital love! That was fun! I kept running out of memory though. Bob On Jun 19, 2012, at 8:45 AM, Tim Jones wrote: > On Jun 19, 2012, at 8:36 AM, Bob Sneidar wrote: > >> Whoa! You can use a single letter as a function name?? I thought that was >> strictly ver

Re: The Long Name peculiarities

2012-06-19 Thread Tim Jones
On Jun 19, 2012, at 8:36 AM, Bob Sneidar wrote: > Whoa! You can use a single letter as a function name?? I thought that was > strictly verboten! I see once more I am mistaken. Yep - and you can use variables like AA, b1, ae, c, e3 - just like in Commodore BASIC ;-). Tim

Re: The Long Name peculiarities

2012-06-19 Thread Bob Sneidar
Whoa! You can use a single letter as a function name?? I thought that was strictly verboten! I see once more I am mistaken. Bob > > -- requires q() > ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe

Re: The Long Name peculiarities

2012-06-18 Thread Peter Haworth
Hi Richard, Thanks for pointing me to the bug report. Seeing that you put it in there in 2005, it's pretty clear it won;t get fixed at this point so I'll have to program around it. I noticed the response to your bug report included the time honored excuse that fixing it would cause backwards comp

Re: The Long Name peculiarities

2012-06-18 Thread Mike Bonner
Yeah, dictionary says a default name will be set if none is supplied during the create. Obviously this isn't happening as it should. On Mon, Jun 18, 2012 at 5:58 PM, Richard Gaskin wrote: > Peter Haworth wrote: > > To me, this is a bug but I've been corrected before on what I believe to >> be >>

Re: The Long Name peculiarities

2012-06-18 Thread Peter Haworth
I can see why this happens with the control itself but not for the owners of the control that do have names defined. Pete lcSQL Software On Mon, Jun 18, 2012 at 4:08 PM, Mike Bonner wrote: > Yep, do the same with buttons. > > create button > create button > > > you get

Re: The Long Name peculiarities

2012-06-18 Thread Peter Haworth
Thanks Mike, interesting what happens if you just click in and out of the name box. Unfortunately, I don't have control over the objects that cause this behavior - they are part of the datagrid structure. I think I will report it as a bug. Kind of a pain to work around it though. I think I will

Re: The Long Name peculiarities

2012-06-18 Thread Richard Gaskin
Peter Haworth wrote: To me, this is a bug but I've been corrected before on what I believe to be bugs so what do you think? I think it's a bug, and have submitted a request for changing the behavior: "long name" returns long ID when control name is empty

Re: The Long Name peculiarities

2012-06-18 Thread Mike Bonner
Yep, do the same with buttons. create button create button you get two buttons with no text, IE no name. Do something that forces the name to be set and viola'. if you create button then put the name of the last button, same deal. It puts the id because apparently the name is not set. This also

Re: The Long Name peculiarities

2012-06-18 Thread Mike Bonner
If you go into the inspector after creating the 2 grcs the name is set to the id. I think this is a behavior that occurs when there is no valid name set for the grc, but the name of the grc isn't actually whats shown in the inspector. If you click in the box, don't change the name, click out of the

Re: The Long Name peculiarities

2012-06-18 Thread Bob Sneidar
Wow! Nice catch! If not a bug, it's certainly an "anomaly". Bob On Jun 18, 2012, at 3:32 PM, Peter Haworth wrote: > I've come across what I think is a bug in what is returned as the long name > of a control. It only happens in fairly obscure circumstances. > > Here's the recipe (LC 5.5). >