OK, I think it's fixed now. I've uploaded the current build of the
FBDK to fbdk_drop.zip in the Files section of this forum. You should
unzip it in a new folder, away from your existing code. Try out
TEST_ADP_SYS.sys in the src/test folder (the classes are already
compiled in the lib/test folder). You can also try out the
TEST_ADP_PLG.fbt and TEST_ADP_SKT.fbt types. Adapter documentation in
the "How To" help has also been updated.
The new runtime framework probably won't work with any types you have
compiled before, so you will have to re-generate and re-compile them.
Also, since I am right in the middle of code audit and JUnit testing,
there's no guarantee that all the bugs are out. In fact I can pretty
well guarantee that there are plenty of new bugs brought about by the
refactoring of the editor and runtime frameworks. But, at least the
adapters should work right!
Anyway, let me know of any new bugs you find and I will incorporate
them in my test plan.
Best regards,
Jim C
On May 2, 5:26 pm, Cheng Pang <
cpan...@aucklanduni.ac.nz> wrote:
> Hi Jim:
> Thanks for your reply. Running FB with AIs in a stand-alone tester frame is not the issue. The issue for me is that in a system configuration I try to connect FBs with AIs and basic data I/Os as shown below:
> I used the same AIBug composite FB and it compiled successfully, when I connected the basic data I/Os to some constants the system configuration can be run. However, when I connected them in the above way FBDK complaints that there is no such F.QO object. All the basic data I/Os are not used inside the composite FB at all and if I remove the AIs the system configuration runs agains, therefore I suspect there is some issue about AI in such usage.Any idea or advice will be appreciated.
> Thanks in advanced.
> Regards,
> Cheng
> James Christensen wrote:The simple answer is: You can't run an FB with adapter inputs (sockets) or outputs (plugs) in a stand-alone tester frame, because there's no corresponding single, general-purpose GUI element that can be connected to adapter I/O. This confuses the Tester. I can get the same kind of error by adding a QI input to the TEST_ADP_SKT block in the "doc" folder. Just delete the plug and socket I/O on AIBug, recompile and restart, and you will see that the Tester starts up OK. The next version of the FBDK will disallow running such FBs in the Tester, just like it disallows testing adapters this way. - Jim C.
>
> moz-screenshot-8.jpg
> 11KViewDownload