Features:

1. The code generation function for automatic event (posted by a database trigger for example) 
 is implemented. Connect the message 
with a data, the corresponding JACK code will be generated in the event's code file. User 
can type in the post condition in the message's descriptor. They will appear in the 
generated code as comments.

2. When users mark a percept as 'EXTERNAL TO SYSTEM' by tickling the checkbox on 
descriptor, PDT does not generate ANY CODE for this percept. 




Bug Fixes:

1. When clicking the entity cell on Analysis Overview, the entity information does not 
show up in the descriptor panel.

2. When user drags the graph cell on any diagram, the corresponding entity information is 
not shown on the descriptor panel.

3. When generating skeleton code, if there are some links from beliefs to events, 
gratuitous PDT parse errors are printed out on code generation panel.
 
4. To delete some protocol which possesses special AUML text may compromise System 
Overview.

5. Redundant protocol icons may appear in the System Overview when the protocol involves 
some percepts/actions sent/received by actors.

6. Double clicking the protocol graph cell on system overview sometimes brings 2 
Protocol Editing Dialog.

7. To remove data/belief icon, which connected with an event/message, from Agent/Capability 
diagram might cause error when performing cross checking.

8. Because the posted event feature allows the connection between belief/data and 
event/message, the cross checking function need to be modified to adjust this change.

9. Cross checking brings some notice about agent-pair or capability-pair which is only for
software testing use.

10. Remove a message from model by clicking 'Delete' button on descriptor panel, the 
corresponding posted events are not cleaned from data entities in model.

11. Double click data icon on Data Coupling Diagram, the data editing dialog does not 
show up.

12. Comment out the '#posted event' statements within the protected block in the .bel 
JACK code.

13. After code generation, if users add folders/files under the code directory, when
regenerating code, some exception may occur.

14. When regenerating code, PDT may delete the JACK files of some valid entities.

15. To delete the external data icon with X button may make the System/Agent/Capability 
unaccessible.

16. If some entity removed from model, when first time regenerating code, some valid lines
in existing JACK files will be commented out.

17. If users rename an entity and regenerate the code, the old JACK file remains
and a new file	is created for the renamed entity. But the user	added code
has to be copied to new file	manually.