Re: mouseenter/mouseleave and pointer tool

Jim Lambert wrote: > Every time I click on a button in the IDE with the pointer tool > in order to select and, say, move it, I'd prefer if the mousedown/up > scripts didn't fire off because I'm editing the UI not running it. > If I recall correctly this was not how LC/Revolution originally >

Re: New(?) Idea for Standalones

Hi James, I downloaded MKVtoolsNix and it opens on the second right-click. As for my wife’s admin privileges, I will have to check later Thanks very much Roger > On Mar 29, 2021, at 4:43 PM, james--- via use-livecode > wrote: > > Hi Roger, > > Below is a link to the download page for

Re: New(?) Idea for Standalones

Well, the thought plickins. I just also tried to open another standalone from Bob Earp and it failed to open. I am back to my usual state of befuddlement! Roger > On Mar 29, 2021, at 6:02 PM, Dev via use-livecode > wrote: > > No Roger, the folder has nothing to do with it. The two right

Re: Resources folder on mac, and the good old days

Once I took a version of the LC IDE and edited one of the files in the package before opening it the first time. It would not open and complained about being corrupt/modified/something (can’t recall exact message). I trashed it and extracted a fresh copy. I launched it once and then quit.

Re: New(?) Idea for Standalones

No Roger, the folder has nothing to do with it. The two right click process will work wherever you unzip the new arrival. Sent from my iPhone > On Mar 29, 2021, at 5:54 PM, Roger Guay via use-livecode > wrote: > > Thanks for your kind offer, Alex, but I think the process of opening an >

Re: New(?) Idea for Standalones

Thanks for your kind offer, Alex, but I think the process of opening an unblessed standalone for OS 11 has been solved. See my previous post in response to Scott. Turns out to be fairly simple . . . at least for this iteration of OS. In short, just right-click 2 times. It may also be important

Re: mouseenter/mouseleave and pointer tool

I DO remember SuperEdit. So fast! But it was a completely “dead” development environment. You had to leave it in order to get any messages, IIRC. — Scott > On Mar 29, 2021, at 4:26 PM, Jim Lambert via use-livecode > wrote: > >> Paul wrote: >> >> This is not a bug, but a feature. Our app

Re: mouseenter/mouseleave and pointer tool

I wrote: > Every time I click on a button in the IDE with the pointer tool in order to > select and, say, move it, I'd prefer if the mousedown/up scripts didn't fire > off because I'm editing the UI not running it. Nevermind. Those scripts are not firing when using the pointer tool. I'm

Re: New(?) Idea for Standalones

Hi Roger, Below is a link to the download page for MkvToolnix, an app for packaging/modifying mkv files. It is not notarised and requires the steps we have been suggesting to open (after copying it to your local machine from the distribution disk image.)

Re: How to get the path to the 'My Livecode' or the plugins folder?

On 3/29/21 4:06 PM, matthias rebbe via use-livecode wrote: Dear all, is there a way to get the path to the 'My Livecode' or the 'Plugins' folder? Searched now for more than 40 minutes and did not find anything about it? Is there maybe a hidden variable / property available for this? Not

Re: How to get the path to the 'My Livecode' or the plugins folder?

Thanks Alex, i will try that. I still hope there is a property for this available. But for the meantime your suggestion will do i think. Matthias - Matthias Rebbe Life Is Too Short For Boring Code > Am 30.03.2021 um 01:26 schrieb Alex Tweedly via use-livecode > : > > Not pretty, but if you

Re: mouseenter/mouseleave and pointer tool

> Paul wrote: > > This is not a bug, but a feature. Our app contains a specialized network > drawing tool and we switch to the pointer tool to allow the user to > interact with drawn objects I'd respectfully suggest that is a fringe use case when compared to authoring in the LC IDE. Every

Re: How to get the path to the 'My Livecode' or the plugins folder?

Not pretty, but if you know you have a particular plugin installed, then you can do put the filename of stack "4wDevo" into tmp and work from there; e.g. I get /Users/alextweedly/Dropbox (Personal)/My Livecode/Plugins/4wDevo.livecode Alex. On 30/03/2021 00:06, matthias rebbe via

Re: New(?) Idea for Standalones

Great Scott! (How often do you hear that?) This works on second attempt but not the first. I verified this by trashing the first unzipped app and unzipping a second as you suggest. Here are the details: On first right-click - Open, I got “"Testeroni” can’t be opened because Apple cannot check

How to get the path to the 'My Livecode' or the plugins folder?

Dear all, is there a way to get the path to the 'My Livecode' or the 'Plugins' folder? Searched now for more than 40 minutes and did not find anything about it? Is there maybe a hidden variable / property available for this? Regards Matthias - Matthias Rebbe Life Is Too Short For Boring

Re: New(?) Idea for Standalones

That symbol probably means it was compiled to run on an older (Motorola ?) processor… similar to what happens if you have a 32 bit app on Big Sur. — Scott > On Mar 29, 2021, at 3:29 PM, Alex Tweedly via use-livecode > wrote: > > > On 29/03/2021 22:11, Roger Guay via use-livecode wrote: >>

Re: New(?) Idea for Standalones

Oops, meant to send that off-list. — Scott > On Mar 29, 2021, at 3:33 PM, scott--- via use-livecode > wrote: > > Hello Roger, > > I made a standalone from an empty stack (and one button that does nothing.) > It is 64 bit Mac. It is zipped. It isn’t in a DMG or any sort of installer. > It

Re: New(?) Idea for Standalones

Hello Roger, I made a standalone from an empty stack (and one button that does nothing.) It is 64 bit Mac. It is zipped. It isn’t in a DMG or any sort of installer. It is NOT code signed. I have been using this app to test how opening non-signed Mac Apps work. After (finally) opening the app

Re: New(?) Idea for Standalones

On 29/03/2021 22:11, Roger Guay via use-livecode wrote: Thanks, Alex. Unfortunately it comes up with the “No Entry” sign on this machine. Roger I'm not exactly sure what message this is, or when it happens. But this sounds like "Fortunately, ..." because I think it means you have an app

Re: Resources folder on mac, and the good old days

> On 30 Mar 2021, at 12:44 am, use-livecode-requ...@lists.runrev.com wrote: > > Unfortunately this has never been true on macOS X. > > The Resources folder (which is in the macOS app bundle) should be > treated as read-only… Mark Waddingham chides me for saying it is OK to write to the

Re: We don't need a Player (was Re: New(?) Idea for Standalones)

On Mon, Mar 29, 2021 at 4:35 PM Richard Gaskin via use-livecode < use-livecode@lists.runrev.com> wrote: > I think we're all on the same page here. > :thumbs_up -- Trevor DeVore ScreenSteps www.screensteps.com ___ use-livecode mailing list

Re: New(?) Idea for Standalones

On 3/29/21 1:20 PM, Craig Newman via use-livecode wrote: For about eight users in my business I distribute standalones for desktop only, both Mac and Windows versions. These are developed on a Mac. Simple to update and make, simple to give away, simple to use. That is the aspect of this

Re: We don't need a Player (was Re: New(?) Idea for Standalones)

Trevor DeVore wrote: > We agree that LiveCode should include a sensible baseline for building > a standalone. We also agree that they shouldn't try to write solutions > for all possible ways that someone may need to distribute a > standalone. My 2 cents is that LiveCode should provide a way for

Re: Help with androidStartAudioPlayingInBackground()

That did the trick, thank you. On 3/28/21 2:08 PM, J. Landman Gay via use-livecode wrote: I've seen similar issues when trying to read other file types from the resources folder in an Android standalone. Try copying the file to specialFolderPath("documents") and play it from there. It's likely

Re: We don't need a Player (was Re: New(?) Idea for Standalones)

On Mon, Mar 29, 2021 at 3:56 PM Richard Gaskin via use-livecode < use-livecode@lists.runrev.com> wrote: > > Here's the bottom of the post you were replying to: > > One suitable solution in the box is all that's needed, > with the option for folks to turn it off if they prefer >

Re: New(?) Idea for Standalones

Thanks, Alex. Unfortunately it comes up with the “No Entry” sign on this machine. Roger > On Mar 29, 2021, at 1:36 PM, Alex Tweedly via use-livecode > wrote: > > > On 29/03/2021 21:23, Roger Guay via use-livecode wrote: >> I have to admit I haven’t had a lot of time to experiment yet on my

Re: We don't need a Player (was Re: New(?) Idea for Standalones)

Trevor DeVore wrote: > On Mon, Mar 29, 2021 at 1:24 PM Richard Gaskin wrote: > >> Trevor DeVore wrote: >> >> > On Mon, Mar 29, 2021 at 12:31 PM Richard Gaskin wrote: >> >> Add-ons to the product experience can be a useful temporary >> >> workaround for long-time users, but if we step back and

Re: New(?) Idea for Standalones

On 29/03/2021 20:54, Paul Dupuis via use-livecode wrote: On 3/29/2021 3:36 PM, Alex Tweedly via use-livecode wrote: there is some way to allow unsigned apps to run on all current and foreseeable versions of the desktop OSes I think your assumption that you will be able - even via some

Re: New(?) Idea for Standalones

On 29/03/2021 21:23, Roger Guay via use-livecode wrote: I have to admit I haven’t had a lot of time to experiment yet on my wife’s computer as I've been busy here trying to communicate my problem. Also, my wife’s computer is busy helping her work from home, not to mention, her style is to

Re: New(?) Idea for Standalones

I have to admit I haven’t had a lot of time to experiment yet on my wife’s computer as I've been busy here trying to communicate my problem. Also, my wife’s computer is busy helping her work from home, not to mention, her style is to have numerous windows open all the time. Drives me nuts! I

Re: New(?) Idea for Standalones

I’m sure you’re right about this. And, If this be the case, I would ask for the work-around approach . . . a LiveCodeLight App downloadable from RunRev (or other approved source) that runs stacks but hides or strips the IDE. Roger > On Mar 29, 2021, at 12:54 PM, Paul Dupuis via use-livecode

Re: New(?) Idea for Standalones

Roger, this is frustrating, isn't it !! If I were you, I'd send an email to the list saying (something along the lines of ) I want to get to the bottom of this. I'm going to host a Zoom call on my wife's Mac at where I will share my screen so you can all see what I'm doing, and I'll

Re: New(?) Idea for Standalones

On 3/29/2021 3:36 PM, Alex Tweedly via use-livecode wrote: there is some way to allow unsigned apps to run on all current and foreseeable versions of the desktop OSes I think your assumption that you will be able - even via some horribly convoluted series of steps - to run unsigned and

Re: New(?) Idea for Standalones

Craig. You and I are very much in the same boat as far as how we use LiveCode. The problem is not constructing the standalones. LiveCode is superb in this regard. The problem is distributing Apple unapproved standalones. It seems I can no longer do that anymore as I used to. The problem is

Re: New(?) Idea for Standalones

On 29/03/2021 19:20, Craig Newman via use-livecode wrote: Roger. For about eight users in my business I distribute standalones for desktop only, both Mac and Windows versions. These are developed on a Mac. Simple to update and make, simple to give away, simple to use. That is the aspect of

Re: mouseenter/mouseleave and pointer tool

This is not a bug, but a feature. Our app contains a specialized network drawing tool and we switch to the pointer tool to allow the user to interact with drawn objects (buttons and line graphics connecting the buttons). We use mouseEnter and mouseLeave to update information about the object

Re: We don't need a Player (was Re: New(?) Idea for Standalones)

On Mon, Mar 29, 2021 at 1:24 PM Richard Gaskin via use-livecode < use-livecode@lists.runrev.com> wrote: > Trevor DeVore wrote: > > > On Mon, Mar 29, 2021 at 12:31 PM Richard Gaskin wrote: > >> Add-ons to the product experience can be a useful temporary > >> workaround for long-time users, but

Re: mouseenter/mouseleave and pointer tool

Jim Lambert wrote: >> Klaus wrote: >> when the pointer tool is active, "mouseenter" and "mouseleave" >> handlers are executed nevertheless!? >> >> I don't this this is correct behaviour! > > I agree. > When the pointer tool is selected in the IDE one is supposedly in > Editing Mode. This is a

Re: We don't need a Player (was Re: New(?) Idea for Standalones)

Trevor DeVore wrote: > On Mon, Mar 29, 2021 at 12:31 PM Richard Gaskin wrote: >> Add-ons to the product experience can be a useful temporary >> workaround for long-time users, but if we step back and look >> at the gestalt of the user experience they're not a true solution. >> > > Do you think

Re: New(?) Idea for Standalones

Roger. For about eight users in my business I distribute standalones for desktop only, both Mac and Windows versions. These are developed on a Mac. Simple to update and make, simple to give away, simple to use. That is the aspect of this thread that I do not understand, perhaps misreading

Re: mouseenter/mouseleave and pointer tool

Hi all, > Klaus wrote: > when the pointer tool is active, "mouseenter" and "mouseleave" > handlers are executed nevertheless!? > > I don't this this is correct behaviour! reported: Best Klaus -- Klaus Major https://www.major-k.de

Re: mouseenter/mouseleave and pointer tool

> Klaus wrote: > when the pointer tool is active, "mouseenter" and "mouseleave" > handlers are executed nevertheless!? > > I don't this this is correct behaviour! I agree. When the pointer tool is selected in the IDE one is supposedly in Editing Mode. To have code execute when you simply enter

Re: New(?) Idea for Standalones

matthias_livecode_150811 wrote: > Don't blame Microsoft and Apple I'm not sure anyone here is. Jumping through hoops is painful, of course, but I think the folks here recognize that having their data and devices compromised is even more painful. > And purchasing a code signing certificate

Re: We don't need a Player (was Re: New(?) Idea for Standalones)

On Mon, Mar 29, 2021 at 12:31 PM Richard Gaskin via use-livecode < use-livecode@lists.runrev.com> wrote: > Trevor DeVore wrote: > > > On Mon, Mar 29, 2021 at 10:57 AM Richard Gaskin wrote: > > > >> TL/DR: > >> > >> We don't need a generic player. > >> > >> What we need is an updated

Re: New(?) Idea for Standalones

They will probably never take the time to be bothered with complaining by not buying from Apple or Microsoft. It would be easier for them to not buy electricity from the power companies and that won’t happen either. JB > On Mar 29, 2021, at 10:51 AM, Paul Dupuis via use-livecode > wrote: > >

Re: We don't need a Player (was Re: New(?) Idea for Standalones)

Trevor DeVore wrote: > On Mon, Mar 29, 2021 at 10:57 AM Richard Gaskin wrote: > >> TL/DR: >> >> We don't need a generic player. >> >> What we need is an updated Standalone Builder, to provide >> more complete tooling and better guidance for building a >> modern standalone. > > > An easy way to

Re: mobileStoreMakePurchase not working for iOS

I see now that it was stated on 7/16/2014 that this might not work in the Simulator, that was my misunderstanding. My app is able to make the request as I can get “sendingRequest” as the pState, but then errors out with the “An unknown error occurred” for the “error” pState. This happens on

Re: New(?) Idea for Standalones

Don't blame Microsoft and Apple There is a reason why MS and Apple require such things. It is security. If there weren't any "bad" people who try to hack, hijack or infect our computers using viruses, trojan or other ways, then it wouldn't be necessary either. As a developer I am also not very

Re: We don't need a Player (was Re: New(?) Idea for Standalones)

On Mon, Mar 29, 2021 at 10:57 AM Richard Gaskin via use-livecode < use-livecode@lists.runrev.com> wrote: > TL/DR: > > We don't need a generic player. > > What we need is an updated Standalone Builder, to provide more complete > tooling and better guidance for building a modern standalone. > An

Re: New(?) Idea for Standalones

Beautifully said, Rick! Especially your point about it being a PITA. Thanks! > On Mar 29, 2021, at 9:36 AM, Rick Harrison via use-livecode > wrote: > > Hi Mark, > > Perhaps improving standalone building should be put at > the top of the priority of things to improve for LiveCode. > > I

Re: New(?) Idea for Standalones

On 3/29/2021 12:28 PM, Roger Guay via use-livecode wrote: In any case it is not as easy as it use to be and IMO, this door may be closing. You are 100% right. The door is closing and will eventually be closed unless enough consumers of Apple (and Windows) products complain with their buying

Re: We don't need a Player (was Re: New(?) Idea for Standalones)

The days of distributing apps without a cost to the developer are unfortunately over (Mac/Win). If you want someone to be able to open an app on their Mac without jumping through hoops, then you need to be a paid developer and do the sign/notarize dance. LC could help automate parts of the

Re: New(?) Idea for Standalones

On 3/29/2021 12:36 PM, Rick Harrison via use-livecode wrote: Many LC users want to be able to create their application, and deploy it quickly to their own computers, or to give away to their family members. They are not interested in inserting Apple or other corporations into their personal

Re: New(?) Idea for Standalones

On 3/29/2021 12:15 PM, Mark Waddingham via use-livecode wrote: In terms of the general thrust behind this thread - I completely agree that standalone building has become tortuous over the last few years as all platforms add more and more hoops you have to jump through. However, this is

Re: New(?) Idea for Standalones

Unfortunately nothing can replace the requirement for an Apple developer account on Mac, which is the reason for the request here. But I'd love to see notarization and stapling built in. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On

Re: We don't need a Player (was Re: New(?) Idea for Standalones)

YES . . . What he said! > On Mar 29, 2021, at 8:55 AM, Richard Gaskin via use-livecode > wrote: > > TL/DR: > > We don't need a generic player. > > What we need is an updated Standalone Builder, to provide more complete > tooling and better guidance for building a modern standalone. > > >

Re: New(?) Idea for Standalones

Hi Mark, Perhaps improving standalone building should be put at the top of the priority of things to improve for LiveCode. I think people are very frustrated that they are having great difficulties in building a standalone. A process that used to be relatively simple is now way too complex.

Re: New(?) Idea for Standalones

Craig, I apologize for the confusion. I tended to shift focus throughout this thread. I too have, in the past, made and distributed standalones with great ease. But recently Apple and perhaps others have made it very difficult to do this as they are now requiring(?) that one be an Apple

Re: New(?) Idea for Standalones

And another good reason not to kick sand in LC’s face is they appear to be the only ones who have invested the money and time for the free community version to exist as it is today with the many features it has now. Think about if before you become so cheap & selfish that you try to destroy them.

Re: New(?) Idea for Standalones

On 2021-03-27 22:22, J. Landman Gay via use-livecode wrote: Also note: The stacks you distribute cannot violate the LC license agreement. They can't reproduce IDE features or allow users to do things that only a licensed user can do. Please don't violate the license agreement; we all want LC to

We don't need a Player (was Re: New(?) Idea for Standalones)

TL/DR: We don't need a generic player. What we need is an updated Standalone Builder, to provide more complete tooling and better guidance for building a modern standalone. - more complete version Background -- This thread, and many

[ANN] This Week in LiveCode 260

Hi all, Read about new developments in LiveCode open source and the open source community in today's edition of the "This Week in LiveCode" newsletter! Read issue #260 here: https://bit.ly/3u1lz5K This is a weekly newsletter about LiveCode, focussing on what's been going on in and

Re: mobileStoreMakePurchase not working for iOS

Hello Andrew, Just to mention that in-app purchases are not supported in the Simulator. Kind regards, Panos -- On Fri, 26 Mar 2021 at 05:29, Andrew at MidWest Coast Media via use-livecode wrote: > I have released my first project with in-app purchases but only to 50% > platform success:

AW: How to install tsNet correctly?

Thanks Matthias for your quick jump in. It obviously was a very old behaviour of mine, regarding some very old version  Tiemo -Ursprüngliche Nachricht- Von: use-livecode Im Auftrag von matthias rebbe via use-livecode Gesendet: Montag, 29. März 2021 15:47 An: How to use LiveCode Cc:

Re: How to install tsNet correctly?

Hi Tiemo, please see my answers below. Regards, Matthias > Am 29.03.2021 um 15:24 schrieb Tiemo via use-livecode > : > > Hello, > > it's some time ago, that I build a new install. > > > > On Windows I formerly just copied the "tsNet-x86" dll into the Externals > folder in my runtime dir

Re: New(?) Idea for Standalones

I have been following this thread with interest, and have no idea what anyone is talking about. I make and update standalones regularly on my Mac, and distribute them to many Windows and Mac desktop users in my company. All for “personal’ use. Somewhere in the middle of all this, I thought

Re: mouseenter/mouseleave and pointer tool

I think if you are making a drawing app in Livecode, you need mouseEnter and mouseLeave with the pointer tool so you can have object scrips change the cursor icon to appropriate icons when over certain special objects that you want to interact with as objects. On 3/29/2021 6:31 AM, Klaus

Re: mouseenter/mouseleave and pointer tool

I think if you are making a drawing app in Livecode, you need mouseEnter and mouseLeave with the pointer tool so you can have object scrips change the cursor icon to appropriate icons when over certain special objects that you want to interact with as objects. On 3/29/2021 6:17 AM, Klaus

Re: mouseenter/mouseleave and pointer tool

Klaus. I have always seen this. It does seem a little odd,, though. You can always place something like this wherever you need to, but I know your question is “Why do I need to” on mouseEnter if the tool = "browse tool" then pass mouseEnter end mouseEnter Craig > On Mar 29, 2021, at 6:31

How to install tsNet correctly?

Hello, it's some time ago, that I build a new install. On Windows I formerly just copied the "tsNet-x86" dll into the Externals folder in my runtime dir and everything was fine. When looking into the LC install dir on C:\programs\runrev\ there is a \Ext\tsNet_Indy_1.4.2\ folder with quite

mouseenter/mouseleave and pointer tool

Hi friends, when the pointer tool is active, "mouseenter" and "mouseleave" handlers are executed nevertheless!? I don't this this is correct behaviour! For the sake of "conceptional continuity" (©Frank Zappa) then all other mouse handlers should be executed and we don't want that. :-) All or

mouseenter/mouseleave and pointer tool

Hi friends, when the pointer tool is active, "mouseenter" and "mouseleave" handlers are executed nevertheless!? I don't this this is correct behaviour! For the sake of "conceptional continuity" (©Frank Zappa) then all other mouse handlers should be executed and we don't want that. :-) All or

Re: Resources folder on mac, and the good old days

I am following this with interest because, as I have previously lamented, I would like to give away apps to colleagues without the huge, incomprehensible headache of certificates, signing and notarising etc. I want to make absolutely sure that I understand it correctly, that a player app which

Re: Unreliable File Deletion

On 2021-03-28 18:11, R.H. via use-livecode wrote: @ Peter Reid Your message found my attention. Also I am working on Windows 10 and have the same problem using LC 9.6.1 Indy version. The similar or same problem as you have: I want to delete the text file. The command I issue is "detele

Re: Resources folder on mac, and the good old days

On 2021-03-29 03:13, Neville Smythe via use-livecode wrote: you may already know this, but this will not work in a standalone! We will surely not have write permissions in that folder! As a workaround I would probably use -> specialfolderpath("temporary") Or even write the text to -> the