MDI and End User Custom Explorer
Hi All
I seem to have run into problems with a custom report explorer form after
upgrading the application to RB 9.03 and Delphi 7.
When you go in to design a report and attempt to float the toolbars, they
appear to be getting parented to the applications main form and not the
designer form. Some buttons with a drop down arrow also drop down and then
disappear before they can be clicked. This means they disappear from the
designer and appear on the main form but are then innaccesible.
I have tried the example 'ReportExplorerWithinPanel' using the default
explorer form and this does not exhibit this behaviour. I think I have set
up everything in a similar way to this example. It appears to be just my
custom explorer.
I cannot locate the problem, can anyone help please?
Regards
Paul.
I seem to have run into problems with a custom report explorer form after
upgrading the application to RB 9.03 and Delphi 7.
When you go in to design a report and attempt to float the toolbars, they
appear to be getting parented to the applications main form and not the
designer form. Some buttons with a drop down arrow also drop down and then
disappear before they can be clicked. This means they disappear from the
designer and appear on the main form but are then innaccesible.
I have tried the example 'ReportExplorerWithinPanel' using the default
explorer form and this does not exhibit this behaviour. I think I have set
up everything in a similar way to this example. It appears to be just my
custom explorer.
I cannot locate the problem, can anyone help please?
Regards
Paul.
This discussion has been closed.
Comments
My first suggestion would be to begin simplifying your custom explorer in
order to more closely mimic the existing explorer in RB 9.03. You may even
try starting with the current explorer and begin adding your customizations
periodically in order to isolate the one causing the problem.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
I did try removing the custom explorer unit and allowing it to use the
default explorer. However, when this is within the main application, the
problem is still there. I feel it must be something to do with the way the
forms are created or the order in which it occurs.
Is there a watch I could add to confirm what's happening?
Have you any other ideas?
I notice the use of the timer in the example to start the process, is this
critical?
All the forms styles are set as in the 'panel' example and other properties
which I think would be relevant are the same, there must be something very
simple that I can't track down.
I've been trying to fix this for two days now but have got nowhere, is there
anything else you could think of?
Thanks, Paul
I have traced the problem to the DockSite property on the application main
form. When this is set to true, the designer toolbars attach themselves to
this form rather than the designer form.
There is also a bug evident within the ReportExplorerAsMDIChildProj.dpr
example.
Please follow these steps:
Run the ReportExplorerAsMDIChildProj sample.
Click the button to create a new report.
Drag the Format toolbar from the top and allow it to float anywhere over the
designer.
Close the designer
Close the application
You then get a couple of exceptions and a runtime 216 error.
You don't get this when the toolbar remains docked to the top of the
designer.
You can also try
Run the ReportExplorerAsMDIChildProj sample.
Click the button to create a new report.
Go to the Customers folder and design the Customer List report
Select any label on the report
Drop down the Highlight Colour menu next to the speed button ( don't click
any colours )
Move the mouse over the Font colour speed button
You will see both the Font & Highlight menus behave erratically now,
sometimes they drop down, sometimes not. Also they can disappear when you go
to actually click one of them.
Regards, Paul.