Tracker - Clarion Support wrote:I'm working on a subclassing solution to the problem, which should eliminate these problems once and for all.

Craig,

Any progress?

--David

My current app is different than the one emailed, but behaves the same. The only DISPLAY() occurs during the OpenWindow event and is unrelated to the pdf viewer. The viewer is on a tab and its code only gets invoked if the user goes to that tab and clicks a button. The example app has a DISPLAY() at...

I believe there might be a couple of DISPLAY()'s in the example app that I'm not doing. Also in following along in what the example app is doing, it looks like it hits the SetCurrentPage method twice in a row. Once when leaving a routine and when entering the next routine called...doubt that matters...

Cycling the accept loop between opening the pdf and doing the display stuff (like the example app happens to do) did not have an effect.

It's kind of like the PDFXCV14.SetFitTo(PXCV_FIT_BEST) isn't working as expected in one of the dimensions.

--David

Craig, Did you come across anything in the code I sent? I tried adding the stripped down viewer to another app and ended up with a similar problem. The region gets resized, but in this case it was wide enough to where I could see part of the pdf. I'm assuming the same thing is happening in both apps...

I'm just trying to display the first page of a pdf on a window without any of the additional functionality shown in the example program (which works fine.) I'm seeing my pdf unloaded from a blob (can open it in Win Explorer OK), but the region on the window is always white and resized oddly. In the ...