Re: Nasty filter bug

se-livecode < > >>>> use-livecode@lists.runrev.com <mailto:use-livecode@lists.runrev.com>> > wrote: > >>>>> > >>>>> Brian. > >>>>> > >>>>> Nope. Those two chars pass through the filter, er, filtered. > >&

Re: Nasty filter bug

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

Re: Nasty filter bug

er 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

Re: Nasty filter bug (not)

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

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

Re: Nasty filter bug

gt; 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. > >>>

Re: Nasty filter bug

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

Re: Nasty filter bug

s. >> >> 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 mat

Re: Nasty filter bug

mehow 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 [[] i

Re: Nasty filter bug

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

Re: Nasty filter bug

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

Nasty filter bug

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

Re: Bug 23507 - LC Clipboard Polling Failure

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

Re: Bug 23507 - LC Clipboard Polling Failure

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

Re: Bug 23507 - LC Clipboard Polling Failure

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

Re: Bug 23507 - LC Clipboard Polling Failure

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

RE: Bug 23507 - LC Clipboard Polling Failure

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... (P

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 cont

RE: Bug 23507 - LC Clipboard Polling Failure

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

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

Re: 2 Qs about the OAuth2 bug fix in v10.x

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

Re: 2 Qs about the OAuth2 bug fix in v10.x

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 redi

2 Qs about the OAuth2 bug fix in v10.x

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

Re: Property Inspector bug for keys with commas in the key name

; 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. Be

Re: Property Inspector bug for keys with commas in the key name

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

Re: Property Inspector bug for keys with commas in the key name

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

Re: Property Inspector bug for keys with commas in the key name

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

Re: Property Inspector bug for keys with commas in the key name

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

Re: Property Inspector bug for keys with commas in the key name

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

Re: Property Inspector bug for keys with commas in the key name

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,

Re: Property Inspector bug for keys with commas in the key name

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

Property Inspector bug for keys with commas in the key name

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

Re: Property Inspector bug for keys with commas in the key name

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

Re: Property Inspector bug for keys with commas in the key name

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 b

Property Inspector bug for keys with commas in the key name

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

Re: sort bug

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

Re: sort bug

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

Re: sort bug

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

Re: sort bug

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,

Re: sort bug

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

Re: Sort bug and also multilevel sorting

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

Re: sort bug

: 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

Re: Sort bug and also multilevel sorting

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

Re: sort bug

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

Re: Sort bug

ot 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

Re: Sort bug

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

Re: Sort bug

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

Re: Sort bug

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

Re: Sort bug

irst, 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 conta

Re: Sort bug

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

Re: Sort bug

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

Sort bug

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

Re: Bug or...? Native Querying

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

Re: Bug or...? Native Querying

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

Bug or...? Native Querying

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

Stop using font file bug

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 als

Re: Bug in browser widget

gt; >> >>> 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 &g

Re: Bug in browser widget

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

Re: Bug in browser widget

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 br

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

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

Re: Anyone else experience this bug?

of > > Has anyone else experienced it? > > Me! I get the IDE Vanishing Act on Windows, once per week. > > But perhaps a DIFFERENT bug or a different trigger: > > Not when interacting specifically with Styled text. > > Best wishes, > > Curry Kenworthy > >

Re: Anyone else experience this bug?

> livecode process just goes poof > Has anyone else experienced it? Me! I get the IDE Vanishing Act on Windows, once per week. But perhaps a DIFFERENT bug or a different trigger: Not when interacting specifically with Styled text. Best wishes, Curry Kenworthy WordLib: Import M

Re: Anyone else experience this bug?

Thank you all for your responses. Knowing that it has to do with Styled text is a big help, thanks Mark W. Bob, the crash report is in the bug report. Mathias, unfortunately I cannot post a sample stack. I cannot reliably reproduce it myself. The fields in the one code base,Appli, are heavily

Re: Anyone else experience this bug?

On 1/3/23 20:22, Tom Glod via use-livecode wrote: Hi Folks, I work with 2 completely different codebases every week. On both I and (we) experience hard crashes to desktop, where livecode process just goes poof Usually it is triggered by either a mouseUp or mouseDown ... most likely UP. The bug

Re: Anyone else experience this bug?

or of some lines. Each line with an other color. I also changed the text style of some words in some lines. I then tried to replicate, but was not successful. Tried it the whole day about every half an hour. But maybe my field is not as complex as your field is. Unfortunately your bug r

Re: Anyone else experience this bug?

Seems there ought to be a crash log somewhere that could give clues. On the Mac you can open the Console app, click the Crash Reports in the left pane, and search for Livecode. But I am not exactly sure that the crash logs will indicate application crashes. Bob S On Jan 4, 2023, at 08:22 ,

Re: Anyone else experience this bug?

55609 > > > > > > On Wed, 4 Jan 2023 at 04:22, Tom Glod via use-livecode < > > use-livecode@lists.runrev.com> wrote: > > > >> Hi Folks, > >> > >> I work with 2 completely different codebases every week. > >> On both I

Re: Anyone else experience this bug?

; process just goes poof > Usually it is triggered by either a mouseUp or mouseDown ... most likely UP. > The bug is not consistent and does not happen when clicking anything in > particular. > There are days it does not happen, and days when it does multiple times. > On the

Re: Anyone else experience this bug?

v.com> wrote: > >> Hi Folks, >> >> I work with 2 completely different codebases every week. >> On both I and (we) experience hard crashes to desktop, where livecode >> process just goes poof >> Usually it is triggered by either a mouseUp or mouseDown ... most

Re: Anyone else experience this bug?

h I and (we) experience hard crashes to desktop, where livecode > process just goes poof > Usually it is triggered by either a mouseUp or mouseDown ... most likely > UP. > The bug is not consistent and does not happen when clicking anything in > particular. > There are days it d

Anyone else experience this bug?

Hi Folks, I work with 2 completely different codebases every week. On both I and (we) experience hard crashes to desktop, where livecode process just goes poof Usually it is triggered by either a mouseUp or mouseDown ... most likely UP. The bug is not consistent and does not happen when clicking

Re: s it a bug?

Bob: I'm not seeing this in the IDE or standalone. LC 9.6.7, macOS Monterey > > I found one thing I think is a bug, and I'd like to report it, but I want to > see if anyone else thinks this may be the expected behavior: > > It seems to me that when clicking and holding the mo

Re: Is it a bug?

If you are seeing a different behavior then perhaps something in my code is doing it. I'll check the executionContexts to see. Bob S > On May 23, 2022, at 14:03 , Ralph DiMola via use-livecode > wrote: > > I also expect nothing is done if I click on anything and move the mouse > outside

RE: Is it a bug?

I also expect nothing is done if I click on anything and move the mouse outside the active window THEN release(unless a drag and drop is involved). I use this all this time with the classic

Re: Is it a bug?

sounds a lot like https://quality.livecode.com/show_bug.cgi?id=23693 Kind regards Bernd ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

Re: Is it a bug?

Seem sensible, after all end-users should be able ti change their minds. On Mon, 23 May 2022, 21:23 Bob Sneidar via use-livecode, < use-livecode@lists.runrev.com> wrote: > I found one thing I think is a bug, and I'd like to report it, but I want > to see if anyone else thi

Is it a bug?

I found one thing I think is a bug, and I'd like to report it, but I want to see if anyone else thinks this may be the expected behavior: It seems to me that when clicking and holding the mouse button down on an pulldown menu, then releasing outside that menu so that no menu item is actually

Re: Re Pulldownmenu button bug on Windows

Klaus wrote: > Am 11.05.2022 um 20:27 schrieb Richard Gaskin wrote: >> ... make sure the buttons you're using in the menu stack have >> their autoArm set to true, ... > > Hint: > that property "autoarm" did not make it into the inspector somehow, > so you need to do this by script! It's far

Re: Re Pulldownmenu button bug on Windows

Hi all, > Am 11.05.2022 um 20:27 schrieb Richard Gaskin via use-livecode > : > ... make sure the buttons you're using in the menu stack have their autoArm > set to true, ... Hint: that property "autoarm" did not make it into the inspector somehow, so you need to do this by script! > -- >

Re: Re Pulldownmenu button bug on Windows

esponse to that message? There are some clever people on this list. I'll bet we can find a solution for your need once we more fully understand the goals. -- Richard Gaskin Fourth World Systems Neville Smythe wrote: The pulldownmenu bug I reported has been confirmed: bug 23693 <https:/

Re: Re Pulldownmenu button bug on Windows

I'm going to have a look at that Richard. Thanks. Bob S > On May 11, 2022, at 11:27 , Richard Gaskin via use-livecode > wrote: > > Neville Smythe wrote: > > Thanks again Richard > > > > In my case I don’t actually need a workaround. Once I had corrected > > my own error, the only effect of

Re: Re Pulldownmenu button bug on Windows

Neville Smythe wrote: > Thanks again Richard > > In my case I don’t actually need a workaround. Once I had corrected > my own error, the only effect of the inconsistent event order is that > on Windows and Linux the colour coding of the selection turns off a > fraction of a second earlier than on

Re Pulldownmenu button bug on Windows

as to need to fix that. Nevertheless it is conceivable, if unlikely, that someone might want to do something more significant in the mouseLeave handler, so I continue to call the inconsistency a bug. The fact that the combobox menu button behaves in the same way on all 3 platforms does seem

Re: Re Pulldownmenu button bug on Windows

What a very kind thing of you to say. Thank you. After 30 years as a recipient of so much wisdom and lore shared with me, I've felt compelled to share some of that forward. In recent years most of what I write seems ignored, so I've been spending my time elsewhere. Your encouragement may see

Re: Re Pulldownmenu button bug on Windows

ended, > but on a user's Windows PC the effect was to change a very minor > cosmetic difference into a major bug because the menu no longer > did anything. This was quite difficult to track down. Thank you for that description. Just to make sure I understand this, the menu button in

Re: Re Pulldownmenu button bug on Windows

and participating in its communities. Just the same, let's >> roll up our sleeves and see what can be done: >> >> >> >> Looking Forward: >> --- >> Edge case or not, let's see what we can do to get a solution for you sooner >> than the engine te

Re: Re Pulldownmenu button bug on Windows

don’t think the developer could be expected to expect this, and to my mind that makes it a definite bug. If it occurred with more common event pairs, LC coding would be much more difficult. I am not actually fussed which processing order is accepted as “correct”: although I expressed an IMO

Re: Re Pulldownmenu button bug on Windows

ion for you sooner > than the engine team would be able to even thinking about revisions as > sweeping as would be needed to satisfy the engine request. > > What do you need from mouseLeave during a menu drop? What are you doing in > response to that message? > > There are some clev

Re: Re Pulldownmenu button bug on Windows

d to satisfy the engine request. What do you need from mouseLeave during a menu drop? What are you doing in response to that message? There are some clever people on this list. I'll bet we can find a solution for your need once we more fully understand the goals. -- Richard Gaskin Fou

Re Pulldownmenu button bug on Windows

The pulldownmenu bug I reported has been confirmed: bug 23693 <https://quality.livecode.com/show_bug.cgi?id=23693> To remind the reader: On a Mac, when a user select a menu item from a pulldown menu button, the menuPick message is sent first followed by a mouseLeave message (gen

Re: Pulldownmenu button bug on Windows

er actually makes the > selection. > > Which means standalones behave quite differently (in my app, the menupick did > something to a selection in a field, and mouseleave did something else to the > selection: the order is thus critical). > > They can’t both be right, so certainly

Pulldownmenu button bug on Windows

behave quite differently (in my app, the menupick did something to a selection in a field, and mouseleave did something else to the selection: the order is thus critical). They can’t both be right, so certainly one is a bug. The Mac order is IMO correct since the pulldown menu has been started

Re: bug in Standalone Only

Hi all. I found it. I have a handler that creates a temp database in the default folder. In a Mac standalone that folder is read only. Thankfully it is only something I use in the IDE and not in standalones, so I now test for the environment. Sent from my iPhone > On Mar 7, 2022, at 17:48,

Re: bug in Standalone Only

Remote debugging allows you to step through the script. But we do have an error lookup utility that will tell you what the error codes mean. -- Jacqueline Landman Gay |

Re: bug in Standalone Only

ook. Hope that helps. On Mon, Mar 7, 2022 at 7:16 PM Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi all. There is a bug in my app which only rears it's ugly head when I > create a standalone. When I am in the IDE it never happens. I get an error &g

bug in Standalone Only

Hi all. There is a bug in my app which only rears it's ugly head when I create a standalone. When I am in the IDE it never happens. I get an error dialog but the numbers in the dialog do not make any sense. I email myself an error report, but where it says the error is happening is NOT where

Re: LC Bug: Clipboard Polling Failure

Me: > BTW, I have a potential user workaround I was almost afraid to mention that: sure enough, LC bombed out after I did! :D So to be clear, this will NOT solve the issue. (User workarounds are only bandaids at best.) Disclaimer: This LC bug needs a real fix. It locks up the clipbo

Re: LC Bug: No Mouse Wheel Scroll after a Ctrl-Click Launch

Tom: > wow Curry that must have been a hard one to track down. > knowing me, i'll run into it. A bit tricky! :) BTW, I have a potential user workaround for the other bug I reported last week. I will post it soon Best wishes, Curry Kenworthy WordLib: Import MS Word and OpenOffice

Re: LC Bug: No Mouse Wheel Scroll after a Ctrl-Click Launch

wow Curry that must have been a hard one to track down. knowing me, i'll run into it. On Sun, Jan 16, 2022 at 2:40 PM Curry Kenworthy via use-livecode < use-livecode@lists.runrev.com> wrote: > > LC Bug: > > After you Ctrl-click a link that uses "launch" >

  1   2   3   4   5   6   7   8   9   10   >