On 3/30/11 12:59 PM, Nate Lowrie wrote: >> While I've experienced the same classes of problems as you, I'm not >> convinced that >> > adding properties to rfxml is needed. The ReportDesigner is simply >> > lacking in basic >> > smarts about how to position things sanely when the expressions don't >> > evaluate at >> > design-time. > How would you approach the positioning problem?
I'd iterate the objects in z-order, drawing each based on their evaluated expressions. In the case of an x or y not evaluating, I'd find the first horizontal or vertical position that doesn't cover up a previously-drawn object. Actually, now I've typed that I think it is too simplistic. Maybe following what you hinted at and offering these properties would help: DefaultX DefaultY DefaultWidth DefaultHeight DefaultExpr At design-time, if the appdev sets x to an expression that evaluates without error, DefaultX also gets set to that same literal, otherwise DefaultX keeps its prior value. If the appdev explicitly sets DefaultX though, it'll never be overridden automatically. So at design-time or run-time, if any of the properties don't evaluate, the Default* property will be used. I actually like this, and could get behind implementing it for all properties, not just the ones listed above, since all report properties are evaluated at runtime. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
