Wilhelm Sanke wrote:
What irritates me is that they speak of a necessary change to the
*engine*, which kind of engine is involved her? What does "(ide) engine"
mean, which - according to the engine-change log - will implement the
standalone building in dp4 and in the future. If this engine is
identical to the Revolution engine, then we - as MC-IDE users - could
possibly get problems? How must standalone building with the new
"engine" be configured to work in the MC IDE?
In the attachment of Comment 11 to bug report # 2217 you find a patched
Rev stack for standalone building to be used with the command (in
Comment 10)
For lazy people like myself, the link to that report is:
<http://quality.runrev.com/qacenter/show_bug.cgi?id=2217>
The full sentence in which RunRev's Oliver Kenyon suggested the need for
an engine change is worth noting:
To fix the issue, we will need to make an engine change, possibly
the addition of a "repeat for each control" loop form.
So rather than something irritating, it's actually quite cool: imagine
if we had the ease of iterating through controls so simply. Nice stuff
- glad to see they're thinking along those lines.
--
Richard Gaskin
Fourth World
Rev training and consulting: http://www.fourthworld.com
Webzine for Rev developers: http://www.revjournal.com
revJournal blog: http://revjournal.com/blog.irv
_______________________________________________
metacard mailing list
[email protected]
http://lists.runrev.com/mailman/listinfo/metacard
