Reply to thread

Message

<blockquote data-quote="OrionHall" data-source="post: 298921" data-attributes="member: 56502">Hi Jamie,Thanks for the tips <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Unfortunately - still no joy.&nbsp; I've done a fair bit of reading and testing, but there doesn't appear to be a way to do this without a huge amount of changes.&nbsp; I think this is partly because I'm using the .Net cheap-and-cheerful multithreading in the form of the BackgroundWorker class.&nbsp; It's crude but effective, and a lot easier than manually creating and manipulating threads.&nbsp; Since the main app runs in the main thread, and the updating process is on a separate thread, the two forms can't see or talk to each other at all.&nbsp; The Microsoft line is that the only way to communicate back to the main thread is through the backgroundworker_OnProgressChanged event.&nbsp; And that's one-way - I can't detect a click on the main form and force the Internet lookup form to the front.&nbsp; I suppose the only cheating way to do it would be to have the Internet lookup form constantly bring itself to the top of the z-order on a timer; but that really is a bit messy and could be annoying when doing other stuff at the same time.Cheers,Orion.p.s. You're welcome for the log window fix - I'm just chuffed to have finally got that working!&nbsp; Every other 'fix' I tried ended up making the two forms flicker madly, particularly when moved!Hi arryo,Glad it's working for you now!The year field is pulled from the Internet lookup - can you confirm which Internet lookup parser file you're using?&nbsp; Actually, please just attach it to your reply as there have been various version of the lookup scripts.&nbsp; The Year field works for me with the latest IMDB script but I haven't tested much with the others.I've also found some entries with those squares - they represent non-printable characters or characters not included in the current font.&nbsp; As before, it'll help to know what script you're using - it should be fairly easy to tweak things to tidy up that kind of thing.Cheerio,Orion.</blockquote>

[QUOTE="OrionHall, post: 298921, member: 56502"] Hi Jamie, Thanks for the tips :) Unfortunately - still no joy. I've done a fair bit of reading and testing, but there doesn't appear to be a way to do this without a huge amount of changes. I think this is partly because I'm using the .Net cheap-and-cheerful multithreading in the form of the BackgroundWorker class. It's crude but effective, and a lot easier than manually creating and manipulating threads. Since the main app runs in the main thread, and the updating process is on a separate thread, the two forms can't see or talk to each other at all. The Microsoft line is that the only way to communicate back to the main thread is through the backgroundworker_OnProgressChanged event. And that's one-way - I can't detect a click on the main form and force the Internet lookup form to the front. I suppose the only cheating way to do it would be to have the Internet lookup form constantly bring itself to the top of the z-order on a timer; but that really is a bit messy and could be annoying when doing other stuff at the same time. Cheers, Orion. p.s. You're welcome for the log window fix - I'm just chuffed to have finally got that working! Every other 'fix' I tried ended up making the two forms flicker madly, particularly when moved! Hi arryo, Glad it's working for you now! The year field is pulled from the Internet lookup - can you confirm which Internet lookup parser file you're using? Actually, please just attach it to your reply as there have been various version of the lookup scripts. The Year field works for me with the latest IMDB script but I haven't tested much with the others. I've also found some entries with those squares - they represent non-printable characters or characters not included in the current font. As before, it'll help to know what script you're using - it should be fairly easy to tweak things to tidy up that kind of thing. Cheerio, Orion. [/QUOTE]

Verification