On May 3, 2009, at 12:10 PM, Montek wrote:
> First of all thanks to everybody for the product. It's really
> powerful.
> I'm try to develop an application based on PostgreSQL 8.5. Till now
> things have kept going quite fine but i have a couple of suggestions:
> the first one is about some form of localization. Having to develop an
> italian application, some how i need accented chars spread among the
> code and without some '<string>.decode(dabo.defaultEncoding)' or
> '<string>.decode(dabo.defaultEncoding)' within the framework's code i
> couldn't avoid compiler errors.
Dabo does have localization; the dLocalize module handles this, and
defines a standard _() function for designating strings to be localized.
We have several international developers who have been extremely
helpful in tracking down parts of the Dabo codebase where unicode
encoding issues cause problems. If you can let us know where the
framework still has issues with encoding, we'll be happy to fix it.
> Well, the second is about the 'onCurrent" event (fires each time a
> record in the recordset is about to become current) so widely used by
> VisualBasic programmers.
> To better explain its use i try to show the scenario: Suppose you
> have a
> field of a type which is not handled directly by the framework (e.g.
> an
> array of an array of datetime objects).
> In such a situation you cannot bind this field to a data control in
> the
> form for lack of representation methods (also virtual fields don't
> help
> in this case because a control can be bound only with known types)
> The workaround could be to override the afterMovePointer method and
> update manually the control with a representation extracted from the
> field value of the current record.
> The problem is, nevertheless, that this event fires only if the record
> pointer is moved "manually". By the first display update, for example,
> upon form creation, this event doesn't fire.
> The 'onCurrent' event of the old VisualBasic would do the trick.
> Any suggestions?
There is the RowNumChanged event, and that will fire on the initial
requery, as well as any time the user moves to a new record. Have you
tried binding to that event?
-- Ed Leafe
_______________________________________________
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]
