A little summary about scope of variables and attr_ (my 2 cents)

Trying to explain this attr_ use of mine and why I said it is ‘module level scope’ here. See diagram attached.
I have 5 classes, each a file. the 3 left ones need the 2 others (double inheritance).
( Tran at the bottom is a class method needed almost every where, in a 6th file)
Method a gets the infos of a Sketchup::Group
and then calls method b (with args) which determines which method to call in Cad.
Method c needs the id of that group. I did not want to use one more argument, to much repercussions, so I tried attr_ as shown.
Works fine. But is it strong ?

Merci Kengey. I will have to read this quite a few times to grasp it.