mappView Compiler Error 7390

Hi there,

while working on the project Performance Analyzer, I needed to adapt the two widgets “TextInput” and “NumericInput” via the Development Kit, which allows you to bind the “keyboard” parameter at runtime.

The two new widgets work in all content, except for one content called fhdRegister.
There, switching to the adapted widget triggers three errors that I cannot explain:

I suspect that there is a problem related to the CompoundWidget, which is also used on this content.

Can you help us with this problem?

The project is processed with AS6.1.1.14.

Best Regards
Jörg Grimmler

Hello @Joerg ,
Please could you minimize the searching area by commenting part of this code?
Just to simplify/confirm if your suspicion regarding the Compound widget is correct or not.
Thank you.

Hello @patrik.simcik ,

the error also comes up when reducing the content to only one TextInput and two of the CompoundWidgets:

It really seems to be due to the combination of the new TextInputExt Widget and the CompoundWidget.

maybe the path is too long? could you modify/change it?

@patrik.simcik here is another piece of information since I looked at this for Joerg last week

If you add the new TextInput widget to the mappView package so it shows up in the toolbar you can’t drag & drop this widget into content. Almost as if the system knows something is missing for the widget / from this package.

It’s also not the path length, we tested that already.

Hi guys,

As @marcel.voigt illustrate if you can’t drag and drop the widget it’s because there is a missing thing in the widget. I’ve already see this, but I can’t remember what it was.
Is it possible to have the library to test it ? And have a look ? (if you have a test project with just the mappView error that would be nice :slight_smile: )
Also is it AS6 ?

Regards,
Florent

1 Like

One thing, in the TextInput brease widget, it depend on alot of file in the brease/common folder.
You cannot import this files from another widget lib, you need to copy and edit them to include them in your widget library.

Hi Florent,
attached you can find an AS6.1 minimum project bringing the error while compiling.
PAError.zip (8.1 MB)

2 Likes

I have identify that eventbinding of the compound widget seems to be the problem, when you comment them, the compilation is done without error. I will investigate a bit more why eventbinding are the problem.

3 Likes

I use this thread as notepad :sweat_smile:

Command line that trigger the error message :
"C:\Program Files (x86)\BRAutomation\AS6\AS\TechnologyPackages\mappView\6.2.0\bin\BR.IAT.Builder.exe" -be "ContentWidgetBuilder" -infrastructure "C:\projects\PAError\Temp\Objects\Config1\PC\.mappView\mappViewBuildInfrastructure.bin" -markerFile "C:\projects\PAError\Temp\Objects\Config1\PC\.mappView\Comp_EB_Trans._markerfile" -cultureName "fr-FR" -uiCultureName "en-US"

“Directory.GetDirectories” throw an exception when trying combine library name and widget name to retrieve path in the project

Ok so I think there is a problem with MappView compilation, compiler try to access a folder that didn’t exist.

If B&R guys see that :

  • An exception DirectoryNotFoundException is throw in the class CompoundWidgetEventBindingGenerator in the function GetWidgetDirectory (in BR.IAT.Builder.Content.Widget).

  • There is something like CustomWidget is detected as a CompoundWidget or the compilation of the CustomWidget library should be complete before calling the this part of the program (missing dependency ?)

So the error message is right, he search the custom widget folder in “C:\projects\PAError\Temp\mappView\Widgets” and it do not exist.

I think this problem will need a B&R Support ticket. I will try to just reproduce a more lite project to test if it’s the fact to have CustomWidget library and CompoundWidget library in same application. And use 1 widget of both library on the same content.

I keep you in touch here, if needed I can contact my local B&R office.

@florent.boissadier thanks for digging into this but no need to run this through your B&R office we ( @Joerg or I ) will take care of this internally :wink:

1 Like

Ok no problem, I identify what generate the message but not the root cause.
Hope that could help

2 Likes

If you need more details, feel free to ask.

1 Like

Hello Florent,
thanks a lot for your help.
We now have new approaches to further troubleshoot the error.

1 Like

@Joerg, please keep us updated about possible solution :slight_smile:

The issue is being looked at but seems to be an internal compiler error. I’ll update this thread when I hear something new to share.

2 Likes