IMPORTANT:
this is not a Support Forum! Experienced users might answer from time to time questions posted here. If you need a professional and reliable answer, or if you want to report a bug, please contact Altova Support instead.

Profile: Tis
About
User Name: Tis
Forum Rank: Newbie
Real Name:
Location Waalre
Occupation:
Interests:
Gender: None Specified
Statistics
Joined: Monday, April 25, 2016
Last Visit: Monday, April 25, 2016 11:02:23 AM
Number of Posts: 1
[0.01% of all post / 0.00 posts per day]
Avatar
Last 10 Posts
Topic: do function at state machine initialize
Posted: Monday, April 25, 2016 11:01:39 AM
I use the onEntry function at many (composite) states and observed that these functions are all executed when an initial state has a connection to such a (composite) state. This item has already been discussed: https://www.altova.com/forum/default.aspx?g=posts&t=1203

So, to workaround this unwanted feature, I changed the onEntry function to a "do / function()" .
However, also this do-function() is executed when the first trigger causes an Initialize().
In the generated code the do-function() is indeed called in a generated snippet: public override void entryState() { my-do-function }

So, this is fairly illogical : a "do" has nothing to do with initialization.

Is there a way to still use the do function as intended, or must we workaround around this bug in the same way as the mentioned onEntry discussion ?

Use of the Altova User Forum(s) is governed by the Altova Terms of Use.