Declaring public variables

[confusion123]

Is it good practice NOT to declare variables publically but instead define a class?

So in place of this in a standard module:

Public FileNumber As Integer

use this in MyClass

Private mintFileNumber As Integer

Public Property Get FileNumber() As Integer

    FileNumber = mintFileNumber

End Property

Public Property Let FileNumber(ByVal FNumber As Integer)

    mintFileNumber = FNumber

End Property

but I still need to add this in a standard module:

Global MyFileNumber As MyClass

Thanks

 

[RoryA]

When you work with the Ribbon you often need to store a reference to the IRibbonUI object so that you can then invalidate controls or the whole ribbon in code (eg to refresh captions, lists, enabled/visible status). The problem is that any unhandled errors destroy your object reference so your code won't work (and you only get supplied the object in the ****** callback when the workbook is loaded). The only workaround I know of is storing the memory address and then using CopyMemory to restore it.

Anyway, this is both irrelevant and moot here.

 

[Kyle123]

Haha that's horrible!! - Think I'm glad I haven't been subject to that gem, though I've done something similar before to sort out some circular references.

But why wouldn't it work? Having cast my eye over your code I don't see why it wouldn't work in this context. The class will get reinitialized if state is lost and called again - can't you just stuff the object hydrating code in the class init?

 

[RoryA]

Yes, but I was hoping this might have been a means to avoid the need for rehydration.