After reformatting my hard drive and reinstalling everything, the issue seems to be resolved. So it may have been a funky PDF-XChange Editor install/update that caused it.

Thanks, Daniel. I followed your procedure and reinstalled. No joy. For this and other reasons, pretty soon I'm going to reinstall Windows and all my apps. I hope at least that will fix it.

I see. My workaround only works with local files, which is less often what I use. This problem appears multiple times a day. So what will have been changed in 334? I don't think the browser is setting up the window either. But it looks like PDFXE is using a different set of stored coordinates or a d...

I've waited another three weeks with no response from you. :( As a workaround, I'm writing a batch file that overwrites registry entries to set window positions. I know the relevant registry keys that set window positions for local PDF files. What are the keys to set the window position for files op...

Okay, thanks. Again, if you want me to run a debugging version or something, let me know.

Have you reproduced the issue? What are next steps?

Oh, okay.

I've attached the Editor's compatibility settings (I think these are all default settings) and some display settings. If you had different display settings in mind, let me know which.

Thanks for following through with this frustrating issue.

It looks like it's not Windows. I still have the "Use this setting..." box unchecked, and the window resizing happened again. I've attached a log of registry accesses made by Editor (I've never seen any other app change these keys). Note how on line 26, as I close Editor, i.right is set to...

Hi Daniel, Maybe we're getting somewhere. I found the relevant registry key (HKEY_CURRENT_USER\Software\Tracker Software\PDFXEditor\3.0\Settings\MainFrm\Rect) and set up Process Monitor to monitor accesses to that key. My laptop has a 4K screen. A while back, because PDF-XChange Editor wasn't handli...

After months of waiting, yesterday I upgraded to 332.0 with high hopes, set up my panes, and was happy to see that they stayed in place through several cycles of opening and closing the app. Until they didn't. The panes have changed their positions several times. :-( And sometimes they do stay in pl...

Yes, in a previous post, I mentioned closing Updater, then exiting it, so I'm aware those are distinct steps. (A bit of a nuisance too—why would I want Updater to stay open, using up resources, when I know there aren't any updates?) I have to exit the app entirely, and maybe even reboot, for the old...

I invoked Update, and it moved and resized its window again. I looked at the MainWnd registry entries, and they looked like what they were when I had closed Update the last time. So it seems as though Update just didn't use those entries when it set up its window. I resized and moved the window agai...

Hi Daniel, My web host implements spam filtering, and it works very well. I wasn't able to find any emails from *tracker* (those are wildcards) in the incoming logs, spam filtered or not. Nonetheless, I've added a whitelist entry for *.tracker-software.com. I don't use a registry cleaner, and I don'...

It happened again. I rebooted my computer since yesterday and just now in Editor, I went to Help > Check for Updates, and the update app window is large and centered on my screen. Yesterday when I closed it, it was small and in the lower-right corner.

Hi Daniel, Well, of course it's not doing it now, but I know that in the past several days, the update window was appearing in different places on my screen and in different sizes. I'll see if I can get it to do it again and let you know if I can document the process. Meantime, can you figure out wh...

Two things:

The Tracker Update window also doesn't remember its position and size. Will you guys please fix that while you're at it?

About when do you expect the next Editor update to be released?

Thanks again!

That's terrific news, Daniel! Thank you for persisting. I look forward to the new version.

Yes, "restore last used..." is enabled.

Exported setting attached.

Thanks.

Hmm, two steps forward, two steps back. I reset the settings. The stamps palette then seemed to reopen. It shifted itself a little from where I left it, but it seems consistent in reopening there. BTW, I use a set of custom stamps. Then I clicked on a stamp, then the PDF, then I undid stamping the P...

Well, this is the problem with assumptions. :-S I need the stamps palette when I proofread professionally, but I often look at PDFs that I'm not going to proofread, so of course I don't touch the stamps palette in those cases. It's a mistake for a software vendor to assume it knows how its users wan...

Hi Daniel, I would have responded sooner, but I didn't get notice of your reply. Actually, what I'm experiencing is exactly what this thread is about. I just now tested opening a document, clicking on a stamp in the stamps palette, then closing the app. If I did all those steps, the editor and stamp...

This issue has gotten worse. It used to be that only the stamps palette window would open to some random size and position. Now the main window is doing the same, so I have to laboriously resize and reposition both windows when I open the app. I like the app, but this bug has become a real PITA and ...

I'm using 328.2 and having two problems with the spell checker: 1. When I click the "Ignore All" button, that word is added to the custom word list. I would only expect this to happen if I clicked the "Add" button. 2. The spell check wastes a lot of time stopping on hyphenated wo...

I'm experiencing this same issue, but with the Stamps palette. It used to work perfectly, now it sometimes doesn't get restored when I open a file. It's restored when I import settings.

Will the upcoming fix apply to the Stamps palette too?

Thanks.

Please alphabetize the stamps regardless of the order they were entered.

I use dozens of stamps to proofread with, add new ones once in a while, and need to find them in the palette quickly. So I've been holding off using PDF-XChange Editor until this issue is resolved.

Thanks for addressing this.