Re: Mysterious new MetaCard file

Mark Schonewille wrote: > I got it running in 5 minutes. The guy who uploaded it says he has > removed all references to passwords. I have no idea why this was a > problem for him, but it is nice that he returned the modified files > as required by the oss licence. Depends on the license. And i

Re: Group does not exist after "copy to this card"

I have "not a clue", but it looks like no-one else had any good ideas, so instead I'll make a couple of suggestions :-) Try either of the following and see if it tells you anything. command sivasiva_Share put sConfigA["shareControl"] into tShareControl put the name of the last control

Re: Mysterious new MetaCard file

On 7/8/17 10:17 pm, Mark Wieder via use-livecode wrote: On 07/08/2017 11:51 AM, Mark Schonewille via use-livecode wrote: I got it running in 5 minutes. The guy who uploaded it says he has removed all references to passwords. I have no idea why this was a problem for him, but it is nice that h

Re: Mysterious new MetaCard file

On 07/08/2017 11:51 AM, Mark Schonewille via use-livecode wrote: I got it running in 5 minutes. The guy who uploaded it says he has removed all references to passwords. I have no idea why this was a problem for him, but it is nice that he returned the modified files as required by the oss licen

Re: Mysterious new MetaCard file

I got it running in 5 minutes. The guy who uploaded it says he has removed all references to passwords. I have no idea why this was a problem for him, but it is nice that he returned the modified files as required by the oss licence. ⁣Verzonden door BlueMail ​ Op 8 jul. 2017 19:40, om 19:40, Ri

Re: Mysterious new MetaCard file

OK: I'll give the thing a try. Richmond. On 7/8/17 9:23 pm, Mark Wieder via use-livecode wrote: On 07/08/2017 10:49 AM, Richmond Mathewson via use-livecode wrote: The backgroundInformation still does not explain where or who this new file comes from. Well, yes. It does. rdba...@sbcglobal.net

Re: Mysterious new MetaCard file

On 07/08/2017 10:49 AM, Richmond Mathewson via use-livecode wrote: The backgroundInformation still does not explain where or who this new file comes from. Well, yes. It does. rdba...@sbcglobal.net is the new moderator of the MC group. Only the moderator(s) can post files in the group. Or, for

Re: Mysterious new MetaCard file

The backgroundInformation still does not explain where or who this new file comes from. Richmond. On 7/8/17 8:44 pm, Mark Wieder via use-livecode wrote: On 07/08/2017 10:39 AM, Richmond Mathewson via use-livecode wrote: I have just received a note that a new file has been uploaded to the Meta

Re: Mysterious new MetaCard file

On 07/08/2017 10:39 AM, Richmond Mathewson via use-livecode wrote: I have just received a note that a new file has been uploaded to the MetaCard Yahoo group: https://groups.yahoo.com/neo/groups/MC_IDE/conversations/messages from an email address rdbar...@sbcglobal.net This purports to be a new

Re: Division by Zero Error

On 07/08/2017 08:26 AM, Roger Guay via use-livecode wrote: I am using the try/catch method you mention, but it doesn’t seem to work reliably. That's a bit disturbing. Can you post your code? -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode ma

Mysterious new MetaCard file

I have just received a note that a new file has been uploaded to the MetaCard Yahoo group: https://groups.yahoo.com/neo/groups/MC_IDE/conversations/messages from an email address rdbar...@sbcglobal.net This purports to be a new version of the mchome file . . . However I feel uncomfortable abou

Re: Fat widgets

I haven't encountered this because our widgets are a library. But - I'm guessing - you could try the revert command? Sent from my iPhone > On 8 Jul 2017, at 15:49, Matthias Rebbe via use-livecode > wrote: > > Thank you very much. :) > > This makes it so much easier to test stacks between 8 a

Re: Fat widgets

Thank you very much for that. This solves the situation where the LC-8 version and the LC-9 version are the same (have the same lcb file). Thus you can only have widgets that use LCB-syntax/features that are present in both LC-8 and LC-9, especially no new/different LCB features from LC-9. > Kev

Re: Division by Zero Error

Thanks very much Mark, Herman and Mike. I am using the try/catch method you mention, but it doesn’t seem to work reliably. I’m probably doing something else wrong . . . I’ll keep trying. Thanks again for your time. Roger ___ use-livecode mailing list u

Re: Fat widgets

Thank you very much. :) This makes it so much easier to test stacks between 8 and 9. I had to make some adjustments, because the source of my extensions is stored somewhere else and the updateMessage is also not present. I get the widget recompiled when i load the stack, but the widget in the st

Re: Fat widgets

I don¹t see why not: on openStack -- Build widgets and libraries if the environment is "development" then _checkExtension _rootFolder() & "/extensions/com.library.folder.here" -- insert any others here end if end openStack -- -- Remove all the files with the extension pExtension in t

Re: debugging a CEF browser instance

Bernard, in case you are filing a bug report could you please post the bug id here? I would like to add a comment with some websites urls i have problems with when using the widget /CEF browser. Regards, Matthias Matthias Rebbe +49 5741 31 ‌matthiasrebbe.eu ‌ > A

Re: Fat widgets

Kevin, is it possible to get that script or is it not for the public? Regards, Matthias Matthias Rebbe +49 5741 31 ‌matthiasrebbe.eu ‌ > Am 08.07.2017 um 12:32 schrieb Kevin Miller via use-livecode > mailto:use-livecode@lists.runrev.com>>: > > What we do one one

Re: debugging a CEF browser instance

Hi Bernard, There's no list, no. The widget is a reasonably thin wrapper around either CEF or (on Mac, iOS and Android) the system provided WebView. Without actually seeing cases to investigate which do not work as expected it is hard to advise what the problem might be (although 'cross origin

Re: Division by Zero Error

I use the try/catch/finally method mark mentions if there is a chance of divide by 0 errors. That way, no need to predict, just try it, and if theres an error, respond accordingly. On Sat, Jul 8, 2017 at 1:08 AM, hh via use-livecode < use-livecode@lists.runrev.com> wrote: > -- d0 is what you jud

Re: Fat widgets

What we do one one large project that uses widgets and moves between 8 and 9 is to automatically recompile them on startup using a script. The logic is simple - if a try determines the widget library functions are not running and available, uninstall the widget, recompile it and reinstall it. Its p

Fat widgets

This is the current situation: [*] A stack that contains a widget that is compiled with LC 8.1.5 can not be used with any other LC version than LC 8.1.5, [*] A stack that contains a widget that is compiled with LC 9.0.0 can not be used with any other LC version than LC 9.0.0 Mark Waddingham did re

Re: debugging a CEF browser instance

Hi Mark, I suspect this is the problem. Is there a list of things which the LC embedded browser forbids? Is there an explanation of the rationale for the embedded browser to behave differently from a default browser? This should be noted in the Dictionary, perhaps in the top entry of: com.livecod

Re: Division by Zero Error

-- d0 is what you judge as "is at about zero" for your input -- select it such in size, that you don't get an "overflow" or -- such that 1/d0 is your max ± vertical plot value (= clipping) function f3 x local d0=0.001 if abs(x-3) < d0 then return empty -- don't plot in case of an empt

Re: Division by Zero Error

oh! denominator! Kind regards, Mark Schonewille http://economy-x-talk.com https://www.facebook.com/marksch Buy the most extensive book on the LiveCode language: http://livecodebeginner.economy-x-talk.com Op 08-Jul-17 om 09:03 schreef Mark Schonewille: Usually, I can predict that a numerator i

Re: Division by Zero Error

Usually, I can predict that a numerator is going to be 0, e.g. in 1/(x^2). I just check the value of the numerator before doing the division. In rare cases, I can't predict the value of the numerator. In those cases, I put a try control structure around the offending lines and some code to cle