Re: Editing polygon points

You can alt-drag from another point to get a new point. :-Håkan ___ http://www.exformedia.se Check out my new iOS game at http://appstore.com/swapatiswap 7 mar 2013 kl. 16:38 skrev Jim Hurley : > Adding points is tricky. But you can just add a new line to the Points and

Re: Sending mouseUp

Thanks for the suggestions everyone. Here's where I'm at. Craig: I moved the code to openCard, still the same problem. Mike: wait zero didn't fix it, nor did send in time with full path. Mark: Restructuring the code does, of course, work and is probably going to have to be my workaround. The re

Re: Sending mouseUp

There's a lot of stuff that doesn't work on preopenstack if your stack is the premier mainstack of a standalone. This includes liburl, all externals, url (files too), and some other things. Just now someone couldn't speed up a complex object creation with "lock screen", so it seems that doesn't

Re: Sending mouseUp

Hi Björnke, Am 20.03.2013 um 17:59 schrieb Björnke von Gierke : > There's a lot of stuff that doesn't work on preopenstack if your stack is the > premier mainstack of a standalone. This includes liburl, all externals, url > (files too), and some other things. but this is caused by the way Live

Re: Sending mouseUp

Hi Bjornke, Yes, I've run into some of those issues with rev libraries and found that shifting them to openCard fixed those issues. I must have missed the post about the lock screen issue, but I've had that same issue too. This is a new type of problem though, at least to me. No libraries or ext

Re: Sending mouseUp

Peter Haworth writes: > I guess I'm just very suspicious of anything other than really > straightforward commands in preOpenCard now. Well, here's the thing. It's *pre*OpenCard because the card and its controls haven't been instantiated yet. So sending a message to a control that doesn't officia

Re: Sending mouseUp

Oh duh. So even if its a send in time, and the control DOES exist by the time the send kicks in, the underlying stuff doesn't get set right when the send is queued so it doesn't work? That actually makes sense. Think I'm going to start changing how I structure things from now on. On Wed, Mar 20

Re: Sending mouseUp

I set the visible of a stack to false, and put this in the stack script: on opencard send "set the visible of me to true" to me in 5 seconds end opencard I didn't try it in a standalone, but opening that in the dev environment resulted in no visible change for 5 seconds, then the stack appeare

Re: Sending mouseUp

OK, that makes sense, but how come I can set the text of option menus, fields, etc without a problem if they don't exist yet? More to the point, why isn't there some sort of runtime error if I try to address a control that doesn't exist yet (Monte?)? That's what I mean about preOpenCard being unr

Re: Sending mouseUp

Thanks Geoff. I had thought about moving things into openCard. I already found I had to move some code that used libURLxxx from preOpenCard to openCard because of the library not being loaded. Didn't think of the visible part of it though, thanks for the idea. Pete lcSQL Software

Re: Sending mouseUp

Maybe I'm missing a subtlety of Mark's reply, but unless an object is being created dynamically, it should be configurable during preOpenCard. The whole reason for the preOpenCard message in the first place is to be able to initialize/format stuff on the card before showing it. Now if a control ha

Re: Sending mouseUp

Hi Scott, That's my confusion too. I have several places where I adjust the content/appearance of controls on the card and that all works fine, only sending a message to a control seems to cause a problem. It seems like the stack is in some partial state of initialization during preOpenCard where

Re: Sending mouseUp

Scott. I think from the original discussion, the card is not really "live" yet, in that it has not been loaded into memory. So the object exists, but has not arrived. This is earlier than what you characterized as simply not shown yet. Rather, it isn't yet. The "mouseUp" message would have bee

Re: Sending mouseUp

All: So here is another test. Make a brand new stack. Put this into the stack script: on mouseUp dispatch "mouseUp" to this card answer it end mouseUp If you start with a new session, opening the test stack from the finder, you will get an error: TypeHandler: can't find handler

LC Android Apps

There has been quite a lot of discussion, mention, announcements, etc. for apps developed in Livecode for IOS. In fact, the runrev Showcase/Solutions page shows over a dozen of them, and many more are listed in Peter Woods "1001 things to do with Livecode". There's been much less mention about

Re: Sending mouseUp

Hi Craig, You're right that the button wasn't fully qualified initially, but no error was thrown. That's another problem I've come across in preOpenCard - often errors just don't get thrown. Plus red dot break points don't trigger (although a breakpoint command does). All in all, preOpenCard is

Re: Sending mouseUp

Out of curiosity I created a simple stack with one card and four buttons named "Button 1" though "Button 4", each button just had the script; on mouseUp answer the short name of me end mouseUp then I put the following in the stack script; on preOpenStack testMessage1 end preOpenStack on

Re: Sending mouseUp

Yep, that's my experience too. Don't remember all the combinations I tried but here's the one that really surprised. 1. Ran LC and opened my stack from within it. Got the mouseUp problem. 2. Closed the stack and opened it again from within LC. All worked OK. 3. Closed the stack and removed it f

[OT] programming video courses bundle

If you are interested in programming for the web, iOS, android or promoting your business, there is currently a "pick a bundle" promotion at https://www.pickabundle.com/courses/ You can pick 6 video courses in a choice of 19 for $59.99 (yes, that's 60 dollars). I have picked courses on HTML, CSS,

Re: Sending mouseUp

Paul. I wonder if the "answer" command has thrown a monkey wrench into the timing of these events. I assume you dismissed each of the dialogs as they appeared, but who know what evil lurked in the heart of LC when this sort of stuff appeared, and lingered, on screen. Can you do it again, loadi

Re: Sending mouseUp

Do you pass the messages as well in your problem stack? i.e. pass preOpenCard, etc. The IDE is dealing with a lot of things that a standalone isn't dealing with. Just a thought, Tom -- Tom McGrath III http://lazyriver.on-rev.com mcgra...@mac.com On Mar 20, 2013, at 5:07 PM, Peter Haworth wro

Re: Sending mouseUp

Hi Tom, I've changed my scripts so much that I'm not sure of the answer to that. Good point though - I'll see if I can find a backup copy of the stack from before I started changing it all around. The dictionary seems to indicate it doesn't matter whether you pass preOpenCard or not, at least in

Re: Sending mouseUp

Craig, I changed the button scripts to put their names into a global variable and the stack script to answer the global at the end of the openCard handler, the answer was in exactly the same order, nothing missing. Paul On 2013-03-20, at 2:14 PM, dunb...@aol.com wrote: > Paul. > > > I wond

Re: Sending mouseUp

Peter: You may be done with this whole issue, but one thing you might try is verifying that your stack is actually removed from memory before testing as you describe. If the stack you're closing has a substack that doesn't get closed, or there's some handler, pending message or other event execut

Re: LC Android Apps

Alex Tweedly writes: > I'd also welcome any comments on what you can / can't do on Android, No sockets. At work we had to give up on LiveCode for Android and now I'm in Flex hell. I hear the CTO at Adobe just defected to become a VP at Apple. Now I'm really scared, but maybe they can just isola

Re: Sending mouseUp

Thanks Scott, good thought. Not about checking openStacks, the bit about "nuking the entire site" :-) Pete lcSQL Software On Wed, Mar 20, 2013 at 2:29 PM, Scott Rossi wrote: > Peter: > > You may be done with this whole issue, but one thing you might try is > verifying

Re: LC Android Apps

On 3/20/13 3:57 PM, Alex Tweedly wrote: So - does anyone else have any Android apps developed in LC ? Or are we so fettered by lack of externals (and so by lack of Monte's help :-) that it is hard to develop a shippable Android app ? Casey's Solitaire was released for iOS and Android both, sim

Re: LC Android Apps

On 21/03/2013, at 7:57 AM, Alex Tweedly wrote: > Or are we so fettered by lack of externals (and so by lack of Monte's help > :-) that it is hard to develop a shippable Android app ? I have been a little fettered (I maintain a couple of Java android projects that would be good candidates if we

Re: LC Android Apps

I'm in the end of a customer's m-commerce oriented app project witch should be published on both iTunes Store and Google Play as soon as some logistical tasks are going to be up on the customer's services side. Best, Pierre Le 20 mars 2013 à 23:02, J. Landman Gay a écrit : > On 3/20/13 3:57 P

Livecode iOS Externals and XCode 4.6

I am trying to build and test a simple iOS external using the Livecode iOS Externals "LiveCodeSDK-R14" following the instructions at http://www.runrev.com/developers/documentation/externals-sdk/. My mac is running 10.8 with LiveCode 5.5.4 and XCode 4.6 with iOS SDKs for 5.1, 6.0 and 6.1. No

Re: Livecode iOS Externals and XCode 4.6

On 21/03/2013, at 12:16 PM, char...@techstrategies.com.au wrote: > Has anyone got the iOS externals SDK working with XCode 4.6 and LiveCode > 5.5.4? Yes, and Hi from From Tasmania ;-) It sounds like you're not building for the correct architecture. In Xcode are you building for the simulator

Re: Xcode 4.6.1

Yeah, I ended up reverting back to Xcode 4.5.2 and then was able to select the Developer location as you suggested. So now I'm able to build which is great. But, I can't move builds over to a couple of our devices because they require Xcode 4.6. On Tue, Mar 19, 2013 at 6:44 PM, Rick Harrison wr