archi-contribs / specialization-plugin

Plugin for Archi to specialize concepts (figure, icon...)
Other
29 stars 2 forks source link

Error message when adding a (new or existing) application component to a view #44

Closed mikisvandijk closed 3 years ago

mikisvandijk commented 3 years ago

I use the specialisation plugin to show a name and a company-defined applicatio-number in the application component. Bij setting the label expression "to ${name}\n${property:SW}"

Everytime I add a component to a view, I get an error message "An error has occurred. See error log for more details. org.archicontribs.specialization.uiProvider.elements.figures.ApplicationComponentFigure.setText()V"

It seems a warning, after acknowledging the message, everything seems working fine.

What information can I provide you to have a look at the issue?

herve91 commented 3 years ago

Hi,

You need to activate the plugin log file in trace mode through the preference page: image

then you need to reproduce the error and provide me with the part of the log file that contains the Exception (and a few lines before, let say a 10ish, that I can understand what the plugin was doing when the exception happend.

Alternatively, you may use the new label functionality that is natively provided by Archi since version 4.7 as the developers included this part directly in their code: image

Best regards Hervé

rich-biker commented 3 years ago

This has gone quiet. I'm also having this problem, Hervé, so I'll provide some more info. Of course, we could use the new labels feature, but I like to be able to replace icons on shapes when I specialise.

Plugin: /Applications/Archi.app/Contents/Eclipse/plugins/org.archicontribs.specialization_v1.0.11.jar Archi version: 4.8.0 Build 202012140831 (although it's been happening before this). Mac OS: Big Sur

Message: An error has occurred. See error log for more details. 'void org.archicontribs.specialization.uiProvider.elements.figures.ProcessFigure.setText()'

Here's the snippet of trace log file

SpecializationPlugin_7Jan_Trace.log

herve91 commented 3 years ago

Hi,

Unfortunately, the log file you provided does not contain any error message, but it should have one (as per the message you've had on your screen).

I do not have any MacOS at the moment so I cannot reproduce your environment and do not have the same error on Windows.

I'll try to do more testing and in the meantime, please reproduce the error and check if there is an error message printed in the log file.

rich-biker commented 3 years ago

There wasn't an error anywhere in the log, so don't worry. I've just realised that the 1.0.12.archiplugin was available and should be used - I was using an older 1.0.11.jar version.

This paved the way: https://github.com/archi-contribs/specialization-plugin/issues/50#issuecomment-756271794

Your latest code is just fine. I think you should close this.

herve91 commented 3 years ago

The lastest version of the plugin has effectively been recompiled against the latest version of Archi because the libraries were not aligned anymore.

So I close your this case.

Best regards

mikisvandijk commented 3 years ago

Excuse me that I didn't react sooner.

But using the recompiled version of the plugin seems to solve the problem for me as well.

Thanks and kind regards

herve91 commented 3 years ago

Great, happy to learn your issue is solved as well

Best regards