How much money can I give you to PLEASE stop selecting ancestor elements in the outline?

Dave shared this question 3 years ago
Answered

First of all:


030611d0395f0e4643e6c0c53c66e902


But, you see, I AM shouting. This bug is costing me money. Every. Darn. Day.


With that out of the way...


I have already filed another bug about this, but I would be more than happy to double my monthly fee to move it to the top of your list.


When I modify an item nested several layers down the outline, Justinmmind insists on selecting some (unknown to me) number of layers up the tree, which in almost every circumstance, is exactly the wrong thing to do. It hinders productivity and sometimes actually damages my work.


For example, I select a (somewhat deeply nested) item, and use the cursor keys to nudge it a pixel one way or the other. On some — but not all — occasions, this random selection of ancestor items causes the focus to now be on parent or grandparent elements, so that the next press of the cursor key moves things that I did not select.


At the very least, it is annoying, in that if the deepest-nested element — or any ancestor up the tree — is part of a long list of elements, then Justinmind's insistence on selecting ancestor elements moves the desired element out of view, and makes it impossible to continue without fiddling around with the scrolling of the outline.


Thank you for letting me rant.

Comments (13)

photo
1

Hello Dave,


We're sorry to hear you're dissatisfied with JustInMind. We thank you for taking the time to bring your concerns to our attention. Our team is working diligently to increase usability, while incorporating suggestions from our fellow JustInMinders. We are terribly sorry for the inconvenience this may have caused, and look forward to producing a resolution in the future.


Regards,


Luisa

photo
1

I don't mean to leave you with the impression that I am entirely dissatisfied with JustinMind: on the contrary, I'm very satisfied overall with it.


I wrote this post when I was frustrated, and I apologize for its harsh tone.


I appreciate that the good people at JustinMind are working to improve its usability, and impressed with the number of improvements I've seen in half a year or so of using it daily.

photo
1

That said, I would gladly make a donation to bump this bug, along with the weird auto-scrolling that makes it difficult to align elements when nudging them within dynamic panels, to the top of the backlog. :-)

photo
1

Hello. It's version 7.0.0, and this problem is still here. It's brutal.


In the work I've done since upgrading to 7.0.0, I've probably lost at least an hour or two (which, if I billed my time hourly, would be way more than a month's subscription to JustinMind) to fixing things that got ruined when I *thought* I was resizing a background rectangle, but (because JustinMind changed the selection to the parent group behind my back) I was actually resizing the entire group, and in just quitting and restarting JustinMind (and restoring all of my context: I'm not always working on the default screen, and losing my focus because I have to spend time managing JustinMind's selection rather than building prototypes under deadline pressure).


Moreover, there is a long-standing bug in which it is impossible to undo the resizing of a group: if you resize a group—which Justinmind makes far too easy to do accidentally—you might as well delete it and start building it from scratch, because Undo does not restore the group's contents to their size and position before the resize. It simply does not.


Incidentally, it seems to be a bug related to how long JustinMind has been running. For the first hour or so, I rarely see it. The longer I work, the more likely it is to occur. I have no idea if it is strictly time related, related to the number of edits I've made, related to the number of items whose layering in the outline I've changed: I do all those things, and I do not keep a log of every change that I make so that I can report it to you.


As you can tell, I am extraordinarily frustrated about this.


Victor Conesa can tell you how much of a fan I am. But this is a really serious and infuriating combination of bugs (the focus changing and the inability to undo group resizing that is caused by the focus changing). I wish someone would be able to put a finger on what's happening and why.

photo
1

The JIM Team's response is very slow, :(

photo
1

Hi, JiM Neighbors,


It happened again today, cost me another 10 minutes to clean up the mess.


That's all. Just thought I would record every occurrence in this thread 'til it's fixed.


As long as I'm already losing time due to this persistent bug, why not lose another minute writing a note to you?

photo
1

Another 15 minutes gone, this time because the Undo doesn't actually undo resizing a group when it becomes selected.


Did I mention I'm on a deadline and these lost minutes actually matter? Yeah, I did.

photo
1

Hi Dave ,


Thank you for your reminder . As this is an issue that happens randomly our development team is trying to find out the specific cases in which this is happening. Any information you can provide will help us on our investigation .


Thank you for your patience and sorry for any inconvenience .


Best,


Sonia Duran

photo
1

The only thing that seems certain is that it happens more frequently the longer I use JustinMind. After a restart, it seems to behave, but once I get into the swing of things, in a "groove" and making progress (and not keeping an eagle eye on the outline), it happens again.


Other than that, I'm not sure how I could effectively capture the sequence of events that leads to it: 100s of edits typically happen in a session, it's not at all clear which of them causes the problem. I feel like I'd have to do a complete screen recording while I use JustinMind all day, and that's impractical.

photo
1

May be you should capture screen video for an hour for example to catch that bug and sent the video file to support?

photo
1

I have done so on other reports related to this bug. I'm pretty sure that our good friends at JustinMind are aware of the issue by now, but thank you for your suggestion.


If you have experienced this issue (which would be my assumption, since you're weighing in on this bug report), then perhaps you could capture it in a video.


If you haven't experienced this issue, then why are you even commenting here?

photo
1

No I haven't experienced it yet. Just wanted to help.

photo
1

Thanks. This is a very helpful community.