IpfcSolid.Regenerate() throws an exception IpfcXtoolkitBadContext
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
IpfcSolid.Regenerate() throws an exception IpfcXtoolkitBadContext
Does anybody else find it odd that IpfcSolid.Regenerate() does not support WF5 default no-resolve mode.
The following is a snippet from the documentation.
--------
Pro/ENGINEER Wildfire 5.0 introduces the No-Resolve mode, wherein if a model and feature regeneration fails,
failed features and children of failed features are created and regeneration of other features continues. However,
VB API does not support regeneration in this mode. The method IpfcSolid.Regenerate() throws an exception
IpfcXtoolkitBadContext, if Creo Elements/Pro is running in the No-Resolve mode. To continue with the Pro/
ENGINEER Wildfire 4.0 behavior in the Resolve mode, set the configuration option
regen_failure_handling to resolve_mode in the Creo Elements/Pro session.
Note: Setting the configuration option to switch to Resolve mode ensures the old behavior as long as you do not retrieve the models saved under the No-Resolve mode. To consistently preserve the old behavior, use Resolve mode from the beginning and throughout your Creo Elements/Pro session.
-------
Is it basically saying that the vb api toolkit should not be used during standard user sessions of Pro/E? Is there a different command that will regenerate the model after it has been changed in default no-resolve mode?
Joe
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
- Labels:
-
General
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi,
there is no other command that I know, but you can use the config option.
Check if WF 5 or not on your preffered way.
SaveConfigOption("regen_failure_handling")
SetConfigOption("regen_failure_handling", "RESOLVE_MODE");
regenerate
if errors regenerate again
if errors regenerate again
ResetConfigOption("regen_failure_handling", "NO_RESOLVE_MODE");
finished. : )
Best Regards,
Eike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
thank you