Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: sbarkeruk on April 06, 2005, 07:24:01 am
-
Am using Windows XP and creating a model for fwd engineering with Visual Basic 6.
If I add an attribute and check the Property checkbox, then 'Modify Property Implementation' form appears. If I then check both Read and Write checkboxes, then choose a scope of anything except Public, for both Get Scope and Let Scope this is fine. However, returning to this form shows the Set scope is reset back to Public and the Write checkbox is unchecked!! (Let scope and Read checkbox remain as they were previously set).
This can be reproduced as follows:
1) Double-click a class then select the Details tab.
2) Click the Attributes button then click New.
3) Enter some details (Name, Type, Scope, etc) then click Save.
4) Highlight the newly added attribute in the list then check the Property checkbox.
5) In Create Property Implementation form, set both Get Scope and Set Scope to Package. Also check both the Read and Write checkboxes.
6) Click OK to save changes.
7) In the Attributes form, click the ellipsis button (...) next to the Property Name text.
8) You will see that the Set Scope is set back to Public and that the Write checkbox has been unchecked (i.e. The bug!!).
-
That doesn't look good. :'(
There are some changes to that dialog that will be introduced in version 4.60 (due sometime around the end of the month) I'll put it in with those changes.
Simon
PS. Instead of going through the class properties, detail tab and then to the attributes dialog try just clicking F9. (F10 for operations)
-
How very interesting.. this does not happen for java classes, but does for C# and VB.
:-/
-
Hello Bruce,
C# is actually a different case.
The problem described above only applies to VB and property let properties.
C# (and VB.Net) only have one property method (as discussed elsewhere in the forum) and they only really have one scope. Because we use the getter as that one method for C# and VB.Net the setter scope will never be set.
I'll fix that up so that it's a little more obvious what's going on.
Simon
-
I knew that. :-[
b