Hi, Roger.
Some suggestions for build 257:
1. The method "MoveColumn" of DC_XbpBrowse should also store and restore the drawmodes (heading, dataarea, footing), the settings for "usevisualstyle" for all cellgroups and the cargo (!) of the columns. Otherwise, moving columns in an ownerdrawn browse (and/or using visual styles) creates crap, since those settings get lost with AddColumn().
2. DCSAY/DCSTATIC TEXT still creates a clipped area (4 pixel) around the presentation space if ownerdrawing is used with this. This comes from the "FORMATTED" option, which mixes up this formatting and ownerdrawing without "FORMATTED".
3. DCGET OPTIONS ... BUTTONS: The accelerator key (element 11) and the tooltip (element 9) don't work. Having the option to create a menu block for the buttons there would be just wonderful (element 12? ).
Build 256
Re: Build 256
Tom -
Thank you for those reminders.
I am in Florida this week, working with Brian Wolfsohn.
He too gave me a few reminders.
I will be working these issues next week when I am back home.
Roger
Thank you for those reminders.
I am in Florida this week, working with Brian Wolfsohn.
He too gave me a few reminders.
I will be working these issues next week when I am back home.
Roger
The eXpress train is coming - and it has more cars.
Re: Build 256
Tom -
I don't understand your #2. Are you saying that you want to use FORMATTED with ownerdrawing?
Roger
I don't understand your #2. Are you saying that you want to use FORMATTED with ownerdrawing?
Roger
The eXpress train is coming - and it has more cars.
Re: Build 256
Hi, Roger.
Look at line #742 (and following) of _DCCLASS.PRG (build 256), DC_XbpStatic:Draw(). This creates a 4 pixel clipped area around every text static that uses either the "FORMATTED" option .or. (!) self-made ownerdrawing. This may be right for "FORMATTED" statics, but it also creates a blank area around every DCSAY or DCSTATIC ... TEXT that uses ownerdrawing without "FORMATTED".
Look at line #742 (and following) of _DCCLASS.PRG (build 256), DC_XbpStatic:Draw(). This creates a 4 pixel clipped area around every text static that uses either the "FORMATTED" option .or. (!) self-made ownerdrawing. This may be right for "FORMATTED" statics, but it also creates a blank area around every DCSAY or DCSTATIC ... TEXT that uses ownerdrawing without "FORMATTED".
Best regards,
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Re: Build 256
Tom -
This DC_XbpStatic():draw() method should have been invoked only when using the FORMATTED option. Are you using the ::ownerDrawBlock to handle your own ownerdrawing or are you using a SUBCLASS? I think the problem is because you may be using a subclass.
I may need to resolve this.
I created a MSGBOXCUSTOM sample program that uses owner draw but does not have this problem because it never calls the DC_XbpStatic():draw() method. I have attached the
program. Copy it to your \exp19\samples\static folder and run it.
Roger
This DC_XbpStatic():draw() method should have been invoked only when using the FORMATTED option. Are you using the ::ownerDrawBlock to handle your own ownerdrawing or are you using a SUBCLASS? I think the problem is because you may be using a subclass.
I may need to resolve this.
I created a MSGBOXCUSTOM sample program that uses owner draw but does not have this problem because it never calls the DC_XbpStatic():draw() method. I have attached the
program. Copy it to your \exp19\samples\static folder and run it.
Roger
- Attachments
-
- msgboxcustom.zip
- (34.47 KiB) Downloaded 690 times
The eXpress train is coming - and it has more cars.
Re: Build 256
Hi, Roger.
You're right - I'm using subclasses. I created all this stuff before you came up with the ownerdraw-codeblock.
You're right - I'm using subclasses. I created all this stuff before you came up with the ownerdraw-codeblock.
Best regards,
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Re: Build 256
I edited my message. Look at MSGBOXCUSTOM and how I implemented owner drawing.
I think I will remove the GraBox. I forget why it's in there.
I think I will remove the GraBox. I forget why it's in there.
The eXpress train is coming - and it has more cars.
Re: Build 256
I don't understand your #3 request.
What do you mean by a menu block?3. DCGET OPTIONS ... BUTTONS: The accelerator key (element 11) and the tooltip
(element 9) don't work. Having the option to create a menu block for the
buttons there would be just wonderful (element 12? ).
The eXpress train is coming - and it has more cars.
Re: Build 256
Tom -
I have a goal to release build 257 this week and I still don't understand your request.
Roger
I have a goal to release build 257 this week and I still don't understand your request.
Roger
The eXpress train is coming - and it has more cars.
Re: Build 256
Hi, Roger.
DCPUSHBUTTONXP has a MENUACTION clause, which places a menu button on the button itself and allows to create a submenu for the button. I'd love to have that with the BUTTONS <aButtons> feature of DCREAD GUI.
DCPUSHBUTTONXP has a MENUACTION clause, which places a menu button on the button itself and allows to create a submenu for the button. I'd love to have that with the BUTTONS <aButtons> feature of DCREAD GUI.
Best regards,
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."