"Could not resolve method to call" messages when running check on DLL files

Hi, what might mean following type of messages when running Check on DLL files in Passolo 2022 Translator Edition:

Control Could not resolve method to callABB.PCM.Tools.ECT.ExpandableGroupBox, set_Caption

Could not resolve method to callABB.PCM.Tools.ECT.ExpandableGroupBox, set_Caption is not initialized. Base form might be unresolved.

Control Could not resolve method to callABB.PCM.Tools.ECT.ExpandableGroupBox, set_CaptionColor

Could not resolve method to callABB.PCM.Tools.ECT.ExpandableGroupBox, set_CaptionColor is not initialized. Base form might be unresolved.

Thanks

Jouni

emoji
Parents
  • Difficult to answer, and usually I would suggest logging a support case into our support portal https://gateway.sdl.com/

    But I can at least express my assumptions here. It seems to be the case that external or self-developed components are used for the GUI, as shown in the error list (e.g. callABB.PCM.Tools.ECT.ExpandableGroupBox, set_Caption).

    Furthermore, it is not entirely clear which checks are activated. When creating a bundle for external translators, these external components are by default not part of the bundle. If, for example, it is now necessary to check whether the translated text fits into the control (here ExpandableGroupBox), the control must be available as a DLL so that Passolo can create an instance and then perform the length check.

    These referenced controls can be sent once and in advance to the translator, who must then save them in the correct directory. A second option would be for Passolo to automatically pack these controls into the bundle. However, this may significantly increase the size of the bundle.

    Screenshot of Passolo .Net Parser Settings window with 'Embed Referenced Assemblies to Passolo Project' option highlighted.

    After that, the check and visualization should work much better for the translators using bundles.

    emoji


    Generated Image Alt-Text
    [edited by: RWS Community AI at 4:08 PM (GMT 0) on 17 Dec 2024]
Reply
  • Difficult to answer, and usually I would suggest logging a support case into our support portal https://gateway.sdl.com/

    But I can at least express my assumptions here. It seems to be the case that external or self-developed components are used for the GUI, as shown in the error list (e.g. callABB.PCM.Tools.ECT.ExpandableGroupBox, set_Caption).

    Furthermore, it is not entirely clear which checks are activated. When creating a bundle for external translators, these external components are by default not part of the bundle. If, for example, it is now necessary to check whether the translated text fits into the control (here ExpandableGroupBox), the control must be available as a DLL so that Passolo can create an instance and then perform the length check.

    These referenced controls can be sent once and in advance to the translator, who must then save them in the correct directory. A second option would be for Passolo to automatically pack these controls into the bundle. However, this may significantly increase the size of the bundle.

    Screenshot of Passolo .Net Parser Settings window with 'Embed Referenced Assemblies to Passolo Project' option highlighted.

    After that, the check and visualization should work much better for the translators using bundles.

    emoji


    Generated Image Alt-Text
    [edited by: RWS Community AI at 4:08 PM (GMT 0) on 17 Dec 2024]
Children