Summary: | Entering a non-exisiting type in the operation return value combobox should automatically create that class | ||
---|---|---|---|
Product: | [Applications] umbrello | Reporter: | Ernesto <ernesto.vallshernandez> |
Component: | general | Assignee: | Umbrello Development Group <umbrello-devel> |
Status: | CONFIRMED --- | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | RedHat Enterprise Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Ernesto
2007-04-23 11:42:05 UTC
Cannot confirm. Please give the exact steps that you did. Are you starting with an empty model? If not then please attach the XMI file for which this happens. > Cannot confirm.
I forgot to mention I did not try it with 1.5.3 but with the latest
version, 1.5.7beta1. And also with SVN HEAD on branches/KDE/3.5/kdesdk.
The point is that I can select the return value, but this value not always appears in the signature of the function. I think that return values only appear in the signature when they are basic types like bool, int, etc. Furthermore, the combobox named Type has always the same size; the combobox is not resizable according to the size string of the types. As a consequence, it is not easy to choose the disable return type. > The point is that I can select the return value, but
> this value not always appears in the signature of the
> function.
Ah. I think I did see this problem once but when I tried to
further investigate, it no longer happened.
|