Loading Profile...
Double clicking an element does not reliably open inline edit
Quite often double clicking has no effect other than selecting the element.
The rest of the times the inline editor correctly opens.
I haven't found a pattern. Triple-clicking always opens the inline editor.
The rest of the times the inline editor correctly opens.
I haven't found a pattern. Triple-clicking always opens the inline editor.
I’m slightly irritated
11
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has a solution in progress.
-
Inappropriate?Hi Stephen, I'll take a look. You can also simply hit the enter key or the F2 key to open the editor as well (I find those faster than double-clicking)
-
Inappropriate?I have found this too, and have taught myself to to single click an element and then hitting enter to edit the text. I do this also because many times a double click will shift an element a little which messes up all my nice alignment. -
Inappropriate?I have this problem on a Mac, (current version of AIR). -
Inappropriate?Before discovering this thread, I experimented to try to get as specific as possible about this problem. The simplest explanation seems to be that Mockups ignores the system double-click speed, and has its own much faster double-click speed requirement:
- A super-fast double-click always works as expected for me, except for sometimes opening the previous editor rather than the one just double-clicked.
- Selecting the desired element with a single click first always produces the expected behavior for me when I then double-click.
That makes me think it's a setting in the runtime or in Mockup's development project. It certainly wouldn't be the first time a cross-platform GUI runtime does something weird!7 Comments
Add a comment
This solves the problem
-
Hi Troy, you got it right. Flash/AIR does not have an API to get the system's double-click speed, so I had to use my own timer. Maybe I should slow it down some? -
It looks like the default for Windows is 500 ms. I don't know what Flash/AIR are capable of, but there's a Win32 API function GetDoubleClickTime(). In case AIR can read the Windows registry, I found my user-setting for it at "HKEY_CURRENT_USER\Control Panel\Mouse\" in the "DoubleClickSpeed" value, a string of "500".
-
oh wow really? I have 200ms now...time to up it to 400 at least. I'll check it in so that we can test it in the pre-release version.
-
Yep, and that 500 ms seems like an eternity, but anything faster feels broken. I look forward to the next build! Working with Mockups has put the fun back into a project I'd stalled on.
-
Ok I made it 400ms, you can test it here: http://www.balsamiq.com/products/mock... - let me know what you think!
-
Funny, talking about the 500 ms delay: Raymond Chen posted something vaguely related today, confirming the 500 ms in the process. (Later: I just saw the date, and it turns out it wasn't actually today, but it only turned up in my RSS reader today. Go figure.)
-
I also have this problem and find it quite time-consuming. I have also learned to click once first to activate the item, then double-click, but this is somewhat irritating. When the item is open for editing, the same thing occurs, I have to click one first to position the cursor and then double-click again so that I can activate a word. It would be great if just double-clicking would do the trick.
EMPLOYEE
