blank fit page when selecting old style plugin after reload

[pkienzle]

The following error occurs when loading an old style model after the "Load Plugin Models" operation (either from the menu, or from editing and saving a model):

Traceback (most recent call last):
  File "/Users/pkienzle/Source/sasview-new/src/sas/sasgui/perspectives/fitting/fitpage.py", line 1179, in _on_select_model
    self._on_select_model_helper()
  File "/Users/pkienzle/Source/sasview-new/src/sas/sasgui/perspectives/fitting/basepage.py", line 2045, in _on_select_model_helper
    self.model = form_factor()
  File "/Users/pkienzle/.sasview/plugin_models/polynomial5.py", line 39, in __init__
    Model1DPlugin.__init__(self, name=self.name) ##DO NOT CHANGE THIS LINE!!!
TypeError: expected string or buffer

This gives a blank FitPage.

The workaround is to request a new fit page, which then makes the old page accessible.

[butler]

I am unable to reproduce. Am using ticket-756 branch at commit 11b094f7ba887a4289c62ca48cf7509991c9fbc2 and sasmodels master at commit
9ed53e739d23bb72709ce13077bfdd3c8c34e58a
under windows 10 with OPEN CL available.

Also downloaded latest ESS build for windows (#640 build on Feb 14, 2017 from SasView master at commit 2510b9b9dd6b1865d897555b1fd71086a65f89d7 and the same sasmodels commit as above) on old windows 10 machine without OpenCL and all worked fine … though of course the very old style which imported from sans.xxxx still don't work till the line(s) are replaced with sas.xxxx but that has been true for a long time.

Will verify with reporter before closing ticket.

[pkienzle]

Still fails on master, but doesn't fail on ticket-756 branch. Close after ticket-756 is merged.

[butler]

Correction to my previous comment. Branch ticket-756 works while the ESS build fails but in a different way for me than reported: the page freezes. It looks fine until one tries to click on the page or change a parameter. This is no doubt just a different manifestation of the same problem on different machines:

Indeed the problem is in fact part of ticket #756 which was only half done. Category had been changed from "Customized Model" to "Plugin Model" but all the strings related to category manager were not. In several places there is a branch point of: if category is built-in then use the category manager managed lists and dictionaries, but if "custom" or "user" or now "plugin" then those lists do not know about it as they are dynamically changing. Unfortunately we now have a situation where category is "Plugin Model" but the check is against a string that is "Customized Model" since the compare is false it goes to the categary manager lists which of course know nothing about the model.

[butler]

Since this is really just a manifestation of ticket 756 I am closing as duplicate but am going to make a comment on that ticket to do extreme testing of that window when done and in particular check for the issue reported here.