Events Filter+ v1.0.9 does not list Custom Type events

[emyoulation]

I was creating an example of using SuperTool to update Event custom types and wanted to use a filtered view for the script.
But the "Type" pull-down menu did not list any Custom types. (The Filter gramplet did list the Custom Types)

So with Filter+ 1.09 and SuperTool installed, I opened the example.gramps
In Events, add the Filter+ gramplet (as the first gramplet, leaving the Filter gramplet as the 2nd sidebar tab)
Add an Event of new custom Type "Communique" with Description "DD Form 214, also known as the Certificate of Release or Discharge from Active Duty"

Try to select "Communique" as a Type in Filter+
  fails because there is no "Custom" submenu.

Try to select "Communique" as a Type using the built-in Filter gramplet
  works because there is a "Custom" submenu with a "Communique" selection.

[kkujansuu]

Hmm. In my quick test both the regular Filter gramplet and Filter+ behave the same way: both update the custom type combobox only after removing and re-adding the gramplet in the sidebar.

[emyoulation]

I tried changing loaded trees , and then even shut down and restarted Gramps without the custom event type being listed.

Thanks for checking so quickly. Glad to have the Finnish Discourse section finally active too.

[kkujansuu]

Looks like a possible bug or two:

1. If a new custom type is created while the event view is active (and the Filter gramplet loaded) then the event type list in the gramplet is not updated.

2. If the setting "Remember last view displayed" is used AND the last view is the Event view then the gramplet does not add the custom types to the type list when Gramps is started. This is because the gramplet is initialized before the database is opened!

Both the regular Filter gramplet and Filter+ behave the same way (as they should since Filter+ is just an extension of Filter and does not modify the Event filter). Did you really see them behaving differently?

[emyoulation]

On the other hand, this Fedora box HAS been misbehaving. So this might be a red herring.

I think it is overdue for a re-format and re-install. (Since I have never done that with a Linux box ... and the factory install was Windows, I am hesitant to do a re-install.)