bb.donnay-software.com

We have just updated to Build 255 and we're using that now with Xbase++ 1.9 SL1.

The first problem that I have noticed is that a number of dialogs in our system do not show the full dialog width. Instead they are a number of pixels smaller in width than they used to be using Build 254.

This shows up by objects being cutoff on the right hand side of the dialog where they were shown fully before.

The dialogs that this appears to affect are ones that we use the DCGETOPTIONS...FITPAD clause on (along with DCREAD GUI FIT obviously).

Having done a few tests it appears that a FITPAD of 6 makes the right dialog border touch the right-most objects right-hand side and anything less than 6 causes the dialog to be made less wide than it should be.

I remember seeing a few messages recently mentioning problems with the FITPAD clause but the ones I looked at don't look as if they are the same problem.

Can anyone else see this? Has there already been a fix mentioned that I possibly missed?

Regan

Are you using Windows 7?

rdonnay wrote:Are you using Windows 7?

Yes...I have been using it for a couple of months with Xbase++ 1.9 SL1 and Express++ 1.9 build 253 or 254 before updationg Express++.

I realised that this is undoubtably an issue related to Win7 as I know that the dialog border and title bar sizing changed. But as far as I can see, this must be as the result of a calculation somewhere that does something different in the updated version.

Steve has asked me if, for the meantime, we can change the FITPADs on these dialogs to something that does not cause a problem and, of course, I can do that. The downside is that a few of these screens do the FITPAD as they contain large coloured statics that act as the backgrounds to varous objects and keeping the FITPAD 0 removes the uncoloured (well, system default dialog coloured..) border which just makes them look cleaner and maximises dialog space. But I might do that for the meantime.

Steve -

If you can be patient for about 2 weeks, I'm waiting for my new Dell laptop to ship (around June 21).
It is installed with Win 7 pro. Currently, I only have Win XP.

I believe there is an issue with Win 7 which I may have already fixed in build 255, but I'm not sure.
Give me a small sample program showing the problem. Maybe I already have a fix for you.

Roger

rdonnay wrote:Steve -

If you can be patient for about 2 weeks, I'm waiting for my new Dell laptop to ship (around June 21).
It is installed with Win 7 pro. Currently, I only have Win XP.

I believe there is an issue with Win 7 which I may have already fixed in build 255, but I'm not sure.
Give me a small sample program showing the problem. Maybe I already have a fix for you.

Roger

We can be patient...As I said we have a workaround for the moment. I am thinking of wrapping the FITPAD value in a function that just returns 10 at present or something so it can easily be reinstated or found later.

I attach a quick knock-up sample in it (hopefully) showing the problem.