Why does TaskExecuter Class have beginOffsetDefault() method?

Question

question

Yokota T asked May 10 2023 at 5:02 AM Yokota T commented May 11 2023 at 4:58 AM

Why does TaskExecuter Class have beginOffsetDefault() method?

Hello all,

I am currently reading the Module Development page.

However, I do not understand why the TaskExecuter class has two methods, beginOffset() and beginOffsetDefault().

As shown in the code below, it appears that beginOffsetDefault() is provided to override beginOffset() and hook a specific process.

double MyTaskExecuter::beginOffset(double endspeed, treenode item)
{
    if (xOnly) {
    offsetloc[1] = 0;
    offsetloc[2] = 0;
    }
 
    return beginOffsetDefault(endspeed, item);
}

However, I am not sure how it differs from "return __super::beginOffset();"

Thank you in advance for your assistance.

Software Version:

FlexSim 23.1.1

module sdk dll

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2023-05-10T16:55:18Z

Jordan Johnson answered May 10 2023 at 4:55 PM Yokota T commented May 11 2023 at 4:58 AM

The beginOffsetDefault() function causes "normal" offset travel to occur. By defining this as a function, we are able to avoid repeating code. The TaskExecuter, Operator, Transporter, and Elevator all call this function.

The difference between this function and calling __super::beginOffset() is that TaskExecuter::beginOffset() sometimes modifies the z component of the travel destination. Not all sub classes need that modification, but they do need the rest of the logic in beginOffsetDefault().

Suppose you override the Operator class. Your MyOperator::beginOffset() method, you cannot call __super::beginOffset(), because that would call Operator::beginOffset(), not TaskExecuter::beginOffset(). By creating the beginOffsetDefault() method, base classes can call that method without worrying about any logic added by intermediate classes.

· 1

question