Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP9 displays only a portion of the report
Message
From
23/02/2014 15:23:37
 
 
To
23/02/2014 00:53:02
Lutz Scheffler
Lutz Scheffler Software Ingenieurbüro
Dresden, Germany
General information
Forum:
Visual FoxPro
Category:
Reports & Report designer
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows 8
Network:
Windows 2008 Server
Database:
Visual FoxPro
Application:
Web
Miscellaneous
Thread ID:
01594739
Message ID:
01595014
Views:
128
This message has been marked as the solution to the initial question of the thread.
Hi Lutz,

Compatibility mode for W7 didn't solve the issues, but for XPsp3 indeed did. However, in XP compatibility mode my 'net use' drive letters were no longer seen by vfp!

Then I saw another checkbox on the Properties sheet. I don't know the English wording, so I attach a picture that shows you the location. It will be something like 'Disable Modify Screen in case of high DPI-settings'. Checking this box had a good effect. There no longer was a need to choose a compatibility mode. I even could go back to my combination of resolution 2048x1152 and 150%. Now it's a matter of personal preferences.

Thank you for your input!

>Peter
>thank you for the information
>
>this need to checked - until I find time ...
>
>
>To the ghost recangle. I have seen this. It can be removed if VFP runs in the compatibility mode. (Hope that is the right word, The Win 8.1 comp is in the hand of the kids for the moment and I can not remember the right naming in german ...) Be carefull with this, if you choose wrong all windows of vfp may be moved outside _SCREEN. (Properties, command etc)
>
>
>>Okay, here are the resultls of my research.
>>
>>Both this partial report display and the other issue I reported (Dragging causes a ghost rectange, Message#1592055) are related to the setting of the screen resolution. Rightclick on the desktop and choose 'Screen Resolution'. In my case it was set to 2048x1152. Moreover, I had chosen for enlargement of all items to 150 percent.
>>When I set these to 1600x900 and 125 percent (normal), the issues are gone.
>>
>>I think there is some related code in (see Reportpreview project) frxpreviewform.init(). The following piece of code gave 96 (screen dpi) as the result. Now the result is 120. Probably that code needs a revision for the repair of the report issue. The other issue is typically vfp. A repair via any vfpx project is unlikely.
>>
#define LOGPIXELSX 88
>>
>>declare integer GetDeviceCaps in WIN32API integer HDC, integer item
>>declare integer GetDC         in WIN32API integer hWnd
>>*declare integer DeleteDC      in WIN32API integer HDC
>>declare integer ReleaseDC     in WIN32API integer hWnd, integer HDC
>>
>>local hdc, screenDPI
>>hdc    = GetDC(0)
>>THIS.screenDPI = GetDeviceCaps( m.hdc, LOGPIXELSX )
>>ReleaseDC( 0, m.hdc )
Groet,
Peter de Valença

Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform