Bug 983221 - Unable to select single locked element with left click.
Summary: Unable to select single locked element with left click.
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER5
: 6.0.0
Assignee: Tihomir Surdilovic
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-10 18:26 UTC by Marek Baluch
Modified: 2020-03-27 18:04 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 18:04:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Marek Baluch 2013-07-10 18:26:47 UTC
Description of problem:
When an element in the process designer is locked using the "lock process part" feature then it's not possible to select a single element using the left mouse button and unlock it.

Version-Release number of selected component (if applicable):
Upstream Beta5


How reproducible:
1) create a process containing a start node and a end node.
2) select the whole process and use the lock feature.
3) now try to select the start node using the left mouse button

Comment 1 Marek Baluch 2013-07-11 20:08:02 UTC
Looks like this may actually be intended behaviour.

Is the lock mechanism reached by preventing the user to show the properties panel? See https://bugzilla.redhat.com/show_bug.cgi?id=983732.

Comment 2 Marek Baluch 2013-07-12 14:25:01 UTC
Found in DR6 (Beta5).

Comment 3 Tihomir Surdilovic 2013-08-27 13:52:10 UTC
You have to highlight the node and click the unlock button to unlock it. Same works if you highlight several locked nodes.

Comment 4 Marek Baluch 2013-08-27 13:57:07 UTC
Any particular reason why viewing the properties of a locked element is forbidden?

Comment 5 Marek Baluch 2013-08-27 14:05:14 UTC
I really think it should be possible to select a node using the left click as that is the most common way to do so. Highlighting (hold_left_button-select_elements-release_left_button) is IMHO only an advanced way to use when you want to select more elements without using the ctrl key.

Comment 6 Prakash Aradhya 2013-09-16 18:53:27 UTC
Internal Whiteboard: Beta Blocker → Blocker
Not critical for Beta, but need to address for GA

Comment 7 Tihomir Surdilovic 2013-09-17 17:56:15 UTC
A node that is locked should not be selectable. You can still unlock it by dragging over it. The properties are hidden because of another BZ that requested that feature :) 

I don't think making locked nodes selectable is the way to do.

Comment 8 Marek Baluch 2013-09-20 11:58:27 UTC
The issue is that if you can select the node then can also edit it. And you can select it by dragging over it (as you said). That means that the node is not really locked.

It's possible that I just don't understand this feature. What is it supposed to do? Is it a traditional lock/unlock which is supposed to prevent a user from modifying the nodes properties? Or is it something else?

Comment 9 Prakash Aradhya 2013-10-17 17:42:17 UTC
Tiho,
Can you take another look at this issue and clarify ?  I am completely lost in the description.

Comment 10 Marek Baluch 2013-10-18 08:07:47 UTC
Prakash,

have a look at the video attached here: https://bugzilla.redhat.com/show_bug.cgi?id=1020704

It shows the lock feature. I believe that should put things into perspective.

Comment 11 Tihomir Surdilovic 2013-10-21 14:10:46 UTC
Here is the article http://surdilovic.wordpress.com/2012/05/19/jbpm-designer-locking-and-unlocking/

Locked nodes have to be "selectable" via dragging over one+ nodes to they can be unlocked. This feature helps during development of the process model for a single user or multiple users that collaborate over it. 

We fixed the properties not being editable for locked nodes. That IMO fixes the issue really.

Comment 12 Marek Baluch 2013-11-01 11:23:47 UTC
I think it's confusing but if that's the design then so be it. I guess that if customers won't like it then we can still sit down discuss things over and come up with improvements.

I will verify and close when the fix will make it into a build. 

Thank you Tihomir.

Comment 13 Marek Baluch 2013-12-04 07:27:09 UTC
Verified on ER5.

Comment 14 Lukáš Petrovický 2014-02-07 16:15:26 UTC
This BZ has been part of the 6.0.0 stream.


Note You need to log in before you can comment on or make changes to this bug.