Bug 341742 - Only public visibility for adding operations through class property dialog possible
Summary: Only public visibility for adding operations through class property dialog po...
Status: RESOLVED DUPLICATE of bug 352633
Alias: None
Product: umbrello
Classification: Applications
Component: general (show other bugs)
Version: 2.13.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Umbrello Development Group
URL:
Keywords:
: 347368 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-12-10 14:05 UTC by Ralf Habacker
Modified: 2016-01-24 16:42 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 2.17.90 (KDE Applications 15.11.90)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Habacker 2014-12-10 14:05:10 UTC
Adding an operation through the class property dialog only supports "public" visibility. All other visibility settings are ignored.
 

Reproducible: Always

Steps to Reproduce:
1. open umbrello
2. add a class to the default class diagram
3. open class property dialog and select operations
4. Click "New operation" 
5. select "private" visibility
6. click "OK" to create the operation
7. select newly added operation and click on "Properties"

Actual Results:  
The visibility of the operation is set to "Public"

Expected Results:  
The visibility of the operation should be set to "Private" as requested
Comment 1 Daniel Pastushchak 2014-12-14 19:13:42 UTC
Comment from GCI student:
I'm using v2.14.2 and I reproduced this same problem. Using Ubuntu 14.10 with KDE 4.14.2
Comment 2 Ralf Habacker 2014-12-19 07:58:51 UTC
The problem here is caused by the fact that the undo framework requires to have all supported objects in the document object list, which is not true for attributes and operations.
Comment 3 Ralf Habacker 2015-05-07 09:17:49 UTC
A workaround is to set the visibility after creation through the attribute properties.
Comment 4 Ralf Habacker 2015-05-07 09:19:11 UTC
*** Bug 347368 has been marked as a duplicate of this bug. ***
Comment 5 Ralf Habacker 2016-01-24 16:42:26 UTC

*** This bug has been marked as a duplicate of bug 352633 ***