Is there a way to slipstream a custom message back to the Modeler Messages view?

[hangtime79]

Good day @wujiazhong

I'm currently working on an extension and I would like to raise a custom error in the stop(). The example here is checking if an end date predates a start date. When I do so, I can see the custom stop output printed in the Console Output of the dialog box and the edit I did to the ibmspsscfr.properties file.

but in Modeler messages, the error is returned like the following:

Looking at the error and the properties file it appears that a 1012 error is raised, which brings me to my question.

Is it possible to raise this custom error and slipstream it into the Modeler message Output, which a user would be much more likely to see then looking in the Console Output? Looking at the Console Output, you can see that I I was able to print out an error, I also updated the .properties file with a custom message "Bad Cop, No Donut" when this error was raised. However, it does not appear that Modeler is reading this value. It is either getting that message from another source or its baked into Modeler. Do we know where the origin of that message in Modeler (image 2) lies?

[wujiazhong]

@mikezhangGit

[hangtime79]

@mikezhangGit any news here? Is it possible to change the error raised in SPSS Modeler messages?

[Wenpei]

@hangtime79
SPSS Modeler didn't support error raise for R extension currently.

It's a poor design, but I don't think modeler has plan to enhance it.
Why not move to python extension?