Forum Replies Created
Hi rollesYea also did that, problem is though that even if the piece is in place and the user's finger is still on the pieces, it repeats the sound. I think for the other questions you have best follow Otterside's advice for now. I havn't tried it myself yet. It seems do-able, but with a bit of extra scripting.good luck, hope you come right. I will post any new findings as well.hein
many thanks Otterslide, that is super helpful. I'll wrap my head around it this morning and see if i can get it to work.awesome sauce!
what I've found sometimes is if I don't close corona between publishes then it hangs as well, but yea, I've also had to close and open once or twice in the past, but havn't had issues since the latest build download ( of kwik2 that is )h
many thanks for the awesome tut Alex. Just busy doing it now and gonna make a puzzle app soon. Worth mentioning that if you want the piece of the robot the user is dragging always at the top of the display stack, add this to the start of the action for each piece:objectName:toFront() ---replace object name with the layer name that is dragable.This ensures that whatever piece the user drags is always at the top and won't float behind other pieces when you drag it to its place.
Hi ChrisIm assuming you've got the "use native font" check box cheched? I also found that the text layout looks different to what I had initially in photoshop. You can try unchecking the box and make sure the font you are using is included in the build folder when you publish.regardshein
UPDATE: I've managed to integrate some of Peach Pellen's code from a tutorial she did here:http://corona.techority.com/2010/11/19/control-an-actor-with-the-accelerometer/I just needed to invert the x and y axis and subtract the motiony and x values instead of adding them. Not too sure why just yet, will keep digging at the problem and try understand why that's the case. I'm assuming its got something to do with the orientation setup? Her example builds fine and runs as expected. Will post any new findings.Many thanks to Peach for that code btw 😉October 16, 2012 at 7:04 am in reply to: [DONE]Copy and paste components & rename components #13126
agreed! had to sit and duplicate the same action 45 times for 45 pages. takes ages. That said, im new to app development and kwik, so with time I will prob learn to streamline workflow better.
Hi Alex, thanks for getting back to me. I tried the method you suggested. No joy unfortunately. The move/scale action makes the layer jump to the specified x value set in the move/scale property box. I downloaded the project files for the “drag” tut on the website. The project opens with a slider and a red ball that scales up when button is released. When I set that to onDrag, i get the result I want, but only in the one direction. Moving the slider back doesn't scale it back down. In fact, it keeps scaling the ball up. I'm assuming the logic would be the same for my project where the slider is just replaced by the cube and the red ball by the tree. Also then moving the tree in the x direction instead of scaling. Problem still remains, the -x direction.hope it makes sense.h
Also had the same problem yesterday. I just deleted the action/ animation and re-built it with 2.07 build. Works fine. I only have one display object fading in though, so I didn't mind re-doing it. Will try the hide/show method as described above as well for future objects.