Re: modal window = block handler?

I realize that, but this thread has been discussing whether that is a "bug" or not. I support that there should be a feature, but probably a MORE clearly identified feature. Something LIKE (I am not proposing specific syntax, but illustrating a point) open window "X" as modal paused and open windo

Re: modal window = block handler?

According to this thread, that is what open invis as modal does. Bob S > On Jul 10, 2017, at 14:53 , Paul Dupuis via use-livecode > wrote: > > 2) present a modal windows, allow no other scripts or actions to occur, > but allow the current handler to continue executing.

Re: modal window = block handler?

On 7/10/2017 4:54 PM, J. Landman Gay via use-livecode wrote: > On 7/10/17 3:41 PM, J. Landman Gay via use-livecode wrote: >> On 7/10/17 12:18 PM, FlexibleLearning.com via use-livecode wrote: >>> Opening a modal as normal (i.e. visible) obviously still does what you >>> specify. We simply have a 'hi

Re: modal window = block handler?

err... will NOW work? Bob S > On Jul 10, 2017, at 14:08 , Bob Sneidar via use-livecode > wrote: > > Okay, this has piqued my curiosity. Are you saying that if I open a stack > invisible as modal, I can then show that stack later and animated progress > indicators will not work?? > > Bob S

Re: modal window = block handler?

Okay, this has piqued my curiosity. Are you saying that if I open a stack invisible as modal, I can then show that stack later and animated progress indicators will not work?? Bob S > On Jul 10, 2017, at 13:51 , FlexibleLearning.com via use-livecode > wrote: > > If “popup” is non-blocking

Re: [ANN] Release 8.1.5

I'm getting the same error with XC 8.3. Interesting, though, I think I may have stumbled on the problem. Every time I launch XC and go into my account and the certs/profiles list, XC creates a new cert for development and a new one for distribution. I just went into my keychain, removed all of the

Re: modal window = block handler?

On 7/10/17 3:41 PM, J. Landman Gay via use-livecode wrote: On 7/10/17 12:18 PM, FlexibleLearning.com via use-livecode wrote: Opening a modal as normal (i.e. visible) obviously still does what you specify. We simply have a 'hidden feature' that enables a non-blocking modal should it be required

RE: modal window = block handler?

If “popup” is non-blocking then it’s a bug. However, I hope that the non-blocking behaviour of “open invis as modal” is retained, or there is no way to indicate progress in a modal. Hugh Senior FLCo From: Andre Garzia [mailto:an...@andregarzia.com] Sent: 10 July 2017 19:15 To: How to us

Re: modal window = block handler?

On 7/10/17 12:18 PM, FlexibleLearning.com via use-livecode wrote: Opening a modal as normal (i.e. visible) obviously still does what you specify. We simply have a 'hidden feature' that enables a non-blocking modal should it be required (e.g. a progress indicator that prevents user-clicks on other

Re: [ANN] Release 8.1.5

Thanks David, good to know. So Sierra 10.12.5 does not seem to be the culprit. Best, Panos -- On Mon, Jul 10, 2017 at 9:12 PM, Dave Kilroy via use-livecode < use-livecode@lists.runrev.com> wrote: > @Panos > > LC 8.1.5 builds OK for iOS here: > OS X: 10.12.5 > Xcode: 8.3.3 > > Dave > > > > @Paul

Re: [ANN] Release 8.1.5

@Panos LC 8.1.5 builds OK for iOS here: OS X: 10.12.5 Xcode: 8.3.3 Dave > @Paul > Thanks for the feedback > > @Mike > After the LiveCode Global on Thursday, I'll update my Mac to Sierra > 10.12.5, to see if this is related. > > > > On Mon, Jul 10, 2017 at 6:39 PM, Paul Hibbert via use-

Re: modal window = block handler?

EEEK! > On Jul 10, 2017, at 11:15 , Andre Garzia via use-livecode > wrote: > > Friends, > > Just to add a related note here, at least on 9dp5 the "popup" command is > also not pausing. It is supposed to pause the handler that calls it until > menupick happens but in my experience here it simpl

Re: modal window = block handler?

Friends, Just to add a related note here, at least on 9dp5 the "popup" command is also not pausing. It is supposed to pause the handler that calls it until menupick happens but in my experience here it simple keeps running even while the modal is open. This might be related. om om andre On Mon,

Re: [ANN] Release 8.1.5

@Paul Thanks for the feedback @Mike After the LiveCode Global on Thursday, I'll update my Mac to Sierra 10.12.5, to see if this is related. On Mon, Jul 10, 2017 at 6:39 PM, Paul Hibbert via use-livecode < use-livecode@lists.runrev.com> wrote: > I just saw the Link Arm error, but the dialogue a

Re: [ANN] Release 8.1.5

I just saw the Link Arm error, but the dialogue also suggested updating the path to the Xcode tools, I did this with [ sudo xcode-select -r ] in terminal and all works correctly now. This is with Xcode 8.3 installed in the default Applications folder. I haven’t tried updating Xcode to 8.3.3 just

Re: [ANN] Release 8.1.5

I do not expect an older Xcode version to make the difference, but anyway. Just a clarification, can you build your app using the same setup in 8.1.5 rc3? On Mon, Jul 10, 2017 at 6:32 PM, Mike Kerner via use-livecode < use-livecode@lists.runrev.com> wrote: > I did clear the PP's. I'll try downlo

Re: [ANN] Release 8.1.5

I did clear the PP's. I'll try downloading an older xcode to see if that helps, since right now I'm stopped. On Mon, Jul 10, 2017 at 1:20 PM, panagiotis merakos via use-livecode < use-livecode@lists.runrev.com> wrote: > @MIke I guess that Xcode8.3.3 is the one in /Applications/Xcode.app? BTW I >

Re: [ANN] Release 8.1.5

@MIke I guess that Xcode8.3.3 is the one in /Applications/Xcode.app? BTW I would suggest to have separate folders for each Xcode version, to avoid problems where the Xcode version is updated automatically (the one in /Applications/Xcode.app), but LC not yet supports this Xcode version. I have a fol

Re: modal window = block handler?

Opening a modal as normal (i.e. visible) obviously still does what you specify. We simply have a 'hidden feature' that enables a non-blocking modal should it be required (e.g. a progress indicator that prevents user-clicks on other windows). Hugh Senior FLCo > I'm going to have to disagree here.

Re: [ANN] Release 8.1.5

10.12.5 8.3.3 /Applications/Xcode.app/Contents/Developer I've also run into another weird thing with this version of xcode. Thinking that I had a cert or provisioning profile problem, I went in to prefs and pulled up the certs. Every time I do that, xcode creates a new one - both developer and di

Re: [ANN] Release 8.1.5

That's moderately exciting. Richmond. On 7/10/17 4:23 pm, panagiotis merakos via use-livecode wrote: Dear List Members, We are pleased to announce the release of LiveCode 8.1.5 Stable. By "Stable", we mean that no reported regressions have been introduced in 8.1.5, compared to the previous Sta

Re: [ANN] Release 8.1.5

hmm, I have not seen that before. Which Sierra version are you using? I am on Sierra 10.12.4. Are you using Xcode 8.3.3? What is the terminal output if you type "xcode-select -p"? On Mon, Jul 10, 2017 at 5:46 PM, Mike Kerner via use-livecode < use-livecode@lists.runrev.com> wrote: > I was able

Re: [ANN] Release 8.1.5

I was able to get the build to get further by switching the ios version to the latest one (10.3), but now I'm getting a codesigning failed, segmentation fault 11 error. Bug 20030. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit t

Re: modal window = block handler?

lesson learned .. happy i found out about this inconcistency now rather than later. going forward I am using a "wait until mywindowopen = 0 with messages" to make sure i get the same identical behavior on every platform. thanks as always you guys On Mon, Jul 10, 2017 at 11:18 AM, Bob Sneidar

Re: [ANN] Release 8.1.5

nope, that doesn't fix it every time, either, so ignore that suggestion. I'm on attempt 6 for this app... On Mon, Jul 10, 2017 at 12:00 PM, Mike Kerner wrote: > I've been fighting with it all morning. The only thing that MIGHT be > fixing it is if I switch the build-for devices to something els

Re: [ANN] Release 8.1.5

I've been fighting with it all morning. The only thing that MIGHT be fixing it is if I switch the build-for devices to something else and then back, and then if I switch the min ios version to 10.3 and then back. I say Might, because I've tried many times, today, across several apps, and finally

Re: I need a "slider" in a circle

I just uploaded the latest version of RadialDialOmatic to Rev Sample Stacks. > http://livecodeshare.runrev.com/stack/838/RadialDialOmatic > All The best, Roger > On Jul 9, 2017, at 3:56 PM, Roger Guay via use-livecode > wrote: > >

Re: [ANN] Release 8.1.5

Hi Mike, I get that occasionally, not sure why and I cannot pin down a reliable recipe. The error goes away if I retry to build. http://quality.livecode.com/show_bug.cgi?id=19080 Best Panos -- On Mon, Jul 10, 2017 at 4:18 PM, Mike Kerner via use-livecode < use-livecode@lists.runrev.com> wrote:

Re: Goofy question #7234

I wrote this explanation a long time ago for someone else: http://www.hyperactivesw.com/resources_function.html Also, in your command handler example, you don't need "do" which adds unnecessary overhead. This is enough: on mouseUp GoRed end mouseUp -- Jacqueline Landman Gay | jac

Re: modal window = block handler?

Of course, modal windows do not "halt code execution" in that sense. They could not because you would not be able to use any code in front or back scripts. They prevent the calling handler from proceeding. It's like inserting blocking code where the modal is called. Bob S > On Jul 10, 2017,

Re: [ANN] Release 8.1.5

Anyone else getting a persistent "linking for arm" error when trying to build with 8.1.5? On Mon, Jul 10, 2017 at 9:23 AM, panagiotis merakos via use-livecode < use-livecode@lists.runrev.com> wrote: > Dear List Members, > > We are pleased to announce the release of LiveCode 8.1.5 Stable. By > "St

Re: modal window = block handler?

A related issue I ran into recently: I had a complex modal dialog. In my code for the dialog controls I was calling a routine that had a "wait 0 with messages" statement. I discovered that the wait ... with messages allows user events (for example commandKeyDown, etc.) to kick off other scripts w

Re: [OT] Renewing Apple Developer ID Installer Certificate

That's only true for apps in the app store. For corporate apps/apps you distribute privately, you have to rebuild them every year with new certs. On Tue, Jul 4, 2017 at 2:47 AM, Tiemo Hollmann TB via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi Marty, > even if your certificate expi

Re: Goofy question #7234

That is cool. As soon as 9 release candidates are released I will have to look hard at v9. Unfortunately I do not develop for a living (exactly) so I do not have a lot of time for running a DP through it's paces. Bob S > On Jul 10, 2017, at 06:01 , Mike Kerner via use-livecode > wrote: > >

Re: modal window = block handler?

I'm going to have to disagree here. I open windows modally for the specific purpose of halting code in the calling stack until the modal window is dismissed so that I can proceed with input from the user. An Answer dialog is simply a modal stack if I am not mistaken. It's interesting though that

[ANN] Release 8.1.5

Dear List Members, We are pleased to announce the release of LiveCode 8.1.5 Stable. By "Stable", we mean that no reported regressions have been introduced in 8.1.5, compared to the previous Stable release. LiveCode 8.1.5 contains 81 extra bug fixes and new features, compared to LiveCode 8.1.4. S

Re: Goofy question #7234

In the newfangled LC world, you can even do things the way the engine can - using "return for value" (or just "return") and "return for error" to allow commands to return values, too. Then "it" gets values that are returned, and "the result" gets errors that are returned. 9 is fun. funfunfunfunf

[ANN] This Week in LiveCode 90

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 #90 here: https://goo.gl/3kqaRQ This is a weekly newsletter about LiveCode, focussing on what's been going on in and around t

Re: Goofy question #7234

Here is what I teach my students: Use the function to return a value to the calling handler, set the properties in the handler, not in the function itself, like this: on mouseUp set backgroundColor of this card to goRed() end mouseUp function goRed return “red” end goRed The benefit of this

Re: Goofy question #7234

It does help a lot: even if only to stop me looking totally 'Stpid' in front of the kids in my Summer classes. Thanks. Richmond. On 7/10/17 11:09 am, Tim Selander via use-livecode wrote: Hi Richmond This works (both scripts in the button): on mouseUp put goRed() end mouseUp function goR

Re: Goofy question #7234

Hi Richmond This works (both scripts in the button): on mouseUp put goRed() end mouseUp function goRed set the backGroundColor of card 1 to red end goRed I think the general idea is that a function returns information. So date() returns the date. But just having a line "date()" in the script

Re: Widget course

OK, looked at actual widgets and see they have metadata items so I added these and the error disappeared. 1. Seems the minimum requirements for the Extension Builder have changed since the course first written (BTW I am using 8.1.5, when I tried in 9dp7 there were even more errors.) Full of co

Re: Widget course

Hi James, "no version found in..." refers to module metadata - add metadata version is "1.0.0" to the library and it should hopefully install. I think perhaps the section on metadata should be before the install section. On Mon, Jul 10, 2017 at 4:13 AM james--- via use-livecode < use-livecode@li

Re: modal window = block handler?

If you open invisible, then display it, a modal will not block. This non-modal behaviour of a modal has been incredibly useful for displaying a progress indicator in a modal window. I do not consider it a bug as such (modal blocks underlying windows, not necessarily code), and would hope this quir