G'Day Dennis,

I am using the INSTANCE, DATA, and REPORTS directives.

For the global.instance_id="CONTESTS" I load the contest log forms using statements like Global.new_object("log_form", "logdata\logforms\_2014-10 Oceania_DX_SSB.LOGFORM"), all via a script in the UPDATES folder.

While developing my Contest Report, it became rather tedious to be always reapplying the appropriate log filter for each contest logform.

In the your Contest Report script, there is code that applies the filter to the log for reporting.


How do I select the contest logform to apply the "contest filter" to the contest logform when I load it from a script in UPDATES?



PS: Wouldn't it be nice if there was a "default filter" in a logform SETUP that was applied every time that logform was loaded. How about a list of "previous filter expressions" saved in a drop down on the logform or the filter dialogue.

G'Day,

I am talking about loading the logform when I open LOGic,

I open logic with many shortcuts that look similar to this ...

"C:\Program Files (x86)\LOGic\logic.exe" INSTANCE=CONTEST_TEST DATA=.\testdata REPORT=VK4IUReports

and in a PRG in the UPDATES folder I have some code like this that runs when LOGic loads ...

if global.instance_id="CONTEST_TEST"
  Global.new_object("log_form", "logdata\logforms\2014-11 CQ-WW-DX-Debug.logform")
        <apply filter to form here>
  Global.new_object("log_form", "logdata\logforms\2014-11 CQWWCW.logform")  
        <apply filter to form here>
endif

I want to apply a filter immediately after any logform load in this, or similar code.

I want to do this for "development work" - mainly developing contest forms, and testing them by making QSOs. I usually have several logforms open with different filters to see what happens as I make test QSOs, with the Browse window sorted in various ways

If I do anything that closes all the logforms, take a back up, or re-index, exit LOGic, I have to load and apply the filters all over again.

A drop down list of filters would make life easier - NONE would be the normal mode, and if any were selected it would be applied on load of the logform.

The answer was right in front of me!

Let me know if any questions.

73,

Dennis WN4AZY

G'Day Dennis,

The filter code is working correctly.

However, when I use the code, another problem has been revealed, not related to setting the filter via code.

I have tested the following without using any code - manually loading logforms and setting filters on both forms. I was also able to demonstrate the problem in a "clean skin" copy of LOGic9 under Windows XP, and in a copy of LOGic 8 under Win 7.

You should be able to see the issue by doing the following ...

Load two logforms, and set filters on each logform. Check that the browse window on each form does what the filter defines - the browse window only showing the filtered records.

Now close ONE logform. The browse window of the OTHER logfrom now no longer reflects the defined filter of its associated logform - it shows ALL records in the log, despite the logform filter.

This may be related to another issue I reported some time ago. Attached is a small video of that previously reported issue.