#noSuchAttribute:

[FredF]

Hi,
Sometimes we got the following problem:
1) A part version 1 exist in image I, J and the library, with some attributes.
2) we add an attribute to the part in image I, making version 2
3) load version 2 in image J and try to use the new attribute => error message #noSuchAttribute:
Nevertheless, the attribute is shown in the editor and just click on 'generate runtime code' on the part fixes the problem.
But then we have version 3 to reload in I to keep only last version everywhere.
Now the problem is annoying because we have this problem with parts used in almost all our images, forcing us to make lot of version number just to fix the problem.
I could not, until now, write a scenario which always reproduces the problem, we have only it with "real life" parts.
This is why I am asking the question here: does anyone else also encounter this problem? What's the best solution?
Fred, Brussels, Belgium
(We use version 6.0.3, I hope soon 7.5.2)

[Joost Bossuyt]

Hello Fred,
we also had problems with attributes but not the ones you have.
After changing the abtPartUpdateOperation method in AbtAppBldrNonVisual and AbtAppBldrVisual our problems were solved.
I don't know if this will solve your problem.
Here is de modified code :

Code: Select all

abtPartUpdateOperation

   | result |

   (result := AbtAppBldrPartClassUpdate forClass: self)
   partBuilderRecord codeGenerationParameters rehash.
   ^result

Greetings,
Joost

[FredF]

Thanks Joost.
It seems that things still happen with vast in Belgium! We will soon need a belgian user group .
As soon as we have this problem again we will try your solution.
Fred

[Joost Bossuyt]

It seems that things still happen with vast in Belgium! We will soon need a belgian user group .

Well... The Belgian Smalltalk User Group is back since past month