Page 1 of 1
Layout controls disabled in designer
Posted: Wed Jul 06, 2011 7:42 pm
by jay@bplogix.com
The "Arrange" controls like Bring to Front, Send to Back etc are disabled unless there is a rectangle, line, or rounded rectangle drawn on the canvas. If you draw an rectangle anywhere on the canvas, then the Layout controls correctly function for all objects (text controls, graphs, etc). But if you remove all the rectangle, then the controls are disabled and you cannot change the Layout of any other controls on the page.
Layout controls disabled in designer
Posted: Thu Jul 07, 2011 8:52 am
by Vladimir
Hello,
We have reproduced this error, we will fix it for the next prerelease build on July, 14.
Thank you.
Layout controls disabled in designer
Posted: Mon Jul 18, 2011 6:22 pm
by jay@bplogix.com
It is a little better now ... but the Layout controls are disabled sometimes when they should not be.
To reporduce, use only a ReportTitleBand (common when your report is just a chart and some text). Most of the time the Arrange controls are ghosted. They seem to be enabled when you add a DataBand, but they should be enabled even when the DataBand is not present.
Thanks
Layout controls disabled in designer
Posted: Tue Jul 19, 2011 8:40 am
by Vladimir
Hello,
Now we cannot reproduce this error. Could you describe it in more detail, as well please send us your report on which this error is reproduced.
Thank you.
Layout controls disabled in designer
Posted: Wed Jul 27, 2011 7:32 pm
by jay@bplogix.com
I attached a simple report which reproduces the problem (latest build SW_2011.07.23).
Basically click on the text box. The layout controls are sometimes disabled. Click on the page, then back onto the text box. Sometimes the layout controls work, sometimes they are ghosted.
Notice in the screen-shot that when I select the text box, the Layout controls (bring forward, send back, etc). This happens sometimes even if there are many controls on the page.
Layout controls disabled in designer
Posted: Fri Jul 29, 2011 3:05 am
by Vladimir
Hello,
The error is fixed, the update will be available in the next prerelease build on August, 4.
Thank you.