Page 1 of 1

Visible Property for Report Designer Components - Conditions

PostPosted: Tue Jan 06, 2009 3:35 pm
by Luiz Alfredo
What about a Visible property for the Report Designer components, based in some conditions (Database Fields Values).

This way we could have many options for making graphical reports, based on the conditions. We could even make Dashboards and related stuff.


Luiz Alfredo G. Menezes

PostPosted: Wed Jan 07, 2009 11:13 am
by Neosoft Support
Interesting idea. How would that work?

PostPosted: Thu Jan 08, 2009 8:37 am
by Luiz Alfredo
For example, in the Picture Properties of the Logo in Invoice, we have in the Display Options:

- Maintain aspect ratio
- Center image

We could have a new box:
- Visible

If we check Visible we could have a new field called Condition.

If nothing is entered it will be visibe (True)

If the Condition Formula (which will use Database Fields and Neobook Formulas for evaluation) returns True it will be Visible. If not it will be not Visible.

This way we could have different Images/Pictures (including Database Images/Fields) for different report results.

It would open many possibilities, cause if some field or calculation or query result, has a value of 60, we can manipulate images for showing a Dial with 60%. An so on.

If in other components like Formulas we also have the Visible, we could have it shown if the Condition is True. The condition could have a Formula Creator using <, <=, =, >=, >, <> (different), Field Names, Numbers, Sum, Avg, etc.

Rectangles and Ellipses should have also the Visible property, and in this cases also a Gradient option, for making Charts in Reports easier.

Imagine the possibilities.

If in future versions Report Designer could have also some more components like Charts, Dials Thermomethers with Min Values, Max Values, Indicator Value, Visible Property, Color Options.

In Neobook Components also, like Buttons and Track Bars, if we had a Condition for Visibility it would be nice, but in that case we can use Show Object and Hide Object.

Neobook RAD can be Superb. Users do not care much about Values for Payment, when the results can be achieved with good feedback.



PostPosted: Thu Jan 08, 2009 12:08 pm
by Neosoft Support
Thank you for your detailed response. I will definitely add your suggestion to the list of things to consider for a future update.

PostPosted: Thu Jan 08, 2009 1:02 pm
by Neosoft Support
The most recent NeoBook update was two months ago. An update to our DBPro plug-in is currently in beta test.

The development of updates is something that we are constantly working on. Because there are so many variables involved in software development, we have learned (from experience) never to promise updates for a specific time frame or date range. It's simply too difficult to predict how long a specific programming project will take. Also, announcing updates too far in advance tends to suppress sales of existing versions.