Dynamic dispatch in State Pattern design

[FilActor85]

Good afternoon, I started using actor framework and State pattern design few weeks ago and now I find myself into trouble about dynamic dispatch behaviour in a State Pattern design. I created a parent Actor (A for semplicity) inheriting from "State Actor" class. I created 2  class A's child classes (B and C). I implemented, as reccomended in documentation, the overrides of "Actor core" (for class A) and "substitute Actor" (for class A), transition methods for (class A, B, C) and one other method to pick a numeric value (Pick_value.vi). The last one has been implemented either in class A and B and C. When I use this method as "vi" in other method --> it works properly and the dynamic dispatch is respected. When i use it by calling with a message (send ...) the dispatch doesn' work.

What I mean is, after change the state from B to C and then call method on C (by message), the numeric value generated is from B implementation of the method, not from C implementation.

Are there any recommendation or flags to check, etc ?

Hope someone could help me

thanks a lot

Thanks

[BertMcMahan]

Could you attach your code? I suspect your "switch actor" has some issues.

[FilActor85]

I'll post the code as soon as I can. In the meantime I can tell you that switching actor should work fine (as far as i Know). I tried to use popup window to verify it and the actor changes states and executes "Entry" method properly.

[FilActor85]

That is the "substitute actor" override. At this stage of the development I don't have data to share between actors. I have just put "to more specific class" for future data exchange.

Thanks

[FilActor85]

I have just posted an example with 2 childs actor A and B and a Father actor. I tried to use "substitute actor" without any inheritance from "state actor" class. If I change state from A to B and call the method "ciao" only the B implementation of ciao is returned.

[BertMcMahan]

Could you backsave to 2023 or prior? I don't have the newest version yet.

[FilActor85]

As request 2023 version.

Thanks for your kind support

[FilActor85]

I found the issue. The "Do.vi" of the messages referring to the transitions methods were not connected properly. I did them by the automatic "create message" and refreshed with"rescript message" functions but the connections were still wrong.

I changed manually the connecttions and it works. Hoping these help someone on the AF way.

Thanks