| Summary: | better description for in/out parameter option | ||
|---|---|---|---|
| Product: | [Applications] umbrello | Reporter: | Sebastian Stein <seb.kde> |
| Component: | general | Assignee: | Umbrello Development Group <umbrello-devel> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | LO | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Sebastian Stein
2004-07-27 15:14:32 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.)
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 *** Bug has been marked as fixed ***. |