In my app I mainly use Berg and TMS controls.
Whenever I place a NextGrid or an Inspector on a TAdvOfficePager, then they are not painted correctly. Simply add some rows and select a cell and something else from the screen is displayed instead of the rows.
NextComponents are the only components which are not painted correctly, all other components I use don't have this problem. Do you have a solution for that?
I use D2009 and the latest versions.
Conflict between NextGrid and TMS TAdvOfficePager
Started by mark, Feb 06 2010 03:24 PM
4 replies to this topic
#1
Posted 06 February 2010 - 03:24 PM
#2
Posted 06 February 2010 - 08:35 PM
I just ran another test, NextGrid and NextInspector also fail when I place them onto a TAdvPanel
#3
Posted 06 February 2010 - 11:11 PM
Hello Mark,
It seems that TMS TAdvOfficePage use DoubleBuffering to True and this is why problems happen since NextGrid uses some techniques for flicker-less drawing.
I have no idea how this may be solved, but maybe you can try to set AdvOfficePager.DoubleBuffer to False.
Best regards
It seems that TMS TAdvOfficePage use DoubleBuffering to True and this is why problems happen since NextGrid uses some techniques for flicker-less drawing.
I have no idea how this may be solved, but maybe you can try to set AdvOfficePager.DoubleBuffer to False.
Best regards
boki@bergsoft.net | LinkedIn Profile
--
BergSoft Home Page: www.bergsoft.net
Users Section: users.bergsoft.net
Articles and Tutorials: help.bergsoft.net (Developers Network)
--
BergSoft Facebook page
--
Send us applications made with our components and we will submit them on: www.bergsoft.net/apps.htm. Link to this page will be also set on home page too.
--
BergSoft Home Page: www.bergsoft.net
Users Section: users.bergsoft.net
Articles and Tutorials: help.bergsoft.net (Developers Network)
--
BergSoft Facebook page
--
Send us applications made with our components and we will submit them on: www.bergsoft.net/apps.htm. Link to this page will be also set on home page too.
#4
Posted 06 February 2010 - 11:19 PM
QUOTE
I have no idea how this may be solved, but maybe you can try to set AdvOfficePager.DoubleBuffer to False.
This should fix it:
NextGrid1.DoubleBuffered := FALSE;
If you use "NextGrid.DoubleBuffered := TRUE" on a (for example) TNxPageControl, you'll have the same effect.
Boki, would it probably make sense to check that property in your components at runtime and disable it to avoid such a conflict? Seems that it is required to have it disabled in your components.
#5
Posted 07 February 2010 - 01:58 AM
Hello Aim,
I will consider this.
Best regards
I will consider this.
Best regards
boki@bergsoft.net | LinkedIn Profile
--
BergSoft Home Page: www.bergsoft.net
Users Section: users.bergsoft.net
Articles and Tutorials: help.bergsoft.net (Developers Network)
--
BergSoft Facebook page
--
Send us applications made with our components and we will submit them on: www.bergsoft.net/apps.htm. Link to this page will be also set on home page too.
--
BergSoft Home Page: www.bergsoft.net
Users Section: users.bergsoft.net
Articles and Tutorials: help.bergsoft.net (Developers Network)
--
BergSoft Facebook page
--
Send us applications made with our components and we will submit them on: www.bergsoft.net/apps.htm. Link to this page will be also set on home page too.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users











