Suggestions for next version

rbuser

Hi,

I have several suggestions for the next version:

- make the multi-selection working properly; I mean that if I select several
TppVariable and set the font style to Bold, every selected TppVariable
should be bold, not only the first selected.
- having aggregates functions (Sum, Min, Max, Average, Count, Distinct
Count) working on TppVariable. Could be something another component called
TppVarCalc if TppDBCalc can't fit.
- improve the Calc Editor. I have some drawing issues while using it, like
having a half of a word in bold and the other half in normal. It doesn't
give problems on compiling, but it's a small thing.
- Having TppVariable descendant that can be filled with a TppParameter.

David Caouette

nicocizik

Hi David,

Thanks for the suggestions .

--
Regards,

Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com

rbuser

I knew I forgot something :

- support for array types. I wish I could declare an array in Calc Editor,
but I can't. Is there any way using RAP RTTI ?

David

rbuser

I think that the "multi-selection" suggestion is very important too.
Changing a property to 30 components 'one-by-one' is not so cool

rbuser

I would be pleased to perform beta-tests on the next version.

David Caouette
Omniciel international inc.

nardmoseley

Just to clarify. There is actually support for this now - though it is
limited to setting font related properties from the Format Toolbar. You can
select any number of components and use the Format toobar to select the font
name, font style, etc. The object inspector and context menus do not
currently contain any multi-selection support - that would be a nice feature
addition...





--
Nard Moseley
Digital Metaphors Corporation
http://www.digital-metaphors.com

rbuser

Thanks, Nard.

When I talked about the multi-selection, it was related to Object Inspector
and contextual menu. Thanks for the clarification.

David Caouette

rbuser

Hello,

another suggestion : when I get i.e: "Could not convert Variant (String)
into (Double)", the faulty component name should be included in this
exception string.

David Caouette