Hi all,

i've written some custom reader that parses some binary files in our own format. This works very well except one point.
We need some configuration here as each version of the binary file has some sort of schema file that needs to be read in order to parse the binary file correctly. Now unfortunately each developer stores the schema files in different locations and we have to make it configurable but therefore the current option with a text box and the arguments in the Initialize method is not sufficient as we have a lot of versions and to maintain these versions in the text box is a mess.
I would really appreciate to have an extra Interface or an extension to the ILogReader interface that provides a custom configuration dialog.
Maybe some extension like an enum ConfigSetting.Simple and ConfigSetting.Custom in the ILogReader interface and dependent on that you show the simple text box or a "configure"-button.  If we press the configure button everything is under the control of the plugin. Including Storing/Restoring the configuration options. If the simple settings is used it's handled as today by logviewplus.
Would something like this be possible?

This looks good for a filter and is what I had in mind.
Unfortunately it seems that this doesn't work for a custom reader that implements the ILogReader interface.
If I understand you right it's only implemented for the ILogFilter and ILogParser interace, isn't it?

Would be good to have it - as this thread subject implies - also on the ILogReader interface

Apologies for the oversight.  I can confirm that this is not yet implemented on the ILogReader interface.  This is an easy fix for us and I should be able to push out a fix tomorrow.

Thanks, 

Toby

We have just released LogViewPlus v2.3.9 which adds custom configuration support for ILogReader implementations.

We have also updated the code samples to demonstrate the new API.  Sample code is available here:
https://www.logviewplus.com/dist/LogViewPlus_Samples.zip

Please let me know if you have any further questions or issues  

Thanks,  

Toby

Sorry for the delay.
It's working with the 2.3.9 version and looks good.
The only thing that immediately comes into my mind is that the skin is not applied to the configuration dialog but that's more a cosmetic thing.
The functionality is there and is working.
Thanks a lot

Thanks for the update.  Glad to hear the new API is working for you.

Skinning is going to be a tricky problem to solve without complicating the API, but I am open to suggestions.  For example, we could pass you a boolean value to indicate if the skin is light or dark.

Thanks again,

Toby