BB10: Rapid charge stand + BB10 dev alphaJune 28, 2012
I was looking for a convenient way to prop up my dev alpha while working on an app, since it's annoying to pick it up every time I run an app. As it turns out, the rapid charge stand for the PlayBook works perfectly -- you can set your dev alpha in the stand and it hold it upright. Obviously it doesn't charge it, but that wasn't the point :)
BB10: Images animating into place when loading QML fileJune 28, 2012
I've noticed that when I load new QML files, the images animate into place.
For example, if the screen contains an image at position X,Y and it is of width W and height H, then the image becomes visible at coordinates 0,0 and has width 0 and height 0, and then animates into place by flying over to coordinates X,Y and growing to eventually be of width W and height H.
If I then click the "Back" button and go to that QML screen a second time, it doesn't animate.
Is this implicit animation intended? While implicit animations are rather amazing and a great tool to have, it seems counter intuitive to have screens use implicit animations when they are first loaded. It creates a rather unpleasant business and visual distraction when the screen is loading.
I thought I could disable this by adding the following to the ImageView controls:
attachedObjects: [
ImplicitAnimationController {
enabled: false
}
]
|
|
... but they are still animating.
Posted question hereBB10: onTouchJune 28, 2012
To respond to a touch event, I added the following:
onTouch: {
navPane.deprecatedPushQmlByString ("mom_dad.qml");
}
|
|
To my amazement, when I ran the code on the dev alpha device and touched the image, it loaded mom_dad.qml five times!
This is because, I would assume, the onTouch event fires when your finger moves on the screen, and you need to limit your "click" event handler to the down event:
onTouch: {
if (event.isDown()) {
navPane.deprecatedPushQmlByString ("mom_dad.qml");
}
}
|
|
older >>
