2018-02-17 19:03 EST


View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0002268wxFREDpublic2010-11-22 05:11
Reporterrodo 
Assigned ToFSO 4 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionopen 
Summary0002268: Moving Events around causes conditionals to loose Event's name.
DescriptionIf you have an Event name used in a conditional sexp (like is-event-true), if that same Event is moved from it's original position in the Events Editor, when trying to save the mission, Fred will warn of an invalid argument, this invalid argument will be the name of the Event that has been moved.
Additional InformationTo test this:

Just open the mission, check that it's possible to save it before doing anything, this way you know everything is all right in the mission.

Then after testing that, just go to the Event Editor and move the Event named "Event 1" from the top of the list to the bottom.

Close the Event Editor and try to save the mission.
You should get a warning.

That's it.
TagsNo tags attached.
Attached Files
  • ? file icon test.fs2 (6,591 bytes) 2010-07-21 21:32

-Relationships
related to 0001961closedFSO 4 FSSCP Reordering events can cause is-event-true and possibly other sexps to reference wrong event. 
+Relationships

-Notes

~0012473

rodo (reporter)

Dammit, I loaded this in wxfred and that's not correct, I tested this on a windows system.

~0012482

Goober5000 (administrator)

This is one of the many vagaries with FRED's event system, something that is targeted to be fixed in wxFRED.
+Notes

-Issue History
Date Modified Username Field Change
2010-07-21 21:32 rodo New Issue
2010-07-21 21:32 rodo File Added: test.fs2
2010-11-18 12:23 rodo Note Added: 0012473
2010-11-22 05:09 Goober5000 Relationship added related to 0001961
2010-11-22 05:11 Goober5000 Note Added: 0012482
2010-11-22 05:11 Goober5000 Assigned To => FSO 4
2010-11-22 05:11 Goober5000 Status new => closed
2010-11-22 05:11 Goober5000 Additional Information Updated
+Issue History