Book a Demo

Author Topic: Attribute Position - way OFF?  (Read 7107 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Attribute Position - way OFF?
« on: August 17, 2005, 08:31:22 pm »
Attribute.Pos Read/Write. Position of Attribute in class attribute list.
Looks OK...

In my test project (embedded in a single larger Model file) I have half a dozen classes.  One of them has 3 attributes.  The .Pos values are 0, 1 and 1000!   ???

Further research shows that of the approximately 1000 attributes in the model, 25 have the value 1000!

Anybody know what's going on?

Cheerz,
Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

thomaskilian

  • Guest
Re: Attribute Position - way OFF?
« Reply #1 on: August 18, 2005, 03:11:09 am »
Tried any sanity check for your model?

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Attribute Position - way OFF?
« Reply #2 on: August 18, 2005, 03:35:51 am »
Quote
Tried any sanity check for your model?
If you mean Tools|Data Management!Data Integrity?  That's the first thing I did... :)  No problems - according to EA...

I have a few classes with Max(.Pos) in the twenties, and one with 39, but then there's "daylight" between it and the 25 I mentioned in the original post.

Paolo

Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

AshK

  • EA User
  • **
  • Posts: 137
  • Karma: +0/-0
    • View Profile
Re: Attribute Position - way OFF?
« Reply #3 on: August 18, 2005, 11:27:16 pm »
Hi Paolo,

 I've just replicated the problem here, and can confirm that  this is bug.

I'm finding that the very last attribute created using the Attributes dialog is being saved with a pos of 1000.  Previously added attributes are assigned a correct position.

Sorry for any inconvenience; I'll try and have this problem corrected by our next build.

Ash
The Sparx Team
[email protected]