Double clicking an element does not reliably open inline edit

  • Problem
  • Updated 2 years ago
  • In Progress
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.
Photo of

  • 34 Posts
  • 0 Likes
  • slightly irritated

Posted 6 years ago

  • 24
Photo of Giacomo 'Peldi' Guilizzoni

Giacomo 'Peldi' Guilizzoni, Official Rep

  • 5887 Posts
  • 457 Likes
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)
Photo of Edie RooER

Edie Roo

  • 6 Posts
  • 0 Likes
remove the pop up that say double click. this is really frustrating.
Photo of Michael

Michael

  • 497 Posts
  • 37 Likes
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.
Photo of

  • 1 Post
  • 0 Likes
I have this problem on a Mac, (current version of AIR).
Photo of

  • 5 Posts
  • 0 Likes
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!
Photo of Giacomo 'Peldi' Guilizzoni

Giacomo 'Peldi' Guilizzoni, Official Rep

  • 5887 Posts
  • 457 Likes
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.
Photo of

  • 5 Posts
  • 0 Likes
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.
Photo of Giacomo 'Peldi' Guilizzoni

Giacomo 'Peldi' Guilizzoni, Official Rep

  • 5887 Posts
  • 457 Likes
Ok I made it 400ms, you can test it here: http://www.balsamiq.com/products/mock... - let me know what you think!
Photo of

  • 5 Posts
  • 0 Likes
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.)
Photo of

  • 3 Posts
  • 0 Likes
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.
Photo of Philipp Quaet-Faslem

Philipp Quaet-Faslem

  • 27 Posts
  • 1 Like
Stephen's intitial post suggested there is no pattern to this behavior. I think the pattern is this: A double click only goes to Edit mode if you're not in another element's Edit mode already. So, even single clicking and hitting Enter or F2 does not work without prior exiting the current Edit mode (either with ESC or by clicking somewhere outside the current text edit pane).

Question: Why do we even need to activate the Edit mode explicitly? If you take a look at Visio, you just select an element and type away.

Cheers,

Philipp
Photo of PalminP

Palmin

  • 20 Posts
  • 0 Likes
I have a reliable way of reproducing this, and it is quite annoying: when editing elements within groups, I'd like to be able to double-click into the groups until I can edit the element under the cursor.

This example (two nested groups with a button in it) shows this: Continue double-clicking on the button. 1st double-click goes into Group 1, 2nd double-click goes into Group 2, 3rd double-click does not open the inline editor of the Button. If I move the mouse a little bit after the 2nd double-click, the inline editor opens on the 3rd double-click.

Hmm... does entering bmml work? It shows up in my comment source, but not in the final comment... Please let me know if I should send the example somewhere else.

Group%201

Group%202
Photo of Giacomo 'Peldi' Guilizzoni

Giacomo 'Peldi' Guilizzoni, Official Rep

  • 5887 Posts
  • 457 Likes
Thanks Palmin, I'll add this to our bugbase.
Photo of Edie RooER

Edie Roo

  • 6 Posts
  • 0 Likes
This is confusing because there is popup that says double click but it only requires on click. most application require a double click and everyone is us to double clicking. also fix its soooooo slow.
Photo of Ben Norris

Ben Norris, Official Rep

  • 3613 Posts
  • 175 Likes
I'm splitting this out to get more information and make sure that this new problem gets resolved. Please reference the new topic here: Problems clicking to edit controls