On Tue, Apr 1, 2008 at 3:15 PM, Charles Day <[EMAIL PROTECTED]> wrote:
> On Tue, Apr 1, 2008 at 1:20 PM, Andreas Köhler <[EMAIL PROTECTED]> wrote:
>
> > Hi Charles,
> >
> > Am Dienstag, den 01.04.2008, 13:01 -0700 schrieb Charles Day:
> > > I have come up with a working fix for bug
> > > 450354
I have looked into trying to combine the existing Swig interface files and
the python-bindings interface files. As far as I can tell there isn't a way
to specify multiple language specific sections in a single interface file
(someone please correct me if I'm missing something). The best bet might b
When manually entering new transactions in the register, how does the
auto-fill capability work? Does it (a) just look at existing transactions,
make a guess at a match, then copy the information? Or does it (b) draw that
information from a bucket of "memorized transactions"?
Quicken does the latt
Jeff Green wrote:
> The best bet might be to put the non-language specific stuff into a
> separate file (it would mostly consist of common typedefs and function
> declarations) and have the language specific interface files %include
> that file.
> I think doing it this way would work well, I'm jus