subject:"Is this a bug\?"

gt;>
> >>>>> On Jan 24, 2024, at 12:51 PM, Craig Newman via use-livecode <
> >>>> use-livecode@lists.runrev.com <mailto:use-livecode@lists.runrev.com>>
> wrote:
> >>>>>
> >>>>> Brian.
> >>>>>
> >>>>> Nope. Those two chars pass through the filter, er, filtered.
> >>>>>
> >>>>> Again, I did not test the entire character set.
> >>>>>
> >>>>> Craig
> >>>>>
> >>>>>> On Jan 24, 2024, at 11:05 AM, Brian Milby via use-livecode <
> >>>> use-livecode@lists.runrev.com> wrote:
> >>>>>>
> >>>>>> The only other two that would cause issues are ? and * which are
> single
> >>>> and multiple char wildcards respectively.
> >>>>>>
> >>>>>> Brian Milby
> >>>>>> br...@milby7.com
> >>>>>>
> >>>>>>> On Jan 24, 2024, at 10:21 AM, Craig Newman via use-livecode <
> >>>> use-livecode@lists.runrev.com> wrote:
> >>>>>>>
> >>>>>>> I did not test the ASCII set exhaustively, but the culprit is the
> >>>> char “[“ (ASCII 91). Any other char (including “]”) in the string
> works
> >>>> correctly, that is, nothing is left after the filter command executes.
> >>>>>>>
> >>>>>>> I do not know enough to say whether that particular char  does
> >>>> something to the filter command, which may use regex somehow in its
> inner
> >>>> workings.
> >>>>>>>
> >>>>>>> Craig
> >>>>>>>
> >>>>>>> Craig
> >>>>>>>
> >>>>>>>> On Jan 23, 2024, at 9:45 PM, Brian Milby via use-livecode <
> >>>> use-livecode@lists.runrev.com> wrote:
> >>>>>>>>
> >>>>>>>> Not sure this is really a bug.  The default is to match a
> >>>> wildcardPattern.  If you want to match [ then you must use [[] in the
> >>>> pattern.
> >>>>>>>>
> >>>>>>>> Brian Milby
> >>>>>>>> br...@milby7.com
> >>>>>>>>
> >>>>>>>>>> On Jan 23, 2024, at 9:02 PM, Neville Smythe via use-livecode <
> >>>> use-livecode@lists.runrev.com> wrote:
> >>>>>>>>>
> >>>>>>>>> Try this in the msg box:
> >>>>>>>>>
> >>>>>>>>> put "aaa[bbb" into tStr; put line 1 of tStr into tLine; filter
> tStr
> >>>> without tLine; put tStr
> >>>>>>>>> I get (using MacOS, LC 9.6.11)
> >>>>>>>>>
> >>>>>>>>> aaa[bbb
> >>>>>>>>>
> >>>>>>>>> That is to say, the line is not filtered out.
> >>>>>>>>>
> >>>>>>>>> And:
> >>>>>>>>>
> >>>>>>>>> put "aaa[bbb" into tStr; filter tStr with tStr; put tStr
> >>>>>>>>>
> >>>>>>>>> produces an empty string instead of the original string.
> >>>>>>>>>
> >>>>>>>>> The bug occurs if the line contains the character “[“ anywhere;
> any
> >>>> lines containing that character are ignored by both filter with and
> filter
> >>>> without.
> >>>>>>>>>
> >>>>>>>>> This is really serious, because I rely on the filter command a
> lot,
> >>>> as I would think do many other developers!
> >>>>>>>>>
> >>>>>>>>> Don’t know if it occurs with other characters, but I have never
> seen
> >>>> it before. I discovered it when filtering lines with regular
> expressions.
> >>>> Other special regexp characters I have tested do not trigger the bug.
> >>>>>>>>>
> >>>>>>>>> Neville Smythe
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> ___
> >>>>>>>>> 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
> >>>>>>
> >>>>>> ___
> >>>>>> 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
> >>>>
> >>> ___
> >>> 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 <mailto: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: Nasty filter bug

Brian.

So the inclusion of “[“ would have matched nothing in the original string 
""aaa[bbb””? That is, even though the bracketed string was not “closed” with 
“]”, did it try to find a string that began with “b”, failed, and therefore 
returned the original string untouched?

Craig

> On Jan 24, 2024, at 4:37 PM, Brian Milby via use-livecode 
>  wrote:
> 
> I just want to clarify that this isn’t the regex version of filter but the 
> wildcard pattern version.  It is much less complicated than regex.  Square 
> brackets are used to group characters to be matched so you can use [abc]* to 
> match any item that starts with a, b, or c.  The dictionary entry for this is 
> pretty good.
> 
> Brian Milby
> br...@milby7.com <mailto:br...@milby7.com>
> 
>> On Jan 24, 2024, at 3:35 PM, Craig Newman via use-livecode 
>> mailto:use-livecode@lists.runrev.com>> wrote:
>> 
>> Brian.
>> 
>> The original post tried to filter a string by filtering (without) that 
>> actual string, and was interested in why that did not yield empty. 
>> Intuitively, the result of such a filter operation ought always to be empty. 
>> The presence of the char “[“ is the “culprit”. That is as far as I took it.
>> 
>> Anyway, you state that the char “[“ is a regex special character, which 
>> explains a lot. The other two, “?” and “*” filter without issue, though, and 
>> I guess one has to be a regex user to see why.
>> 
>> I am not.
>> 
>> Craig
>> 
>>> On Jan 24, 2024, at 2:53 PM, Brian Milby via use-livecode 
>>> mailto:use-livecode@lists.runrev.com>> 
>>> wrote:
>>> 
>>> Your test misses the actual issue:
>>> 
>>> on mouseup
>>> local tStr
>>> local tFilter
>>> put "a*b" into tFilter
>>> put "anything bold" into tStr
>>> filter tStr with tFilter
>>> put tStr
>>> end mouseup
>>> 
>>> Will yield "anything bold"
>>> 
>>> while using the following 2 lines:
>>> put "a?b" into tFilter
>>> put "a*b" into tStr
>>> will yield "a*b"
>>> 
>>> Finally, using the following 2 lines:
>>> put "a[?]b" into tFilter
>>> put "a?b" into tStr
>>> will  yield "a?b"
>>> 
>>> The point is that you can end up with issues if you are counting on "*" and
>>> "?" to filter literally.  They don't - they are wildcards and can match
>>> anything (multiple char or single char respectively).  The "[" is also
>>> special.
>>> 
>>> To ensure that your filters work properly if you do not want to use any
>>> wildcards (i.e. match * and ? literally) would require you to change *, ?,
>>> and [ to [*], [?], and [[].
>>> 
>>>> On Wed, Jan 24, 2024 at 1:19 PM Craig Newman via use-livecode <
>>>> use-livecode@lists.runrev.com <mailto:use-livecode@lists.runrev.com>> 
>>>> wrote:
>>>> 
>>>> OK, instead of working I did this:
>>>> 
>>>> on mouseUp
>>>> 
>>>> repeat with y = 1 to 255
>>>> 
>>>> put "XX" & numToChar(y) & "XX"  into temp
>>>> 
>>>> filter temp without temp
>>>> 
>>>> if temp <> "" then put y & return after accum
>>>> 
>>>> end repeat
>>>> 
>>>> answer accum
>>>> 
>>>> end mouseUp
>>>> 
>>>> There are two characters that prevent the filter command from doing its
>>>> job: ASCII 91 (“[“) and ASCII 10, the return char.
>>>> 
>>>> 
>>>> 
>>>> Craig
>>>> 
>>>> 
>>>>> On Jan 24, 2024, at 12:51 PM, Craig Newman via use-livecode <
>>>> use-livecode@lists.runrev.com <mailto:use-livecode@lists.runrev.com>> 
>>>> wrote:
>>>>> 
>>>>> Brian.
>>>>> 
>>>>> Nope. Those two chars pass through the filter, er, filtered.
>>>>> 
>>>>> Again, I did not test the entire character set.
>>>>> 
>>>>> Craig
>>>>> 
>>>>>> On Jan 24, 2024, at 11:05 AM, Brian Milby via use-livecode <
>>>> use-livecode@lists.runrev.com> wrote:
>>>>>> 
>>>>>> The only other two that would cause issues are ? and * which are single
>>>>

Re: Nasty filter bug

I just want to clarify that this isn’t the regex version of filter but the 
wildcard pattern version.  It is much less complicated than regex.  Square 
brackets are used to group characters to be matched so you can use [abc]* to 
match any item that starts with a, b, or c.  The dictionary entry for this is 
pretty good.

Brian Milby
br...@milby7.com

> On Jan 24, 2024, at 3:35 PM, Craig Newman via use-livecode 
>  wrote:
> 
> Brian.
> 
> The original post tried to filter a string by filtering (without) that actual 
> string, and was interested in why that did not yield empty. Intuitively, the 
> result of such a filter operation ought always to be empty. The presence of 
> the char “[“ is the “culprit”. That is as far as I took it.
> 
> Anyway, you state that the char “[“ is a regex special character, which 
> explains a lot. The other two, “?” and “*” filter without issue, though, and 
> I guess one has to be a regex user to see why.
> 
> I am not.
> 
> Craig
> 
>> On Jan 24, 2024, at 2:53 PM, Brian Milby via use-livecode 
>>  wrote:
>> 
>> Your test misses the actual issue:
>> 
>> on mouseup
>>  local tStr
>>  local tFilter
>>  put "a*b" into tFilter
>>  put "anything bold" into tStr
>>  filter tStr with tFilter
>>  put tStr
>> end mouseup
>> 
>> Will yield "anything bold"
>> 
>> while using the following 2 lines:
>>  put "a?b" into tFilter
>>  put "a*b" into tStr
>> will yield "a*b"
>> 
>> Finally, using the following 2 lines:
>>  put "a[?]b" into tFilter
>>  put "a?b" into tStr
>> will  yield "a?b"
>> 
>> The point is that you can end up with issues if you are counting on "*" and
>> "?" to filter literally.  They don't - they are wildcards and can match
>> anything (multiple char or single char respectively).  The "[" is also
>> special.
>> 
>> To ensure that your filters work properly if you do not want to use any
>> wildcards (i.e. match * and ? literally) would require you to change *, ?,
>> and [ to [*], [?], and [[].
>> 
>>> On Wed, Jan 24, 2024 at 1:19 PM Craig Newman via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
>>> 
>>> OK, instead of working I did this:
>>> 
>>> on mouseUp
>>> 
>>> repeat with y = 1 to 255
>>> 
>>> put "XX" & numToChar(y) & "XX"  into temp
>>> 
>>> filter temp without temp
>>> 
>>> if temp <> "" then put y & return after accum
>>> 
>>> end repeat
>>> 
>>> answer accum
>>> 
>>> end mouseUp
>>> 
>>> There are two characters that prevent the filter command from doing its
>>> job: ASCII 91 (“[“) and ASCII 10, the return char.
>>> 
>>> 
>>> 
>>> Craig
>>> 
>>> 
>>>> On Jan 24, 2024, at 12:51 PM, Craig Newman via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
>>>> 
>>>> Brian.
>>>> 
>>>> Nope. Those two chars pass through the filter, er, filtered.
>>>> 
>>>> Again, I did not test the entire character set.
>>>> 
>>>> Craig
>>>> 
>>>>> On Jan 24, 2024, at 11:05 AM, Brian Milby via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
>>>>> 
>>>>> The only other two that would cause issues are ? and * which are single
>>> and multiple char wildcards respectively.
>>>>> 
>>>>> Brian Milby
>>>>> br...@milby7.com
>>>>> 
>>>>>> On Jan 24, 2024, at 10:21 AM, Craig Newman via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
>>>>>> 
>>>>>> I did not test the ASCII set exhaustively, but the culprit is the
>>> char “[“ (ASCII 91). Any other char (including “]”) in the string works
>>> correctly, that is, nothing is left after the filter command executes.
>>>>>> 
>>>>>> I do not know enough to say whether that particular char  does
>>> something to the filter command, which may use regex somehow in its inner
>>> workings.
>>>>>> 
>>>>>> Craig
>>>>>> 
>>>>>> Craig
>>>>>> 
>>>>>>> On Jan 23, 2024, at 9:45 PM, Brian Milby via use-livecode <
>>> use-live

Re: Nasty filter bug (not)

2024-01-24 Thread Neville Smythe via use-livecode

Thanks Brian of putting me right (once again) . I had completely forgotten.the 
escape sequence for the wildcards is [*] and [? (an unexpected way to escape a 
character, but it is what it is) and so had overlooked that [ is itself a 
special character.

And neither * nor ? In the msg box example cause the so-called “bug” but for 
accidental reasons since they happen to match themselves, so they didn’t 
trigger my memory to look further for an explanation!

Neville Smythe




___
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: Nasty filter bug

Brian.

The original post tried to filter a string by filtering (without) that actual 
string, and was interested in why that did not yield empty. Intuitively, the 
result of such a filter operation ought always to be empty. The presence of the 
char “[“ is the “culprit”. That is as far as I took it.

Anyway, you state that the char “[“ is a regex special character, which 
explains a lot. The other two, “?” and “*” filter without issue, though, and I 
guess one has to be a regex user to see why.

I am not.

Craig

> On Jan 24, 2024, at 2:53 PM, Brian Milby via use-livecode 
>  wrote:
> 
> Your test misses the actual issue:
> 
> on mouseup
>   local tStr
>   local tFilter
>   put "a*b" into tFilter
>   put "anything bold" into tStr
>   filter tStr with tFilter
>   put tStr
> end mouseup
> 
> Will yield "anything bold"
> 
> while using the following 2 lines:
>   put "a?b" into tFilter
>   put "a*b" into tStr
> will yield "a*b"
> 
> Finally, using the following 2 lines:
>   put "a[?]b" into tFilter
>   put "a?b" into tStr
> will  yield "a?b"
> 
> The point is that you can end up with issues if you are counting on "*" and
> "?" to filter literally.  They don't - they are wildcards and can match
> anything (multiple char or single char respectively).  The "[" is also
> special.
> 
> To ensure that your filters work properly if you do not want to use any
> wildcards (i.e. match * and ? literally) would require you to change *, ?,
> and [ to [*], [?], and [[].
> 
> On Wed, Jan 24, 2024 at 1:19 PM Craig Newman via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> 
>> OK, instead of working I did this:
>> 
>> on mouseUp
>> 
>> repeat with y = 1 to 255
>> 
>> put "XX" & numToChar(y) & "XX"  into temp
>> 
>> filter temp without temp
>> 
>> if temp <> "" then put y & return after accum
>> 
>> end repeat
>> 
>> answer accum
>> 
>> end mouseUp
>> 
>> There are two characters that prevent the filter command from doing its
>> job: ASCII 91 (“[“) and ASCII 10, the return char.
>> 
>> 
>> 
>> Craig
>> 
>> 
>>> On Jan 24, 2024, at 12:51 PM, Craig Newman via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>> 
>>> Brian.
>>> 
>>> Nope. Those two chars pass through the filter, er, filtered.
>>> 
>>> Again, I did not test the entire character set.
>>> 
>>> Craig
>>> 
>>>> On Jan 24, 2024, at 11:05 AM, Brian Milby via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>>> 
>>>> The only other two that would cause issues are ? and * which are single
>> and multiple char wildcards respectively.
>>>> 
>>>> Brian Milby
>>>> br...@milby7.com
>>>> 
>>>>> On Jan 24, 2024, at 10:21 AM, Craig Newman via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>>>> 
>>>>> I did not test the ASCII set exhaustively, but the culprit is the
>> char “[“ (ASCII 91). Any other char (including “]”) in the string works
>> correctly, that is, nothing is left after the filter command executes.
>>>>> 
>>>>> I do not know enough to say whether that particular char  does
>> something to the filter command, which may use regex somehow in its inner
>> workings.
>>>>> 
>>>>> Craig
>>>>> 
>>>>> Craig
>>>>> 
>>>>>> On Jan 23, 2024, at 9:45 PM, Brian Milby via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>>>>> 
>>>>>> Not sure this is really a bug.  The default is to match a
>> wildcardPattern.  If you want to match [ then you must use [[] in the
>> pattern.
>>>>>> 
>>>>>> Brian Milby
>>>>>> br...@milby7.com
>>>>>> 
>>>>>>>> On Jan 23, 2024, at 9:02 PM, Neville Smythe via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>>>>>> 
>>>>>>> Try this in the msg box:
>>>>>>> 
>>>>>>> put "aaa[bbb" into tStr; put line 1 of tStr into tLine; filter tStr
>> without tLine; put tStr
>>>>>>> I get (using MacOS, LC 9.6.11)
>>>>>>> 
>>>>>>> aaa[bbb
>>>>

Re: Nasty filter bug

Your test misses the actual issue:

on mouseup
   local tStr
   local tFilter
   put "a*b" into tFilter
   put "anything bold" into tStr
   filter tStr with tFilter
   put tStr
end mouseup

Will yield "anything bold"

while using the following 2 lines:
   put "a?b" into tFilter
   put "a*b" into tStr
will yield "a*b"

Finally, using the following 2 lines:
   put "a[?]b" into tFilter
   put "a?b" into tStr
will  yield "a?b"

The point is that you can end up with issues if you are counting on "*" and
"?" to filter literally.  They don't - they are wildcards and can match
anything (multiple char or single char respectively).  The "[" is also
special.

To ensure that your filters work properly if you do not want to use any
wildcards (i.e. match * and ? literally) would require you to change *, ?,
and [ to [*], [?], and [[].

On Wed, Jan 24, 2024 at 1:19 PM Craig Newman via use-livecode <
use-livecode@lists.runrev.com> wrote:

> OK, instead of working I did this:
>
> on mouseUp
>
> repeat with y = 1 to 255
>
> put "XX" & numToChar(y) & "XX"  into temp
>
> filter temp without temp
>
> if temp <> "" then put y & return after accum
>
> end repeat
>
> answer accum
>
> end mouseUp
>
> There are two characters that prevent the filter command from doing its
> job: ASCII 91 (“[“) and ASCII 10, the return char.
>
>
>
> Craig
>
>
> > On Jan 24, 2024, at 12:51 PM, Craig Newman via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > Brian.
> >
> > Nope. Those two chars pass through the filter, er, filtered.
> >
> > Again, I did not test the entire character set.
> >
> > Craig
> >
> >> On Jan 24, 2024, at 11:05 AM, Brian Milby via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >>
> >> The only other two that would cause issues are ? and * which are single
> and multiple char wildcards respectively.
> >>
> >> Brian Milby
> >> br...@milby7.com
> >>
> >>> On Jan 24, 2024, at 10:21 AM, Craig Newman via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >>>
> >>> I did not test the ASCII set exhaustively, but the culprit is the
> char “[“ (ASCII 91). Any other char (including “]”) in the string works
> correctly, that is, nothing is left after the filter command executes.
> >>>
> >>> I do not know enough to say whether that particular char  does
> something to the filter command, which may use regex somehow in its inner
> workings.
> >>>
> >>> Craig
> >>>
> >>> Craig
> >>>
> >>>> On Jan 23, 2024, at 9:45 PM, Brian Milby via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >>>>
> >>>> Not sure this is really a bug.  The default is to match a
> wildcardPattern.  If you want to match [ then you must use [[] in the
> pattern.
> >>>>
> >>>> Brian Milby
> >>>> br...@milby7.com
> >>>>
> >>>>>> On Jan 23, 2024, at 9:02 PM, Neville Smythe via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >>>>>
> >>>>> Try this in the msg box:
> >>>>>
> >>>>> put "aaa[bbb" into tStr; put line 1 of tStr into tLine; filter tStr
> without tLine; put tStr
> >>>>> I get (using MacOS, LC 9.6.11)
> >>>>>
> >>>>> aaa[bbb
> >>>>>
> >>>>> That is to say, the line is not filtered out.
> >>>>>
> >>>>> And:
> >>>>>
> >>>>> put "aaa[bbb" into tStr; filter tStr with tStr; put tStr
> >>>>>
> >>>>> produces an empty string instead of the original string.
> >>>>>
> >>>>> The bug occurs if the line contains the character “[“ anywhere; any
> lines containing that character are ignored by both filter with and filter
> without.
> >>>>>
> >>>>> This is really serious, because I rely on the filter command a lot,
> as I would think do many other developers!
> >>>>>
> >>>>> Don’t know if it occurs with other characters, but I have never seen
> it before. I discovered it when filtering lines with regular expressions.
> Other special regexp characters I have tested do not trigger the bug.
> >>>>>
> >>>>> Nevi

Re: Nasty filter bug

OK, instead of working I did this:

on mouseUp

repeat with y = 1 to 255

put "XX" & numToChar(y) & "XX"  into temp

filter temp without temp

if temp <> "" then put y & return after accum

end repeat

answer accum

end mouseUp

There are two characters that prevent the filter command from doing its job: 
ASCII 91 (“[“) and ASCII 10, the return char.



Craig


> On Jan 24, 2024, at 12:51 PM, Craig Newman via use-livecode 
>  wrote:
> 
> Brian.
> 
> Nope. Those two chars pass through the filter, er, filtered.
> 
> Again, I did not test the entire character set.
> 
> Craig
> 
>> On Jan 24, 2024, at 11:05 AM, Brian Milby via use-livecode 
>>  wrote:
>> 
>> The only other two that would cause issues are ? and * which are single and 
>> multiple char wildcards respectively.
>> 
>> Brian Milby
>> br...@milby7.com
>> 
>>> On Jan 24, 2024, at 10:21 AM, Craig Newman via use-livecode 
>>>  wrote:
>>> 
>>> I did not test the ASCII set exhaustively, but the culprit is the char “[“ 
>>> (ASCII 91). Any other char (including “]”) in the string works correctly, 
>>> that is, nothing is left after the filter command executes.
>>> 
>>> I do not know enough to say whether that particular char  does something to 
>>> the filter command, which may use regex somehow in its inner workings.
>>> 
>>> Craig
>>> 
>>> Craig
>>> 
>>>> On Jan 23, 2024, at 9:45 PM, Brian Milby via use-livecode 
>>>>  wrote:
>>>> 
>>>> Not sure this is really a bug.  The default is to match a wildcardPattern. 
>>>>  If you want to match [ then you must use [[] in the pattern.
>>>> 
>>>> Brian Milby
>>>> br...@milby7.com
>>>> 
>>>>>> On Jan 23, 2024, at 9:02 PM, Neville Smythe via use-livecode 
>>>>>>  wrote:
>>>>> 
>>>>> Try this in the msg box:
>>>>> 
>>>>> put "aaa[bbb" into tStr; put line 1 of tStr into tLine; filter tStr 
>>>>> without tLine; put tStr
>>>>> I get (using MacOS, LC 9.6.11)
>>>>> 
>>>>> aaa[bbb
>>>>> 
>>>>> That is to say, the line is not filtered out.
>>>>> 
>>>>> And:
>>>>> 
>>>>> put "aaa[bbb" into tStr; filter tStr with tStr; put tStr
>>>>> 
>>>>> produces an empty string instead of the original string.
>>>>> 
>>>>> The bug occurs if the line contains the character “[“ anywhere; any lines 
>>>>> containing that character are ignored by both filter with and filter 
>>>>> without.
>>>>> 
>>>>> This is really serious, because I rely on the filter command a lot, as I 
>>>>> would think do many other developers!
>>>>> 
>>>>> Don’t know if it occurs with other characters, but I have never seen it 
>>>>> before. I discovered it when filtering lines with regular expressions. 
>>>>> Other special regexp characters I have tested do not trigger the bug.
>>>>> 
>>>>> Neville Smythe
>>>>> 
>>>>> 
>>>>> 
>>>>> ___
>>>>> 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
>> 
>> ___
>> 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: Nasty filter bug

Brian.

Nope. Those two chars pass through the filter, er, filtered.

Again, I did not test the entire character set.

Craig

> On Jan 24, 2024, at 11:05 AM, Brian Milby via use-livecode 
>  wrote:
> 
> The only other two that would cause issues are ? and * which are single and 
> multiple char wildcards respectively.
> 
> Brian Milby
> br...@milby7.com
> 
>> On Jan 24, 2024, at 10:21 AM, Craig Newman via use-livecode 
>>  wrote:
>> 
>> I did not test the ASCII set exhaustively, but the culprit is the char “[“ 
>> (ASCII 91). Any other char (including “]”) in the string works correctly, 
>> that is, nothing is left after the filter command executes.
>> 
>> I do not know enough to say whether that particular char  does something to 
>> the filter command, which may use regex somehow in its inner workings.
>> 
>> Craig
>> 
>> Craig
>> 
>>> On Jan 23, 2024, at 9:45 PM, Brian Milby via use-livecode 
>>>  wrote:
>>> 
>>> Not sure this is really a bug.  The default is to match a wildcardPattern.  
>>> If you want to match [ then you must use [[] in the pattern.
>>> 
>>> Brian Milby
>>> br...@milby7.com
>>> 
>>>>> On Jan 23, 2024, at 9:02 PM, Neville Smythe via use-livecode 
>>>>>  wrote:
>>>> 
>>>> Try this in the msg box:
>>>> 
>>>> put "aaa[bbb" into tStr; put line 1 of tStr into tLine; filter tStr 
>>>> without tLine; put tStr
>>>> I get (using MacOS, LC 9.6.11)
>>>> 
>>>> aaa[bbb
>>>> 
>>>> That is to say, the line is not filtered out.
>>>> 
>>>> And:
>>>> 
>>>> put "aaa[bbb" into tStr; filter tStr with tStr; put tStr
>>>> 
>>>> produces an empty string instead of the original string.
>>>> 
>>>> The bug occurs if the line contains the character “[“ anywhere; any lines 
>>>> containing that character are ignored by both filter with and filter 
>>>> without.
>>>> 
>>>> This is really serious, because I rely on the filter command a lot, as I 
>>>> would think do many other developers!
>>>> 
>>>> Don’t know if it occurs with other characters, but I have never seen it 
>>>> before. I discovered it when filtering lines with regular expressions. 
>>>> Other special regexp characters I have tested do not trigger the bug.
>>>> 
>>>> Neville Smythe
>>>> 
>>>> 
>>>> 
>>>> ___
>>>> 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
> 
> ___
> 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: Nasty filter bug

The only other two that would cause issues are ? and * which are single and 
multiple char wildcards respectively.

Brian Milby
br...@milby7.com

> On Jan 24, 2024, at 10:21 AM, Craig Newman via use-livecode 
>  wrote:
> 
> I did not test the ASCII set exhaustively, but the culprit is the char “[“ 
> (ASCII 91). Any other char (including “]”) in the string works correctly, 
> that is, nothing is left after the filter command executes.
> 
> I do not know enough to say whether that particular char  does something to 
> the filter command, which may use regex somehow in its inner workings.
> 
> Craig
> 
> Craig
> 
>> On Jan 23, 2024, at 9:45 PM, Brian Milby via use-livecode 
>>  wrote:
>> 
>> Not sure this is really a bug.  The default is to match a wildcardPattern.  
>> If you want to match [ then you must use [[] in the pattern.
>> 
>> Brian Milby
>> br...@milby7.com
>> 
>>>> On Jan 23, 2024, at 9:02 PM, Neville Smythe via use-livecode 
>>>>  wrote:
>>> 
>>> Try this in the msg box:
>>> 
>>> put "aaa[bbb" into tStr; put line 1 of tStr into tLine; filter tStr without 
>>> tLine; put tStr
>>> I get (using MacOS, LC 9.6.11)
>>> 
>>> aaa[bbb
>>> 
>>> That is to say, the line is not filtered out.
>>> 
>>> And:
>>> 
>>> put "aaa[bbb" into tStr; filter tStr with tStr; put tStr
>>> 
>>> produces an empty string instead of the original string.
>>> 
>>> The bug occurs if the line contains the character “[“ anywhere; any lines 
>>> containing that character are ignored by both filter with and filter 
>>> without.
>>> 
>>> This is really serious, because I rely on the filter command a lot, as I 
>>> would think do many other developers!
>>> 
>>> Don’t know if it occurs with other characters, but I have never seen it 
>>> before. I discovered it when filtering lines with regular expressions. 
>>> Other special regexp characters I have tested do not trigger the bug.
>>> 
>>> Neville Smythe
>>> 
>>> 
>>> 
>>> ___
>>> 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

___
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: Nasty filter bug

I did not test the ASCII set exhaustively, but the culprit is the char “[“ 
(ASCII 91). Any other char (including “]”) in the string works correctly, that 
is, nothing is left after the filter command executes.

I do not know enough to say whether that particular char  does something to the 
filter command, which may use regex somehow in its inner workings.

Craig

Craig

> On Jan 23, 2024, at 9:45 PM, Brian Milby via use-livecode 
>  wrote:
> 
> Not sure this is really a bug.  The default is to match a wildcardPattern.  
> If you want to match [ then you must use [[] in the pattern.
> 
> Brian Milby
> br...@milby7.com
> 
>> On Jan 23, 2024, at 9:02 PM, Neville Smythe via use-livecode 
>>  wrote:
>> 
>> Try this in the msg box:
>> 
>> put "aaa[bbb" into tStr; put line 1 of tStr into tLine; filter tStr without 
>> tLine; put tStr
>> I get (using MacOS, LC 9.6.11)
>> 
>> aaa[bbb
>> 
>> That is to say, the line is not filtered out.
>> 
>> And:
>> 
>> put "aaa[bbb" into tStr; filter tStr with tStr; put tStr
>> 
>> produces an empty string instead of the original string.
>> 
>> The bug occurs if the line contains the character “[“ anywhere; any lines 
>> containing that character are ignored by both filter with and filter without.
>> 
>> This is really serious, because I rely on the filter command a lot, as I 
>> would think do many other developers!
>> 
>> Don’t know if it occurs with other characters, but I have never seen it 
>> before. I discovered it when filtering lines with regular expressions. Other 
>> special regexp characters I have tested do not trigger the bug.
>> 
>> Neville Smythe
>> 
>> 
>> 
>> ___
>> 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: Nasty filter bug

2024-01-23 Thread Brian Milby via use-livecode

Not sure this is really a bug.  The default is to match a wildcardPattern.  If 
you want to match [ then you must use [[] in the pattern.

Brian Milby
br...@milby7.com

> On Jan 23, 2024, at 9:02 PM, Neville Smythe via use-livecode 
>  wrote:
> 
> Try this in the msg box:
> 
> put "aaa[bbb" into tStr; put line 1 of tStr into tLine; filter tStr without 
> tLine; put tStr
> I get (using MacOS, LC 9.6.11)
> 
> aaa[bbb
> 
> That is to say, the line is not filtered out.
> 
> And:
> 
> put "aaa[bbb" into tStr; filter tStr with tStr; put tStr
> 
> produces an empty string instead of the original string.
> 
> The bug occurs if the line contains the character “[“ anywhere; any lines 
> containing that character are ignored by both filter with and filter without.
> 
> This is really serious, because I rely on the filter command a lot, as I 
> would think do many other developers!
> 
> Don’t know if it occurs with other characters, but I have never seen it 
> before. I discovered it when filtering lines with regular expressions. Other 
> special regexp characters I have tested do not trigger the bug.
> 
> Neville Smythe
> 
> 
> 
> ___
> 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

Nasty filter bug

2024-01-23 Thread Neville Smythe via use-livecode

Try this in the msg box:

put "aaa[bbb" into tStr; put line 1 of tStr into tLine; filter tStr without 
tLine; put tStr
I get (using MacOS, LC 9.6.11)

aaa[bbb

That is to say, the line is not filtered out.

And:

put "aaa[bbb" into tStr; filter tStr with tStr; put tStr

produces an empty string instead of the original string.

The bug occurs if the line contains the character “[“ anywhere; any lines 
containing that character are ignored by both filter with and filter without.

This is really serious, because I rely on the filter command a lot, as I would 
think do many other developers!

Don’t know if it occurs with other characters, but I have never seen it before. 
I discovered it when filtering lines with regular expressions. Other special 
regexp characters I have tested do not trigger the bug.

Neville Smythe



___
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: Bug 23507 - LC Clipboard Polling Failure

2024-01-17 Thread Curry Kenworthy via use-livecode




Bernd:

> I then changed to 'fullClipboardData' instead of 'ClipboardData'
> and that worked for without a hitch for minutes.

Thanks, that may even have potential for a temp workaround!

It makes the Windows outcome more like Mac:
Glitches, but seems to reset a few seconds later, without LC restart.

So, "full" might be the ONLY reliable Clipboard access on Windows...

My test stack looks like a special case, but actually just simulates 
normal user copy and paste or poll over time.


(There is likewise an opposite LC bug, failing to COPY text from LC.
Haven't made a recipe/trigger stack for that one yet.)

Best wishes,

Curry Kenworthy

Radically Innovative Christian LiveCode Development
"PASSION for Elegant, Efficient Code!"
http://livecodeconsulting.com/

___
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: Bug 23507 - LC Clipboard Polling Failure

2024-01-17 Thread Niggemann, Bernd via use-livecode

Curry,

> Any progress to fix LC's Clipboard Polling Failure Bug?


I tried your code on MacOS Monterey using LC 9.6.11 and LC 10.0.0 DP-7.
I saw after a short time gibberish and at times empty clipboard content. No 
crash though.
I then changed to 'fullClipboardData' instead of 'ClipboardData' and that 
worked for without a hitch for minutes.

I realise that your main concern is Windows with crashes/freezes. But maybe 
that would help on Windows too.

Kind regards
Bernd
___
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: Bug 23507 - LC Clipboard Polling Failure

2024-01-16 Thread Curry Kenworthy via use-livecode




Paul:

> I have very limited time and resources and I'd like to spend MORE
> of it making new features for my products tha[n] fixing bugs that
> happen because a new macOS (or Windows) came out or a new version
> of Livecode or some combination breaks what was working.

Last month I wanted to post my Top 3 favorite list posts of 2023.
But only had 2 posts Behold, the 3rd! Thanks Paul.

I like that, and it perfectly sums up my experience for several years.
(I love some challenges and workarounds, but not a continual onslaught.)

Best wishes,

Curry Kenworthy

Radically Innovative Christian LiveCode Development
"PASSION for Elegant, Efficient Code!"
http://livecodeconsulting.com/

___
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: Bug 23507 - LC Clipboard Polling Failure

2024-01-16 Thread Paul Dupuis via use-livecode


Ralph,

Thanks for the tip. As I did into this problem, I'll give that a try.

I'm just getting tired of Apple and/or Livecode changing things so that 
code that DID work is then discovered NOT working any more.


I have very limited time and resources and I'd like to spend MORE of it 
making new features for my products that fixing bugs that happen because 
a new macOS (or Windows) came out or a new version of Livecode or some 
combination breaks what was working.


I always post on this list first in hopes someone else has see whatever 
issue I have run into and can say definitively look at this bug number 
in the LC Quality Center for both the issue and, ideally, a work-around.




On 1/16/2024 8:20 PM, Ralph DiMola via use-livecode wrote:

Too fast to look and see I was on the wrong thread. Meant to respond to
Paul's.

Woops...

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Curry Kenworthy via use-livecode
Sent: Tuesday, January 16, 2024 6:21 PM
To: use-livecode@lists.runrev.com
Cc: Curry Kenworthy
Subject: Re: Bug 23507 - LC Clipboard Polling Failure


Ralph:

  > do a send in time to the real resizing code.

Oh I fixed mine smooth as butter, but still blamed! First impressions...
(Plus some extra bias since I can't do phone/voice anymore, per health.)

But A: That's the other thread; This one is LC Clipboard Polling bug!

And B: Main context is Paul's situation, possibly an engine or OS issue.
(As mine was, but a different specific one. Required a big workaround.)

Thanks!

Best wishes,

Curry K.

___
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: Bug 23507 - LC Clipboard Polling Failure

2024-01-16 Thread Ralph DiMola via use-livecode

Too fast to look and see I was on the wrong thread. Meant to respond to
Paul's.

Woops...

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Curry Kenworthy via use-livecode
Sent: Tuesday, January 16, 2024 6:21 PM
To: use-livecode@lists.runrev.com
Cc: Curry Kenworthy
Subject: Re: Bug 23507 - LC Clipboard Polling Failure


Ralph:

 > do a send in time to the real resizing code.

Oh I fixed mine smooth as butter, but still blamed! First impressions...
(Plus some extra bias since I can't do phone/voice anymore, per health.)

But A: That's the other thread; This one is LC Clipboard Polling bug!

And B: Main context is Paul's situation, possibly an engine or OS issue.
(As mine was, but a different specific one. Required a big workaround.)

Thanks!

Best wishes,

Curry K.

___
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: Bug 23507 - LC Clipboard Polling Failure

2024-01-16 Thread Curry Kenworthy via use-livecode




Ralph:

> do a send in time to the real resizing code.

Oh I fixed mine smooth as butter, but still blamed! First impressions...
(Plus some extra bias since I can't do phone/voice anymore, per health.)

But A: That's the other thread; This one is LC Clipboard Polling bug!

And B: Main context is Paul's situation, possibly an engine or OS issue.
(As mine was, but a different specific one. Required a big workaround.)

Thanks!

Best wishes,

Curry K.

___
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: Bug 23507 - LC Clipboard Polling Failure

2024-01-16 Thread Ralph DiMola via use-livecode

Curry,

In your resizeStack handler do a send in time to the real resizing code. You
may find the even a short wait will fix it.

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Curry Kenworthy via use-livecode
Sent: Tuesday, January 16, 2024 12:16 PM
To: use-livecode@lists.runrev.com
Cc: Curry Kenworthy
Subject: Bug 23507 - LC Clipboard Polling Failure


Any progress to fix LC's Clipboard Polling Failure Bug?

https://quality.livecode.com/show_bug.cgi?id=23507

Needed this for an app.

Best wishes,

Curry K.

___
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

Bug 23507 - LC Clipboard Polling Failure

2024-01-16 Thread Curry Kenworthy via use-livecode




Any progress to fix LC's Clipboard Polling Failure Bug?

https://quality.livecode.com/show_bug.cgi?id=23507

Needed this for an app.

Best wishes,

Curry K.

___
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: 2 Qs about the OAuth2 bug fix in v10.x

2024-01-03 Thread matthias rebbe via use-livecode

What i forgot,

if this all is done by the oauth2.livecodescript, couldn't one then use that 
script in V9?


> Am 03.01.2024 um 21:54 schrieb matthias rebbe via use-livecode 
> :
> 
> According to the release notes of dp7 the corresponding bug is 24334
> 
> 
> https://quality.livecode.com/show_bug.cgi?id=24334
> 
> 
> 
>> Am 03.01.2024 um 21:35 schrieb ambassador--- via use-livecode 
>> :
>> 
>> The blog discussion re v10 mentions this fix to OAuth2:
>> 
>>  "OAuth2 redirect parameters are now correctly decoded"
>> 
>> I was unable to find the corresponding bug report for that item.
>> 
>> Does anyone here know the bug report ID for that?
>> 
>> And can anyone on the team confirm if this will be backported to the v9.x 
>> series?
>> 
>> Thanks in advance - 
>> 
>> --
>> Richard Gaskin
>> FourthWorld.com
>> 
>> ___
>> 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: 2 Qs about the OAuth2 bug fix in v10.x

2024-01-03 Thread matthias rebbe via use-livecode

According to the release notes of dp7 the corresponding bug is 24334


https://quality.livecode.com/show_bug.cgi?id=24334



> Am 03.01.2024 um 21:35 schrieb ambassador--- via use-livecode 
> :
> 
> The blog discussion re v10 mentions this fix to OAuth2:
> 
>   "OAuth2 redirect parameters are now correctly decoded"
> 
> I was unable to find the corresponding bug report for that item.
> 
> Does anyone here know the bug report ID for that?
> 
> And can anyone on the team confirm if this will be backported to the v9.x 
> series?
> 
> Thanks in advance - 
> 
> --
> Richard Gaskin
> FourthWorld.com
> 
> ___
> 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

2 Qs about the OAuth2 bug fix in v10.x

2024-01-03 Thread ambassador--- via use-livecode

The blog discussion re v10 mentions this fix to OAuth2:

   "OAuth2 redirect parameters are now correctly decoded"

I was unable to find the corresponding bug report for that item.

Does anyone here know the bug report ID for that?

And can anyone on the team confirm if this will be backported to the v9.x 
series?

Thanks in advance - 

--
Richard Gaskin
FourthWorld.com

___
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: Property Inspector bug for keys with commas in the key name

2023-11-06 Thread Curry Kenworthy via use-livecode


Mark, re Inspector and custom property names with commas:

> I agree its an annoyance - and is something which is resolvable

1. Great news! Because that code/data reality is hard to avoid:

- EVERY shipping LC app's stack has cRevStandaloneSettings ...
- If the IDE or app has build glitches, we need to check props -
- Right now, even VIEWING them with Inspector can CORRUPT data.

Likewise, you confirmed commas work with set[prop] and indirect syntax.
Thus, users do it - just like LC Ltd does; goose/gander - important fix.

2. Here's a set of 3 other Custom Property editor Scroll/Selection Bugs:

https://quality.livecode.com/show_bug.cgi?id=24391

Hat-trick to make the Inspector succeed at custom property editing -
Just need to fix the scrolling glitches and lost selections.

3. And YES to your proposal, thanks:

> an obvious syntactic extension would be allowing
> quoting of the property keyword: the "foo,bar,baz" of me.

Here's a "get" Request and "set" Bug report for reliably quoting custom 
property names:


https://quality.livecode.com/show_bug.cgi?id=24392

See the "Quoted Name Test" button for thorough code and results.

Best wishes,

Curry Kenworthy

Radically Innovative Christian LiveCode Development
"PASSION for Elegant, Efficient Code!"
http://livecodeconsulting.com/

___
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: Property Inspector bug for keys with commas in the key name

2023-11-05 Thread Mark Waddingham via use-livecode

Indeed you can indirect through a variable - but you can’t do, e.g:

get the foo,bar,baz of me

Which was my point :)

Warmest Regards,

Mark.

P.S. Of course an obvious syntactic extension would be allowing quoting of the 
property keyword: the “foo,bar,baz” of me.

Sent from my iPhone

> On 5 Nov 2023, at 16:14, Curry Kenworthy via use-livecode 
>  wrote:
> 
> 
> Mark:
> 
> > to access your custom properties with `the X of` syntax -
> > it is *this* kind of access which is *not* possible
> > if the custom property name is not an identifier
> 
> Discussion is perception - Code is reality:
> 
>   put "I,love,commas*etc" into X
>   set the X of me to "Hi, Mark!"
>   answer the X of me
> 
> https://quality.livecode.com/show_bug.cgi?id=23512
> 
> Best wishes,
> 
> Curry Kenworthy
> 
> Radically Innovative Christian LiveCode Development
> "PASSION for Elegant, Efficient Code!"
> http://livecodeconsulting.com/
> 
> ___
> 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: Property Inspector bug for keys with commas in the key name

2023-11-05 Thread Curry Kenworthy via use-livecode




Mark:

> to access your custom properties with `the X of` syntax -
> it is *this* kind of access which is *not* possible
> if the custom property name is not an identifier

Discussion is perception - Code is reality:

   put "I,love,commas*etc" into X
   set the X of me to "Hi, Mark!"
   answer the X of me

https://quality.livecode.com/show_bug.cgi?id=23512

Best wishes,

Curry Kenworthy

Radically Innovative Christian LiveCode Development
"PASSION for Elegant, Efficient Code!"
http://livecodeconsulting.com/

___
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: Property Inspector bug for keys with commas in the key name

2023-11-05 Thread Mark Waddingham via use-livecode


On 2023-11-03 20:21, Paul Dupuis via use-livecode wrote:
You do make a good point about the documentation regarding custom 
properties. Assuming people read the documentation. At the same time, 
you used to be able to use commas in custom property names. As Curry 
noted, Livecode even used to use them in the standalone setting 
properties, so the mothership set a precedence.


The user guide's comments are really good advice *if* you want to access 
your custom properties with `the X of` syntax - it is *this* kind of 
access which is *not* possible if the custom property name is not an 
identifier (i.e. something you can use as a variable or handler name). 
(Remember that you can set the 'current' custom property set of an 
object and use `the X of` syntax to access the keys of that too - and if 
you do that, then any non-identifier keys are similarly not accessible).


So we haven't set a precedent by using commas in custom property names - 
its in a custom property set *and* they are never accessed via `the X 
of` syntax (only via `the SET[X] of` syntax) - and with such things 
(where you are using the custom property set as an array of data) I 
don't think the rule applies.


It's not really a problem since I can do updates by script. It is more 
of just an annoyance.


I agree its an annoyance - and is something which is resolvable (i.e. by 
adding a variant of the hilitedElement property of the treeview with one 
which returns a sequence rather than a string).


Feel free to file a bug report about it and we'll put it on the list to 
look at.


Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Build Amazing Things

___
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: Property Inspector bug for keys with commas in the key name

2023-11-05 Thread Niggemann, Bernd via use-livecode

Hi Paul,

I forgot to add handler

editorUpdate

to the list that needs a 

"set the itemDelimiter to tab"

Kind regards
Bernd

___
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: Property Inspector bug for keys with commas in the key name

2023-11-05 Thread Niggemann, Bernd via use-livecode

Hi Paul,

I looked a bit further into the problem with commas in key names of custom 
properties.
It turns out that the widget "treeview" has the option to choose a delimiter 
for paths. Default is comma.

If you feel adventurous you could hack the properties inspector fairly easily 
to work with commas in the key names;

Recipe:

open any custom property in the PI

close the PI

Select from Menu "View": Show IDE Stacks in Lists

open Project Browser

Use the project browser to edit the script of 
com.livecode.pi.customprops.behavior

Now add to handler editorInitialize at the end

   -- more code
   set the pathDelimiter of widget 1 of me to tab -- add
end editorInitialize

Now add the line:

set the itemDelimiter to tab

to handlers:

setArrayDataOnPath
setArrayKeyOnPath
deleteArrayKeyOnPath
addArrayKeyOnPath
fetchArrayDataOnPath
keyChangedOnPath


To be sure you can do a search for "item" in the script and every handler that 
refers to "item" needs 

set the itemDelimiter to tab


Reopen the PI for a custom property containing comma in a key name and it 
should work to display key and value in PI and also lets you change the value.

If you want this change to be persistent for that particular version of LC you 
would have to save the changes to com.livecode.pi.customprops.behavior from the 
Script Editor.
Otherwise the next time you start that version of LC the changes would be gone.

I tested shortly and it worked for me. Maybe try this first on a LC version 
that is not your current working version.

I chose tab as delimiter since I doubt that tab will be used in a key name...


Kind regards
Bernd




___
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: Property Inspector bug for keys with commas in the key name

2023-11-03 Thread Paul Dupuis via use-livecode

Hi Bernd,

You do make a good point about the documentation regarding custom
properties. Assuming people read the documentation. At the same time,
you used to be able to use commas in custom property names. As Curry
noted, Livecode even used to use them in the standalone setting
properties, so the mothership set a precedence.

My problem is that I have stacks where commas were used because they
could be used and there was value to using them as evidenced by how
Livecode used them in the standalone settings. Now I can only edit them
via scripts rather than the current PI.

It's not really a problem since I can do updates by script. It is more
of just an annoyance.

Knowing that the current issue if the hilitedElement of the tree view
object, I won't bother trying to look for any quick fix I could make to
the PI code in the IDE. Thanks for the information.

On 11/3/2023 2:29 PM, Niggemann, Bernd via use-livecode wrote:

Hi Paul,

The problem with the comma in a customproperty name in the Properties Inspector (PI) arises because
the PI uses a treeview to display the customproperties. More specifically the
"hilitedElement" to retrieve the current selection and "hilitedElement" has the
form:
"A comma delimited list of array keys."

Now you have a comma in your customproperty name and at that point the PI is
confused as to what is the key and what is the value and fails to display both.

However I wonder if treeview or PI is to blame:

Page 145 of "Livecode User Guide" 9.6.10
Custom Property Names
The name of a custom property must consist of a single word and may contain any
combination of letters, digits, and underscores (_). The first character must
be either a letter or an underscore.

Page 113 of "Revolution User Guide 2.0" printed edition from 2004
Custom Property Names
The name of a custom property must consist of a single word and may contain any
combination of letters, digits, and underscores (_). The first character must
be either a letter or an underscore.

So I am afraid that treeview could not expect a comma in a customproperty name.

Kind regards
Bernd
___
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: Property Inspector bug for keys with commas in the key name

2023-11-03 Thread Curry Kenworthy via use-livecode




Bernd:

> "Livecode User Guide" 9.6.10 - Custom Property Names
> any combination of letters, digits, and underscores
> treeview could not expect a comma in a customproperty name.

Hi Y'all,

Anyone ever hear of the cRevStandaloneSettings?

Wonderful (official) prop set ... especially all the commas!

Best wishes,

Curry Kenworthy

Radically Innovative Christian LiveCode Development
"PASSION for Elegant, Efficient Code!"
http://livecodeconsulting.com/

___
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

Property Inspector bug for keys with commas in the key name

2023-11-03 Thread Niggemann, Bernd via use-livecode

Hi Paul,

The problem with the comma in a customproperty name in the Properties Inspector 
(PI) arises because the PI uses a treeview to display the customproperties. 
More specifically the "hilitedElement" to retrieve the current selection and 
"hilitedElement" has the form:
"A comma delimited list of array keys."

Now you have a comma in your customproperty name and at that point the PI is 
confused as to what is the key and what is the value and fails to display both.

However I wonder if treeview or PI is to blame:

Page 145 of "Livecode User Guide" 9.6.10
Custom Property Names
The name of a custom property must consist of a single word and may contain any 
combination of letters, digits, and underscores (_). The first character must 
be either a letter or an underscore.

Page 113 of "Revolution User Guide 2.0" printed edition from 2004
Custom Property Names
The name of a custom property must consist of a single word and may contain any 
combination of letters, digits, and underscores (_). The first character must 
be either a letter or an underscore.

So I am afraid that treeview could not expect a comma in a customproperty name.

Kind regards
Bernd
___
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: Property Inspector bug for keys with commas in the key name

2023-11-03 Thread Mike Kerner via use-livecode

ok, let's see. you got me distracted from real work:
if you're following along at home, in real time, look in
toolset->palettes->inspector->editors->com.livecode.pi.customprops.behavior.livecodescript

On Thu, Nov 2, 2023 at 6:02 PM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:

> This bug (https://quality.livecode.com/show_bug.cgi?id=23512) where a
> comma in the key name of an array prevents the Proerty Inspector from
> being able to edit the property just bit me again.
>
> I have a stack (for help) that extensively uses keys with commas (create
> prior to the Project Browser and new PI) that I can not edit except by
> script - which is a pain in the (you know what).
>
> Does anyone have an edit to the PI code for this OR an alternative PI
> that does not have this bug?
>
> ___
> 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: Property Inspector bug for keys with commas in the key name

2023-11-03 Thread Mike Kerner via use-livecode

no, but, i started to write a wiki on the PI/PE, which might help you to
get started in your search:
https://github.com/macMikey/LC-HACK/wiki/Property-Inspector

On Thu, Nov 2, 2023 at 6:02 PM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:

> This bug (https://quality.livecode.com/show_bug.cgi?id=23512) where a
> comma in the key name of an array prevents the Proerty Inspector from
> being able to edit the property just bit me again.
>
> I have a stack (for help) that extensively uses keys with commas (create
> prior to the Project Browser and new PI) that I can not edit except by
> script - which is a pain in the (you know what).
>
> Does anyone have an edit to the PI code for this OR an alternative PI
> that does not have this bug?
>
> ___
> 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

Property Inspector bug for keys with commas in the key name

2023-11-02 Thread Paul Dupuis via use-livecode

This bug (https://quality.livecode.com/show_bug.cgi?id=23512) where a 
comma in the key name of an array prevents the Proerty Inspector from 
being able to edit the property just bit me again.


I have a stack (for help) that extensively uses keys with commas (create 
prior to the Project Browser and new PI) that I can not edit except by 
script - which is a pain in the (you know what).


Does anyone have an edit to the PI code for this OR an alternative PI 
that does not have this bug?


___
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: sort bug

2023-09-07 Thread Bob Sneidar via use-livecode

I’ve always thought that an operator like “a list of…” might be handy. In this 
case a list of integers, so you could check to see if the list you want to sort 
is a valid list of integers.

Bob S


On Sep 7, 2023, at 9:02 AM, Brian Milby via use-livecode 
 wrote:

It seems the error/bug is related to the error being in the last value.  If you 
were to change the bug report to sort on the field itself, then the sort is 
performed but the answer does not execute.  If you clicked the button again, 
then the answer does show.  If you revert to the saved stack and add a valid 
value after the bad one, the answer works as expected with the bad value being 
first.

Brian Milby
br...@milby7.com<mailto:br...@milby7.com>

On Sep 6, 2023, at 10:31 PM, Geoff Canyon via use-livecode 
mailto:use-livecode@lists.runrev.com>> wrote:

From the original email:

If the function myVal encounters a run-time error (in the example if one of
the items is not a number) the sort command fails silently: the script
exits at that code line and the user is unaware that the sort (and the rest
of the handler) were not executed.


To be clear: the above is NOT what I'm seeing. Mark W says in the bug
report:

The 'sort ... by ...' command has always allowed the by expression to be
fault tolerant - if evaluating it generates a runtime error then the sort
key for that element is just taken to be the original element.

And that is what I'm seeing. For example, this code does not exit -- it
displays the answer dialog as if nothing out of the ordinary has happened:

on mouseUp
 sort lines of fld 1 numeric by sortVal(each)
 answer "done"
end mouseUp

function sortVal S
 return item 2 of S + item 3 of S
end sortVal

It seems to be sorting as Mark described: when the function fails, the
whole line is used for the sort. And that "fallback to the whole value
needs better documentation, and could lead to some truly dismal debugging
situations, but it doesn't seem like a bug to me.

The original report, if I were able to replicate it, would clearly be a bug.

___
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: sort bug

2023-09-07 Thread Bob Sneidar via use-livecode

I think it is putting all non-numeric values first as unsortable, then the 
sortable items next. This seems to be the case because:

put "b,4,2,a,3,6" into tList;sort items of tList numeric ascending;put tList

Results in:

b,a,2,3,4,6

This implies that the non-numeric items are not being sorted at all, just 
shuttled to the front of the line. 

Bob S


> On Sep 7, 2023, at 8:46 AM, Craig Newman via use-livecode 
>  wrote:
> 
> Bob,
> 
> If you remove the “numeric” the result is “2,3,4,6,a”.
> 
> To me this implies that ASCII values are used as the sortKey. But that begs 
> the issue why, as in your post, with “numeric” included, the “a” appears 
> first. What makes the “a” a lower "numeric" value than “2”?
> 
> Craig
> 
>> On Sep 7, 2023, at 11:19 AM, Bob Sneidar via use-livecode 
>>  wrote:
>> 
>> put "4,2,a,3,6" into tList;sort items of tList numeric ascending;put tList


___
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: sort bug

2023-09-07 Thread Brian Milby via use-livecode

It seems the error/bug is related to the error being in the last value.  If you 
were to change the bug report to sort on the field itself, then the sort is 
performed but the answer does not execute.  If you clicked the button again, 
then the answer does show.  If you revert to the saved stack and add a valid 
value after the bad one, the answer works as expected with the bad value being 
first.

Brian Milby
br...@milby7.com

> On Sep 6, 2023, at 10:31 PM, Geoff Canyon via use-livecode 
>  wrote:
> 
> From the original email:
> 
> If the function myVal encounters a run-time error (in the example if one of
> the items is not a number) the sort command fails silently: the script
> exits at that code line and the user is unaware that the sort (and the rest
> of the handler) were not executed.
> 
> 
> To be clear: the above is NOT what I'm seeing. Mark W says in the bug
> report:
> 
> The 'sort ... by ...' command has always allowed the by expression to be
> fault tolerant - if evaluating it generates a runtime error then the sort
> key for that element is just taken to be the original element.
> 
> And that is what I'm seeing. For example, this code does not exit -- it
> displays the answer dialog as if nothing out of the ordinary has happened:
> 
> on mouseUp
>   sort lines of fld 1 numeric by sortVal(each)
>   answer "done"
> end mouseUp
> 
> function sortVal S
>   return item 2 of S + item 3 of S
> end sortVal
> 
> It seems to be sorting as Mark described: when the function fails, the
> whole line is used for the sort. And that "fallback to the whole value
> needs better documentation, and could lead to some truly dismal debugging
> situations, but it doesn't seem like a bug to me.
> 
> The original report, if I were able to replicate it, would clearly be a bug.
> 
>> On Sat, Sep 2, 2023 at 8:19 PM neville smythe via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> 
>> Geoff Canyon wrote (after a bravura  display of how many different
>> ways there are to do things in LC!) :
>> 
>> And the function sort also sorts based on a negative infinity value
>> for
>> 
>> errors. I'm not sure I'd consider that a bug.
>> 
>> Hmm. I would. The sortKey function should tolerate any sort of
>> run-time error? But anyway that's not the issue. The bug I see is that
>> the sort command exits its containing handler - actually I presume the
>> sortKey function exits to top - without throwing an error, so nothing
>> beyond that line is executed. This creates a very difficult problem
>> to track down, since the code appears to be executing correctly, until
>> something falls over or a file gets corrupted much later because some
>> stuff never happened.
>> 
>> Of course one should always validate data, particularly if it's not
>> your own data. In this case it was my own data! Moreover I had thought
>> I had checked for invalid cases, just hadn't checked all possible
>> kinds of invalid data (the sortKey was rather more complicated than
>> the one I used for illustration).
>> 
>> Neville
>> 
>> -
>> Email sent using Optus Webmail
>> ___
>> 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: sort bug

2023-09-07 Thread Craig Newman via use-livecode

Bob,

If you remove the “numeric” the result is “2,3,4,6,a”.

To me this implies that ASCII values are used as the sortKey. But that begs the 
issue why, as in your post, with “numeric” included, the “a” appears first. 
What makes the “a” a lower "numeric" value than “2”?

Craig

> On Sep 7, 2023, at 11:19 AM, Bob Sneidar via use-livecode 
>  wrote:
> 
> put "4,2,a,3,6" into tList;sort items of tList numeric ascending;put tList

___
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: sort bug

2023-09-07 Thread Bob Sneidar via use-livecode

For me, 

put "4,2,a,3,6" into tList;sort items of tList numeric ascending;put tList
Results in: 
a,2,3,4,6

Bob S


> On Sep 6, 2023, at 7:29 PM, Geoff Canyon via use-livecode 
>  wrote:
> 
> From the original email:
> 
> If the function myVal encounters a run-time error (in the example if one of
> the items is not a number) the sort command fails silently: the script
> exits at that code line and the user is unaware that the sort (and the rest
> of the handler) were not executed.
> 
> 
> To be clear: the above is NOT what I'm seeing. Mark W says in the bug
> report:
> 
> The 'sort ... by ...' command has always allowed the by expression to be
> fault tolerant - if evaluating it generates a runtime error then the sort
> key for that element is just taken to be the original element.
> 
> And that is what I'm seeing. For example, this code does not exit -- it
> displays the answer dialog as if nothing out of the ordinary has happened:
> 
> on mouseUp
>   sort lines of fld 1 numeric by sortVal(each)
>   answer "done"
> end mouseUp
> 
> function sortVal S
>   return item 2 of S + item 3 of S
> end sortVal
> 
> It seems to be sorting as Mark described: when the function fails, the
> whole line is used for the sort. And that "fallback to the whole value
> needs better documentation, and could lead to some truly dismal debugging
> situations, but it doesn't seem like a bug to me.
> 
> The original report, if I were able to replicate it, would clearly be a bug.



___
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: Sort bug and also multilevel sorting

2023-09-07 Thread Craig Newman via use-livecode

Neville.

My example was only to show that the sort command still maintains the ability 
to accept concatenated sort criteria. This allows a single line of code to do 
the work, and obviates the need for multiple sorts.  In that sense it was a bad 
example to use character "places" in a string. This would not be an issue when 
using an explicit delimiter of some sort, typically what any sane coder would 
automatically do.

Padding with zeros or spaces is the sort of kludge even I would blanch at.

Craig

> On Sep 6, 2023, at 7:57 PM, Neville Smythe via use-livecode 
>  wrote:
> 
> Ralph: Interesting. Your code works as you present it, sorting the given 
> items by the sortkey function f1 which adds 1 to each item. I do get the 
> “sorting failed” dialog.
> 
> But if I try the same thing using myVal modified as you suggest, which adds 
> the first and second items of each line of data and then adds 1 to the global 
> s1, I get the bug I reported: the handler simply exits without showing either 
> the “sorting failed” or the “Done” answer dialog.
> 
> I would have thought the two methods would generate the same error code, an 
> incorrect operand in a sum, so this is strange! The function definitely 
> returns on the error line, the value of s1 is not changed in the next line in 
> either your f1 or my myVal. So perhaps the bug occurs when the processing 
> returns to the sort code. Not something we can solve here, one for the 
> engineers to sort out (!)
> 
> Mark Waddingham says the sortKey function is intended to be tolerant of 
> errors, simply returning the original value of ‘each’ - in your case each 
> item, in my case each line. So it should either 
> 
> 1. Continue with the (undocumented) sort order  OR 
> 
> 2a. exit to top AND 2b. drop into the debugger/errorDialog. In my example it 
> is doing  2a but not 2b.
> 
> Craig: The missing bit is that your method won’t work if the integers you are 
> sorting by having different string lengths
> 
> The lines
> 2,7
> 1,99
> 
> should, when sorted by numeric ascending (item 1 of each, item 2 of each) - 
> which would be the appropriate syntax for a multilevel sort tho not in LC - 
> result in
> 1.99
> 2,7
> 
> But if sorted by (item 1 of each & item 2 of each) - which concatenates as 
> strings - gives sort keys 199 and 27 to result in
> 2,7
> 1,99
> This can be fixed by formatting the numbers  so they have the same length by 
> padding with 0s, as MW noted. Once they have the same length you could 
> actually sort lexically which may be a lot faster than sorting numerically 
> (although my guess is using 2 separate sorts may be faster still at least for 
> short lists).
> 
> The concatenation method also won’t work if sorting real numbers:
> 1.0,0.2
> 1.0,0.1
> since after concatenation the second decimal place would be ignored in a 
> numeric sort.
> 
> 
> Neville Smythe
> 
> 
> 
> 
> ___
> 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: sort bug

2023-09-06 Thread Geoff Canyon via use-livecode

From the original email:

If the function myVal encounters a run-time error (in the example if one of
the items is not a number) the sort command fails silently: the script
exits at that code line and the user is unaware that the sort (and the rest
of the handler) were not executed.

To be clear: the above is NOT what I'm seeing. Mark W says in the bug
report:

The 'sort ... by ...' command has always allowed the by expression to be
fault tolerant - if evaluating it generates a runtime error then the sort
key for that element is just taken to be the original element.

And that is what I'm seeing. For example, this code does not exit -- it
displays the answer dialog as if nothing out of the ordinary has happened:

on mouseUp
   sort lines of fld 1 numeric by sortVal(each)
   answer "done"
end mouseUp

function sortVal S
   return item 2 of S + item 3 of S
end sortVal

It seems to be sorting as Mark described: when the function fails, the
whole line is used for the sort. And that "fallback to the whole value
needs better documentation, and could lead to some truly dismal debugging
situations, but it doesn't seem like a bug to me.

The original report, if I were able to replicate it, would clearly be a bug.

On Sat, Sep 2, 2023 at 8:19 PM neville smythe via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Geoff Canyon wrote (after a bravura  display of how many different
> ways there are to do things in LC!) :
>
> And the function sort also sorts based on a negative infinity value
> for
>
> errors. I'm not sure I'd consider that a bug.
>
> Hmm. I would. The sortKey function should tolerate any sort of
> run-time error? But anyway that's not the issue. The bug I see is that
> the sort command exits its containing handler - actually I presume the
> sortKey function exits to top - without throwing an error, so nothing
>  beyond that line is executed. This creates a very difficult problem
> to track down, since the code appears to be executing correctly, until
> something falls over or a file gets corrupted much later because some
> stuff never happened.
>
> Of course one should always validate data, particularly if it's not
> your own data. In this case it was my own data! Moreover I had thought
> I had checked for invalid cases, just hadn't checked all possible
> kinds of invalid data (the sortKey was rather more complicated than
> the one I used for illustration).
>
> Neville
>
> -
> Email sent using Optus Webmail
> ___
> 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: Sort bug and also multilevel sorting

2023-09-06 Thread Neville Smythe via use-livecode

Ralph: Interesting. Your code works as you present it, sorting the given items 
by the sortkey function f1 which adds 1 to each item. I do get the “sorting 
failed” dialog.

But if I try the same thing using myVal modified as you suggest, which adds the 
first and second items of each line of data and then adds 1 to the global s1, I 
get the bug I reported: the handler simply exits without showing either the 
“sorting failed” or the “Done” answer dialog.

I would have thought the two methods would generate the same error code, an 
incorrect operand in a sum, so this is strange! The function definitely returns 
on the error line, the value of s1 is not changed in the next line in either 
your f1 or my myVal. So perhaps the bug occurs when the processing returns to 
the sort code. Not something we can solve here, one for the engineers to sort 
out (!)

Mark Waddingham says the sortKey function is intended to be tolerant of errors, 
simply returning the original value of ‘each’ - in your case each item, in my 
case each line. So it should either 

1. Continue with the (undocumented) sort order  OR 

2a. exit to top AND 2b. drop into the debugger/errorDialog. In my example it is 
doing  2a but not 2b.

Craig: The missing bit is that your method won’t work if the integers you are 
sorting by having different string lengths

The lines
2,7
1,99

should, when sorted by numeric ascending (item 1 of each, item 2 of each) - 
which would be the appropriate syntax for a multilevel sort tho not in LC - 
result in
1.99
2,7

But if sorted by (item 1 of each & item 2 of each) - which concatenates as 
strings - gives sort keys 199 and 27 to result in
2,7
1,99
This can be fixed by formatting the numbers  so they have the same length by 
padding with 0s, as MW noted. Once they have the same length you could actually 
sort lexically which may be a lot faster than sorting numerically (although my 
guess is using 2 separate sorts may be faster still at least for short lists).

The concatenation method also won’t work if sorting real numbers:
1.0,0.2
1.0,0.1
since after concatenation the second decimal place would be ignored in a 
numeric sort.


Neville Smythe




___
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: sort bug

2023-09-02 Thread neville smythe via use-livecode

Geoff Canyon wrote (after a bravura  display of how many different
ways there are to do things in LC!) :

And the function sort also sorts based on a negative infinity value
for

errors. I'm not sure I'd consider that a bug.

Hmm. I would. The sortKey function should tolerate any sort of
run-time error? But anyway that's not the issue. The bug I see is that
the sort command exits its containing handler - actually I presume the
sortKey function exits to top - without throwing an error, so nothing
 beyond that line is executed. This creates a very difficult problem
to track down, since the code appears to be executing correctly, until
something falls over or a file gets corrupted much later because some
stuff never happened. 

Of course one should always validate data, particularly if it's not
your own data. In this case it was my own data! Moreover I had thought
I had checked for invalid cases, just hadn't checked all possible
kinds of invalid data (the sortKey was rather more complicated than
the one I used for illustration).

Neville

-
Email sent using Optus Webmail
___
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: Sort bug

2023-09-01 Thread Geoff Canyon via use-livecode

With 9.6.9 on a mac and a field where the second and third items of each
line are numbers:

   sort lines of fld 1 numeric by item 2 of each + item 3 of each -- works
   sort lines of fld 1 numeric by value(item 2 of each + item 3 of each) --
works
   sort lines of fld 1 numeric by merge("[[item 2 of each + item 3 of
each]]") -- works

and

on mouseUp
   sort lines of fld 1 numeric by sortVal(each)
end mouseUp

function sortVal S
   return item 2 of S + item 3 of S
end sortVal

works.

I haven't checked, but I'd guess that performance degrades with each
further method.

They all work if one or both of the items are empty.

If there is an entry that has a non-numeric value in item 2 or 3:

   sort lines of fld 1 numeric by item 2 of each + item 3 of each --
partially sorts and throws an error
   sort lines of fld 1 numeric by value(item 2 of each + item 3 of each) --
partially sorts and throws an error
   sort lines of fld 1 numeric by merge("[[item 2 of each + item 3 of
each]]") -- surprisingly, works -- error lines are seemingly sorted with a
value of negative infinity?

And the function sort also sorts based on a negative infinity value for
errors. I'm not sure I'd consider that a bug.

And this works:

   sort lines of fld 1 numeric by merge("")

And of course sorting by this function does the same thing:

function sortVal S
   if item 2 of S is not a number or item 3 of S is not a number then
return 0
   return item 2 of S + item 3 of S
end sortVal



On Thu, Aug 31, 2023 at 9:30 PM Brian Milby via use-livecode <
use-livecode@lists.runrev.com> wrote:

> I just tried this in 10dp5 and the sort didn’t completely bail (it put the
> error value first) but it did error when including inline (as in the bug
> report).  If I add a try, then it will stop on the throw.  Not sure how
> much this would slow down execution though.
>
> function myVal pStr
>local tResult
>try
>   put item 1 of pStr + item 2 of pStr into tResult
>catch errorVariable
>   throw "Bad data"
>end try
>return tResult
> end myVal
>
> Brian Milby
> br...@milby7.com
>
> > On Aug 31, 2023, at 7:53 PM, Alex Tweedly via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > 
> >> On 01/09/2023 00:37, Bob Sneidar via use-livecode wrote:
> >> The function is adding the value of two chunks together and returning
> the result. How does that even compute? Unless the + operator is doing
> something totally different here…
> >
> > The code said:
> >
> >> sort lines tVariable by myVal(each)
> >>
> >> where the function is for example
> >>
> >> function myVal pStr
> >>return item 1 of pStr + item 2 of pStr
> >> end myval
> > since it's sorting the lines of the container, it calls the custom
> function with each line in turn. The function simply adds together the
> first two items from the passed-in line, and returns that. The returned
> value is associated with the corresponding line - and then the container is
> sorted by those associated values.
> >
> > This works fine if the input variable is well formatted (i.e. first and
> second items of each line are numeric), but fails to give an error when
> something goes wrong - such as a non-numeric item.
> >
> > (and, yes - the dictionary description is misleading, if not simply
> incorrect. However, the "Tip" at the end describes the use of ustom
> functions).
> >
> > Alex.
> >
> >
> > ___
> > 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: Sort bug

2023-08-31 Thread Brian Milby via use-livecode

I just tried this in 10dp5 and the sort didn’t completely bail (it put the 
error value first) but it did error when including inline (as in the bug 
report).  If I add a try, then it will stop on the throw.  Not sure how much 
this would slow down execution though.

function myVal pStr
   local tResult
   try
  put item 1 of pStr + item 2 of pStr into tResult
   catch errorVariable
  throw "Bad data"
   end try
   return tResult
end myVal

Brian Milby
br...@milby7.com

> On Aug 31, 2023, at 7:53 PM, Alex Tweedly via use-livecode 
>  wrote:
> 
> 
>> On 01/09/2023 00:37, Bob Sneidar via use-livecode wrote:
>> The function is adding the value of two chunks together and returning the 
>> result. How does that even compute? Unless the + operator is doing something 
>> totally different here…
> 
> The code said:
> 
>> sort lines tVariable by myVal(each)
>> 
>> where the function is for example
>> 
>> function myVal pStr
>>return item 1 of pStr + item 2 of pStr
>> end myval
> since it's sorting the lines of the container, it calls the custom function 
> with each line in turn. The function simply adds together the first two items 
> from the passed-in line, and returns that. The returned value is associated 
> with the corresponding line - and then the container is sorted by those 
> associated values.
> 
> This works fine if the input variable is well formatted (i.e. first and 
> second items of each line are numeric), but fails to give an error when 
> something goes wrong - such as a non-numeric item.
> 
> (and, yes - the dictionary description is misleading, if not simply 
> incorrect. However, the "Tip" at the end describes the use of ustom 
> functions).
> 
> Alex.
> 
> 
> ___
> 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: Sort bug

2023-08-31 Thread Alex Tweedly via use-livecode



On 01/09/2023 00:37, Bob Sneidar via use-livecode wrote:

The function is adding the value of two chunks together and returning the 
result. How does that even compute? Unless the + operator is doing something 
totally different here…


The code said:


sort lines tVariable by myVal(each)

where the function is for example

function myVal pStr
return item 1 of pStr + item 2 of pStr
end myval
since it's sorting the lines of the container, it calls the custom 
function with each line in turn. The function simply adds together the 
first two items from the passed-in line, and returns that. The returned 
value is associated with the corresponding line - and then the container 
is sorted by those associated values.


This works fine if the input variable is well formatted (i.e. first and 
second items of each line are numeric), but fails to give an error when 
something goes wrong - such as a non-numeric item.


(and, yes - the dictionary description is misleading, if not simply 
incorrect. However, the "Tip" at the end describes the use of ustom 
functions).


Alex.


___
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: Sort bug

2023-08-31 Thread Bob Sneidar via use-livecode

The function is adding the value of two chunks together and returning the 
result. How does that even compute? Unless the + operator is doing something 
totally different here…

Bob S


On Aug 31, 2023, at 3:38 PM, J. Landman Gay via use-livecode 
 wrote:

Actually, the syntax is correct. It uses a custom sort function. The function 
call includes the "each" which means it passes the correct parameter to the 
custom function, which then acts on it and sends the result back to the calling 
handler for sorting. It's a nice way to customize the built-in sort. You can do 
some pretty extravagant things with it.


On 8/31/23 10:25 AM, Bob Sneidar via use-livecode wrote:


___
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: Sort bug

2023-08-31 Thread J. Landman Gay via use-livecode

Actually, the syntax is correct. It uses a custom sort function. The function call includes the 
"each" which means it passes the correct parameter to the custom function, which then acts on 
it and sends the result back to the calling handler for sorting. It's a nice way to customize 
the built-in sort. You can do some pretty extravagant things with it.



On 8/31/23 10:25 AM, Bob Sneidar via use-livecode wrote:

To be more clear, the argument to “by” needs to be a chunk statement, not a 
value, followed by “of each”. Your function *might* work if you returned the 
chunk expression instead of the actual value the chunk resolves to.

But why? I am not sure what the myVal() function accomplishes. Does the chunk 
expression change on the fly? Even so, pStr needs to be a list of numbers 
because you are adding them together, so it won’t return a chunk expression.

Your method as it stands would resolve to “sort lines tVariable by 3” when it 
needs to resolve to something like “sort lines of tVariable by item 3 of each”.

Further it looks like you are sorting by multiple items. You cannot do that in 
one statement. Instead run multiple sorts, by the last element first, down to 
the first element.

Bob S



On Aug 31, 2023, at 8:06 AM, Bob Sneidar via use-livecode 
 wrote:

I think you have to append “of each”. Sort lines of tVar by item 3 of each

Bob S



On Aug 30, 2023, at 9:11 PM, Neville Smythe via use-livecode 
 wrote:

There is a bug in sorting a container using a function, as in

sort lines tVariable by myVal(each)

where the function is for example

function myVal pStr
   return item 1 of pStr + item 2 of pStr
end myval

If the function myVal encounters a run-time error (in the example if one of the 
items is not a number) the sort command fails silently: the script exits at 
that code line and the user is unaware that the sort (and the rest of the 
handler) were not executed.

If you sort directly with

sort lines tVariable by (item 1 of pStr + item 2 of pStr)

the handler will throw an error dialog, as expected.

QC has confirmed this is a bug ( bug 24321 
<https://quality.livecode.com/show_bug.cgi?id=24321> ) that evidently has been 
around for a long time.

Neville Smythe



___
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


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
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: Sort bug

2023-08-31 Thread Bob Sneidar via use-livecode

To be more clear, the argument to “by” needs to be a chunk statement, not a 
value, followed by “of each”. Your function *might* work if you returned the 
chunk expression instead of the actual value the chunk resolves to. 

But why? I am not sure what the myVal() function accomplishes. Does the chunk 
expression change on the fly? Even so, pStr needs to be a list of numbers 
because you are adding them together, so it won’t return a chunk expression. 

Your method as it stands would resolve to “sort lines tVariable by 3” when it 
needs to resolve to something like “sort lines of tVariable by item 3 of each”. 

Further it looks like you are sorting by multiple items. You cannot do that in 
one statement. Instead run multiple sorts, by the last element first, down to 
the first element. 

Bob S

> On Aug 31, 2023, at 8:06 AM, Bob Sneidar via use-livecode 
>  wrote:
> 
> I think you have to append “of each”. Sort lines of tVar by item 3 of each
> 
> Bob S
> 
> 
>> On Aug 30, 2023, at 9:11 PM, Neville Smythe via use-livecode 
>>  wrote:
>> 
>> There is a bug in sorting a container using a function, as in
>> 
>> sort lines tVariable by myVal(each)
>> 
>> where the function is for example
>> 
>> function myVal pStr
>>   return item 1 of pStr + item 2 of pStr
>> end myval
>> 
>> If the function myVal encounters a run-time error (in the example if one of 
>> the items is not a number) the sort command fails silently: the script exits 
>> at that code line and the user is unaware that the sort (and the rest of the 
>> handler) were not executed.
>> 
>> If you sort directly with
>> 
>> sort lines tVariable by (item 1 of pStr + item 2 of pStr)
>> 
>> the handler will throw an error dialog, as expected.
>> 
>> QC has confirmed this is a bug ( bug 24321 
>> <https://quality.livecode.com/show_bug.cgi?id=24321> ) that evidently has 
>> been around for a long time.
>> 
>> Neville Smythe
>> 
>> 
>> 
>> ___
>> 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: Sort bug

2023-08-31 Thread Bob Sneidar via use-livecode

I think you have to append “of each”. Sort lines of tVar by item 3 of each

Bob S


> On Aug 30, 2023, at 9:11 PM, Neville Smythe via use-livecode 
>  wrote:
> 
> There is a bug in sorting a container using a function, as in
> 
> sort lines tVariable by myVal(each)
> 
> where the function is for example
> 
> function myVal pStr
>return item 1 of pStr + item 2 of pStr
> end myval
> 
> If the function myVal encounters a run-time error (in the example if one of 
> the items is not a number) the sort command fails silently: the script exits 
> at that code line and the user is unaware that the sort (and the rest of the 
> handler) were not executed.
> 
> If you sort directly with
> 
> sort lines tVariable by (item 1 of pStr + item 2 of pStr)
> 
> the handler will throw an error dialog, as expected.
> 
> QC has confirmed this is a bug ( bug 24321 
> <https://quality.livecode.com/show_bug.cgi?id=24321> ) that evidently has 
> been around for a long time.
> 
> Neville Smythe
> 
> 
> 
> ___
> 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

Sort bug

2023-08-30 Thread Neville Smythe via use-livecode

There is a bug in sorting a container using a function, as in

sort lines tVariable by myVal(each)

where the function is for example

function myVal pStr
return item 1 of pStr + item 2 of pStr
end myval

If the function myVal encounters a run-time error (in the example if one of the 
items is not a number) the sort command fails silently: the script exits at 
that code line and the user is unaware that the sort (and the rest of the 
handler) were not executed.

If you sort directly with

sort lines tVariable by (item 1 of pStr + item 2 of pStr)

the handler will throw an error dialog, as expected.

QC has confirmed this is a bug ( bug 24321 
<https://quality.livecode.com/show_bug.cgi?id=24321> ) that evidently has been 
around for a long time.

Neville Smythe



___
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: Bug or...? Native Querying

2023-08-07 Thread Bob Sneidar via use-livecode

Final correction and then I’ll shut up. Should have read

…where custid = 56 AND fileversion = (select max(t2.fileversion) from files t2 
where t2.filename = t1.filename)

MAN that is complicated!

Bob S


On Aug 7, 2023, at 4:01 PM, Bob Sneidar  wrote:

 I spoke too soon. I appended some SQL onto the initial query and there 
was an error in the SQL. I used

...where custid = 56 AND fileversion = (select max(fileversion) from files t2 
where t2.filename = t1.filename)

I should have used

...where custid = 56 AND fileversion = (select max(t1.fileversion) from files 
t2 where t2.filename = t1.filename)

I was making an ambiguous reference to fileversion. Odd that the SQL ran 
anyway. Apparently if the reference is inside a function, mySQL does not balk!

Bob S



On Aug 7, 2023, at 3:48 PM, Bob Sneidar via use-livecode 
 wrote:

I have code that uses the native API for SQL (as opposed to sqlYoga) because I 
have to do some joining that I do not know how to do with sqlYoga. The query 
string looks like this:

select 
fileid,filename,fileversion,filecategory,custid,siteid,deviceid,serviceid,softwareid,parentidlist,filemodified,tempfilemodified,tmpfilesmodified,checkoutid,checkoutname,checkoutpath,rfapath,lastupdate,updateby
from files t1
where custid = 56;

When I execute this query in mySQLWorkbench, I get 6 records. When I use the 
native API:

put revQueryDatabase( tDBID, tSQL) into tCursor

Then I get the revNumberOfRecords(tCursor), but it’s only 5!

The same query gets 6 using mySQLWorkbench and only 5 are counted in the cursor!

Please tell my I haven’t stumbled across a Lex Luther universe!

Bob S


___
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: Bug or...? Native Querying

2023-08-07 Thread Bob Sneidar via use-livecode

 I spoke too soon. I appended some SQL onto the initial query and there 
was an error in the SQL. I used

...where custid = 56 AND fileversion = (select max(fileversion) from files t2 
where t2.filename = t1.filename)

I should have used

...where custid = 56 AND fileversion = (select max(t1.fileversion) from files 
t2 where t2.filename = t1.filename)

I was making an ambiguous reference to fileversion. Odd that the SQL ran 
anyway. Apparently if the reference is inside a function, mySQL does not balk!

Bob S



On Aug 7, 2023, at 3:48 PM, Bob Sneidar via use-livecode 
 wrote:

I have code that uses the native API for SQL (as opposed to sqlYoga) because I 
have to do some joining that I do not know how to do with sqlYoga. The query 
string looks like this:

select 
fileid,filename,fileversion,filecategory,custid,siteid,deviceid,serviceid,softwareid,parentidlist,filemodified,tempfilemodified,tmpfilesmodified,checkoutid,checkoutname,checkoutpath,rfapath,lastupdate,updateby
from files t1
where custid = 56;

When I execute this query in mySQLWorkbench, I get 6 records. When I use the 
native API:

put revQueryDatabase( tDBID, tSQL) into tCursor

Then I get the revNumberOfRecords(tCursor), but it’s only 5!

The same query gets 6 using mySQLWorkbench and only 5 are counted in the cursor!

Please tell my I haven’t stumbled across a Lex Luther universe!

Bob S

___
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

Bug or...? Native Querying

2023-08-07 Thread Bob Sneidar via use-livecode

I have code that uses the native API for SQL (as opposed to sqlYoga) because I 
have to do some joining that I do not know how to do with sqlYoga. The query 
string looks like this: 

select 
fileid,filename,fileversion,filecategory,custid,siteid,deviceid,serviceid,softwareid,parentidlist,filemodified,tempfilemodified,tmpfilesmodified,checkoutid,checkoutname,checkoutpath,rfapath,lastupdate,updateby
 
from files t1 
where custid = 56;

When I execute this query in mySQLWorkbench, I get 6 records. When I use the 
native API: 

put revQueryDatabase( tDBID, tSQL) into tCursor

Then I get the revNumberOfRecords(tCursor), but it’s only 5!

The same query gets 6 using mySQLWorkbench and only 5 are counted in the 
cursor! 

Please tell my I haven’t stumbled across a Lex Luther universe! 

Bob S

___
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

Stop using font file bug

2023-03-25 Thread Neville Smythe via use-livecode

I have at least got around to filing a bug report about the “stop using font 
file” bug discovered in my cross-platform text issues investigation, life 
having intervened in the last few months.
Bug 24151 <https://quality.livecode.com/show_bug.cgi?id=24151> Stop Using font 
bug

I have also file an enhancement request for text baselines (GET SET and a 
fixedBaselIne feature for fields).
Bug 24152 <https://quality.livecode.com/show_bug.cgi?id=24152> textbaseline 
enhancement request


Those who came in late can read my article in
https://www.dropbox.com/sh/s3t9fwdij9cfxqh/AAD5nfbjHQwG2aIE3oZljEPsa?dl=0 
<https://www.dropbox.com/sh/s3t9fwdij9cfxqh/AAD5nfbjHQwG2aIE3oZljEPsa?dl=0>
There is also an updated version of the font metrics database in the same folder

Neville Smythe




___
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: Bug in browser widget

I have now discovered that this probably was related to MacOS 13.0. Having 
upgraded the OS to 13.2.1 solved the problem on the affected machine.

> 16. mar. 2023 kl. 19:07 skrev Tore Nilsen :
> 
> Hi Matthias, thanks for your interest in this ! I have been trying to solve 
> the problem myself and I have discovered that the problem only occurs on one 
> of my Macs. Unfortunately it is my main machine, but as long as I can get it 
> to work on the other machines I can always live with the situation for now.
> 
> Best regards
> Tore
> 
>> 16. mar. 2023 kl. 13:31 skrev matthias rebbe via use-livecode 
>> :
>> 
>> Tore,
>> do you have a url i could try?
>> 
>> Tried here with a page that has Youtube videos embedded and could not 
>> reproduce the error with LC 9.6.9RC2 and 10DP4 on macOS 13.2.1
>> 
>> 
>> 
>>> Am 16.03.2023 um 10:44 schrieb Tore Nilsen via use-livecode 
>>> :
>>> 
>>> I have come across a bug in the browser widget. The browser will not show 
>>> any video when the video is embedded into the web page. The poster image 
>>> and the thumbnail images will display properly, but once the videoplayer is 
>>> started the screen goes blank. The player will indeed play and the sound 
>>> from the video can be heard! Videos that are displayed using the video-tag 
>>> in the html file seems to work OK.
>>> 
>>> Are there anyone else who has the same experience? I am on MacOS 13.0 and 
>>> LC 10 dp 3 and dp 4
>>> 
>>> Best regards
>>> Tore Nilsen
>>> ___
>>> 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: Bug in browser widget

Hi Matthias, thanks for your interest in this ! I have been trying to solve the 
problem myself and I have discovered that the problem only occurs on one of my 
Macs. Unfortunately it is my main machine, but as long as I can get it to work 
on the other machines I can always live with the situation for now.

Best regards
Tore

> 16. mar. 2023 kl. 13:31 skrev matthias rebbe via use-livecode 
> :
> 
> Tore,
> do you have a url i could try?
> 
> Tried here with a page that has Youtube videos embedded and could not 
> reproduce the error with LC 9.6.9RC2 and 10DP4 on macOS 13.2.1
> 
> 
> 
>> Am 16.03.2023 um 10:44 schrieb Tore Nilsen via use-livecode 
>> :
>> 
>> I have come across a bug in the browser widget. The browser will not show 
>> any video when the video is embedded into the web page. The poster image and 
>> the thumbnail images will display properly, but once the videoplayer is 
>> started the screen goes blank. The player will indeed play and the sound 
>> from the video can be heard! Videos that are displayed using the video-tag 
>> in the html file seems to work OK.
>> 
>> Are there anyone else who has the same experience? I am on MacOS 13.0 and LC 
>> 10 dp 3 and dp 4
>> 
>> Best regards
>> Tore Nilsen
>> ___
>> 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: Bug in browser widget

2023-03-16 Thread matthias rebbe via use-livecode

Tore,
do you have a url i could try?

Tried here with a page that has Youtube videos embedded and could not reproduce 
the error with LC 9.6.9RC2 and 10DP4 on macOS 13.2.1



> Am 16.03.2023 um 10:44 schrieb Tore Nilsen via use-livecode 
> :
> 
> I have come across a bug in the browser widget. The browser will not show any 
> video when the video is embedded into the web page. The poster image and the 
> thumbnail images will display properly, but once the videoplayer is started 
> the screen goes blank. The player will indeed play and the sound from the 
> video can be heard! Videos that are displayed using the video-tag in the html 
> file seems to work OK.
> 
> Are there anyone else who has the same experience? I am on MacOS 13.0 and LC 
> 10 dp 3 and dp 4
> 
> Best regards
> Tore Nilsen
> ___
> 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

Bug in browser widget?

I have come across a bug in the browser widget. The browser will not show any 
video when the video is embedded into the web page. The poster image and the 
thumbnail images will display properly, but once the videoplayer is started the 
screen goes blank. The player will indeed play and the sound from the video can 
be heard! Videos that are displayed using the video-tag in the html file seems 
to work OK.

Are there anyone else who has the same experience? I am on MacOS 13.0 and LC 10 
dp 3 and dp 4

Best regards
Tore Nilsen
___
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

Bug in browser widget