Bug 86083

Summary: better description for in/out parameter option
Product: [Applications] umbrello Reporter: Sebastian Stein <seb.kde>
Component: generalAssignee: Umbrello Development Group <umbrello-devel>
Status: RESOLVED FIXED    
Severity: normal    
Priority: LO    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Sebastian Stein 2004-07-27 15:14:32 UTC 
Version:           1.3.0 (using KDE 3.2.3, compiled sources)
Compiler:          gcc version 3.3.3
OS:                Linux (i686) release 2.4.26

past KDE 3.3 issue:

During creation of a function parameter, you have to choose the "Kind" setting.
At the moment the options are in, out, inout. Well, this is not very
descriptive, so we have to find something else. Also, i18n() calls are needed
around in, out, inout.
Comment 1 Oliver Kellogg 2004-07-28 21:08:59 UTC 
> At the moment the options are in, out, inout. Well, this is not very
> descriptive, so we have to find something else.

It's the other way round: The values (in/out/inout) conform to the UML
standard, but the designation "Kind" should be replaced by "Direction"
as per the UML standard. (Can't change this for 1.3 because of string
freeze.)
Comment 2 Sebastian Stein 2004-07-29 10:52:14 UTC 
Oliver Kellogg <okellogg@users.sourceforge.net> [040729 10:21]:
> > At the moment the options are in, out, inout. Well, this is not very
> > descriptive, so we have to find something else.
> 
> It's the other way round: The values (in/out/inout) conform to the UML
> standard, but the designation "Kind" should be replaced by "Direction"
> as per the UML standard.

Yes, but then it only makes sense, if you know the UML standard. So it would
be better to have something like:

Direction

Input Parameter | Output Parameter | Input & Output Parameter

> (Can't change this for 1.3 because of string freeze.)

Yes, I know. That's why I have added those bug reports so that we don't
forgot it.

Sebastian
Comment 3 Sebastian Stein 2004-08-18 17:35:05 UTC 
*** Bug has been marked as fixed ***.