Reply to thread

Message: <blockquote data-quote="GJC" data-source="post: 884166" data-attributes="member: 120757">Hi Valdi, Thanks for the wonderful feedback! I've been checking the forum every day wondering if the plug-in installed ok and how it was working out. As a developer you can get into a certain way of doing things and can sometimes miss the obvious. I'm surprised that you'd get a firewall warning when trying to import settings, but thankfully that's not a problem. Did I leave that HID device stuff in there? Oops! Yes, it's ok to remove it. I have it in there to get my remote to work properly with MP. I mentioned in the documentation (and in the script file) that you'll see an exception in the EventGhost log each time you rotate the antenna. The problem is that the timer function in the wx library needs to be run on the main application thread. If you don't, then a warning exception is logged. EventGhost doesn't run the python code on the main application thread, so I couldn't see anything I could do in a "timely" (pardon the pun) fashion. It also didn't seem worth much effort as the timer works anyway. I'll probably have a crack at another approach before I make an "official" release of the plug-in, but I'd be grateful if  there's an experienced Python developer out there that can help out. Regarding multiple monitors, I'm presuming that you have one PC and three monitors on it? I'd considered the possibility of 3 PCs and one TV Server. You'd have a copy of EventGhost running on each PC and then have the batch file on TV Server send the event to all 3 PCs through their respective EventGhosts. However, for a single PC and 3 monitors, the only thing I can think of would be to modify the script to display the dialog at a set of coordinates that maps to the monitor that has MP displayed. I think this could be done using the logic I have to find the MP window and then use its coordinates to determine the position of the message. Hmmm, I'll try to take a peek at that. I considered the EventGhost message dialog, but it needs to be triggered as an event and I didn't know how to close it programmatically after the rotation period. It's not necessary to enter additional azimuths for a station if there are no other stations near those azimuths. The idea is that you want "overlap" between azimuth ranges to help find a common position that will satisfy all active channels. Keep in mind, however, that you probably have several local stations that you can pick up at almost any azimuth, so you may have overlaps that you hadn't considered. Adding more azimuths will never hurt as long as you have reliable reception at those azimuths. Couch potatoes will still have to vacuum the stairs and do laundry, at least for now. We'll look into that for version 2.0. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink    ;)" loading="lazy" data-shortname=";)" />[DOUBLEPOST=1342731886][/DOUBLEPOST]BTW, thanks for posting the ChannelMaster codes. I'll incorporate them in the next release of the python script.</blockquote>

Verification