Found it - the reason why the engine had not registered the new status of the created objects is the following lines of code:
send "delete viewToReplace" to viewToReplace in 2 ticks # in order to
self delete if required.
The engine must be waiting until the delete occurs before updating its records - even though a subsequent "copy" has already created the new objects. Changeing the line to: delete viewToReplace
Fixes everything - phew! I am not sure if this is a bug or something that should be put up with and put in the docs - but its filed: http://quality.runrev.com/qacenter/show_bug.cgi?id=5038 _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
