konva.js behavior when the mouse button is pressed - onmousedown

I ask if konva.js may behave like other graphics libraries as Raphael.js or Paper.js when the mouse is pressed and then leaves the canvas or browser window, this video illustrates the difference in behavior by default.
https://www.youtube.com/watch?v=DeBNJiN_Vdo
Is there a trick to konva.js work the same way?
(google translator)

It is fixed in develop version.
You can get the last build here: https://raw.githubusercontent.com/konvajs/konva/master/konva.js

Related

JetBrains IDEs scrolling on touchscreen

I'm having a problem scrolling in all the JetBrains IDEs (PyCharm, PhpStorm) using touch screen. I have a Dell XPS 15 with a touchscreen.
When I try to scroll it just selects code. I have tried in regular Notepad and Notepad++ and there works as expected.
Has anyone else experienced it? Is there any solution to this? It would be really great to scroll through the code using touchscreen.
I have found temporary solution by installing plugin Code glance (https://plugins.jetbrains.com/plugin/7275). The plugin provides a sidebar with code map, which is similar to the one from Sublime. In the sidebar it is possible to navigate through code. It is not ideal but it's better than nothing.
Yes, I was having the same problem. And luckily I got a gesture to scroll using two fingers:
Scroll up: Tap and hold using one finger and swipe away[from close to distant of the first finger] using another finger. Swiping away from each other also works.
Scroll Down: Tap and hold using one finger and swipe in[from distant to close of the first finger] using another finger. Swiping close to each other also works.

Bringing up the iPad keyboard which is predominantly symbols

Apologies in advance if this is answered but I genuinely couldn't find it. I'm trying to bring up the keyboard type on iPad which appears when pressing the "#+=" button. I've tried going through all the types on the docs and I'm sure that this wasn't successful. Am I missing something or does the user have to click this button every time?
Edit: this question was closed as "off-topic" because it didn't include code or ideas or what I've tried already... Therefore for a bit of extra detail, I used EVERY keyboard type that is available on the docs e.g.
theTextField.keyboardType = UIKeyboardTypeNumberPad;
This did not yield the results that I require, which is the keyboard plane that appears when you press the #+= button because I wanted users to go straight to that one.
Unfortunately, this is impossible. It's not a keyboard type you want, it's a keyboard plane. There is no public API to switch or in any way access the keyboard planes.
One solution could be to create your own keyboard with the symbols you want. Another solution would be to open the keyboard and then generate a touch event that will switch the keyboard plane. However, this would be complicated, non-portable and a bit dangerous.
You have no ability to affect the built-in keyboards.
You can however create your own custom input view which you would set on the inputView of your text editing view before you make it first responder. Then iOS will show this view instead.
Have a look at this project of mine which implemented a "Morse keyboard" (April Fool's joke), but demonstrates how to achieve a custom keyboard that still interacts with a text field as you'd expect. http://www.cocoanetics.com/2012/04/dtmorsekeyboard-tutorial/

Is there a way to focus a popover for a Safari extension?

Just wanted to know if anyone knew how to put the focus on a popover for a Safari extension. Currently, the popover acts as if the window is inactive. This prevents any mouseover events from working and trying to type in any input field is difficult because there is no flashing cursor.
According to a post on the Safari developer forums, this is a known issue with Lion and they are looking into it.

Single finger scrolling panes - how?

See here:
http://dev.sencha.com/deploy/touch/examples/kitchensink/ (click/tap on "Touch Events")
The pane that explains the touch events available, you can drag w/ one finger on an iPad or iPhone, and even on the desktop you can use the mouse to drag/scroll as well. How does this work?! I need to be able to do this without Sensa Touch (we're using jQuery Mobile).
I used iScroll4 and it worked fairly well.
http://cubiq.org/iscroll-4
If you are using jQuery Mobile, you may want to try out their experimental "Scroll View." I haven't ran across a reason to try it yet but it does look promising.
http://jquerymobile.com/test/experiments/scrollview/

Workaround for history animation in Safari for OS X Lion?

In Safari for OS X Lion, when you use the swipe gesture to navigate forward or backward in history, the window animates as though you were moving through physical pages. The problem with this behavior is that many apps already listen for changes in the history state, and respond appropriately -- either when the hash is changed, or when HTML5 pushState is used.
A perfect example is GitHub, when navigating in and out of folders -- https://github.com/johndyer/mediaelement, for example. If you click on a folder, then swipe to the previous page, the end state "snapshot" is shown, and then animated to again from the beginning state, which not only is confusing, but nullifies the informational value of the animation.
Today is my first day using Lion, but I'm curious if any other web devs have encountered this issue, and whether you've found a workaround?
Sadly it seems there's no documentation about this in the Safari Developer Library.
But there is an (ugly) workaround to disable them on your client machine at least.
In the Trackpad settings, if you set Swipe between pages to Swipe with two or three fingers you can use two fingers to do fancy animations, and three fingers if you don't
like them. But it feels really weird, especially because the three finger swipe is in the
wrong direction.
Maybe use Modernizr to sniff out Safari and rely on Safari's native animation instead of your code's animation? I know this doesn't help with consistency, but lets face it... this is a browser we are talking about!
I would suggest that you go into settings and navigate to gestures. Here, you will see a little dropdown bar that contains the options. Select either of the other two options to fix this. Hope I could help!