Difference between revisions of "Bug: EVENT TYPE CUSTOM COMMAND COMPLETE not being handled"

From Dragon Age Toolset Wiki
Jump to: navigation, search
(Created page with '*'''Version found:''' <!-- v1.0.1008.0 --> *'''Status:''' Open == Description == <!-- Trying to signal an EVENT_TYPE_CUSTOM_COMMAND_COMPLETE at the end of a conversation sometim...')
 
Line 1: Line 1:
*'''Version found:''' <!-- v1.0.1008.0 -->
+
*'''Version found:''' v1.0.1008.0
 
*'''Status:''' Open
 
*'''Status:''' Open
  
 
== Description ==
 
== Description ==
<!-- Trying to signal an EVENT_TYPE_CUSTOM_COMMAND_COMPLETE at the end of a conversation sometimes will not work. It can depend on how long you remain in conversation mode (rushing through the conversation usually makes it work, while delaying usually causes it not to work). Any other event fired at the end of a conversation will work perfectly. Also signaling an event at the end of a conversation and having that signal an EVENT_TYPE_CUSTOM_COMMAND_COMPLETE does not work. The first event will fire properly but the second won't get handled. -->
+
Trying to signal an EVENT_TYPE_CUSTOM_COMMAND_COMPLETE at the end of a conversation sometimes will not work. It can depend on how long you remain in conversation mode (rushing through the conversation usually makes it work, while delaying usually causes it not to work). Any other event fired at the end of a conversation will work perfectly.  
 +
 
 +
Also, signaling an event at the end of a conversation and having that signal an EVENT_TYPE_CUSTOM_COMMAND_COMPLETE does not work. The first event will fire properly but the second won't get handled.
  
 
== Workarounds ==
 
== Workarounds ==
<!--  -->
+
 
  
 
[[Category:Toolset bugs]]
 
[[Category:Toolset bugs]]

Revision as of 19:58, 17 June 2010

  • Version found: v1.0.1008.0
  • Status: Open

Description

Trying to signal an EVENT_TYPE_CUSTOM_COMMAND_COMPLETE at the end of a conversation sometimes will not work. It can depend on how long you remain in conversation mode (rushing through the conversation usually makes it work, while delaying usually causes it not to work). Any other event fired at the end of a conversation will work perfectly.

Also, signaling an event at the end of a conversation and having that signal an EVENT_TYPE_CUSTOM_COMMAND_COMPLETE does not work. The first event will fire properly but the second won't get handled.

Workarounds