WYATT  In 3.2.2.3 I added a workaround to refresh the state of the account window, which is what is making it open again. The actual bug appears to be in a third party library, so I cannot fix it directly; I think that this 'fix' is as good as it will get until the library itself is fixed.

Cheers  
(Version 3.2.2.3)

WYATT  I have implemented this as of development version 3.3.0.0. This version will not be released for a little while, as I am in the process of working with another developer to allow split transactions, and will not release it until that is finished. However, keep watching for updates, and you will get this eventually ;-)

(FYI, 3.3.0.0 will be released as a development release, and will probably take a bit of time to become considered stable. At the very latest, though, you can use this feature in 3.4.0.0, which will be the first 'stable' release after 3.3.x. See http://buddi.thecave.homeunix.org/en/faq.jsp, "How do I interpret your version numbers?" for information on how I determine the version number.)

Cheers  
(Version 3.2.2.3)

WYATT  Ahh, gotcha. The reason I removed that field was that it was not used in the program at all (and it had the potential to be confusing - people expected that it would actually calculate interest, etc, but that is beyond the scope of the program).

I can easily re-add that field, sort of as a 'for information only', and make a note that it does not calculate interest.

Cheers  
(Version 3.2.2.2)

WYATT  Just to verify, in your comment you mention interest rates. The only extra field I have in accounts is the overdraft / credit limits. Is this what you mean? Or do you have interest rates in the notes section?

I have added an 'Available Funds' column on the My Accounts screen, if you have either overdraft or credit limit active in Preferences. This will show you either the amount of money left before you reach your credit limit (for Credit accounts), or the amount of money you can spend before reaching your overdraw limit (Debit accounts).

This is not yet in the stable version, but is in a development preview release 3.3.0.0 - if you are interested, you can grab it from http://buddi.thecave.homeunix.org/builds/ . Note that this is not tested, and there have been some changes to the data model, which may corrupt your data. If you *save* using this version, you will not be able to open it in previous versions, so please backup your data before running this!

Please let me know if you have any further questions / comments about this feature.

Cheers  
(Version 3.2.2.2)

WYATT  Not sure about this, as it seems to be a MacUpdate issue. However, in the future, you can always go to http://buddi.thecave.homeunix.org/buddi.dmg, and you will always get the most recent version.

Cheers  
(Version 3.2.2)

WYATT  Hello,

1) That should not be a problem... I can't remember why I removed it in the first place (I think that it was just something that I missed when converting to the new 3.0 version). Can you please add a feature request via the Buddi web site (http://buddi.thecave.homeunix.org/en/support.jsp)? I only rarely read these comments, and generally use the official feature request list for new features / bugs. If it is on the official list, I tend to remember it better.

2) This is an annoying bug which I have been aware of for some time; however, from what I can tell, it is a bug in the third party component I am using. I will look into it some more to see if I can figure out what is causing it.

Cheers  
(Version 3.2.2)

WYATT  This is due to how Apple launches Java programs. The actual launcher which is contained in the application package is a PPC binary; however, at launch time, OS X detects this and substitutes the Intel version of the launcher instead. You can see this in your system messages as "[JavaAppLauncher] application launched with ppc-thin application stub. Using native application stub instead".

As another poster pointed out, since this is Java, even the launcher itself does not matter - it runs in a special virtual machine, which itself is implemented in either Intel of PPC instructions.

Cheers  
(Version 3.2.0.1)

WYATT  It may be native, but it is still slower than Gimp, with fewer functions. I was a beta tester for Pixelmator, and while it does look very nice, it is substantially slower then the Gimp. Perhaps in a few more iterations, it will get the speed that was promised, but for now, I am sticking with the Gimp!

Cheers  
(Version 2.4rc3)

WYATT  Thanks for your feedback. FYI, I have added request #1 to Buddi 3.0 (currently in Beta, but should be released as a Developer download within a week or two).

The reason I was unable to do this before was due to the problems changing the data file format - the old version of the Buddi data file was not very resilient to change, and could easily become corrupted if I changed too much. In 3.0, I have completely redone the data model from scratch, and thus was able to make some architectural changes which I have wanted to for some time, but have been unable to do previously.

Cheers  
(Version 2.6.1)

WYATT  You may want to take a look at the new 2.4 branch. I have completely revamped the transactions window area, which now looks much more like a standard ledger would - with two columns for debit / credit, consistent colors for positive / negative amounts, etc.

Cheers  
(Version 2.4.1.1)

WYATT  When running Java applications, if the JavaApplicationStub is not a Universal Binary (such as in Buddi's case), OS X will automatically launch the correct Universal version of it. When you run it, you should be able to verify this via Console.app - there should be a message saying that 'This application is using a PPC version of JavaApplicationStub; an Intel version will be used instead'. While I don't have a MacBook myself yet, I tried running Buddi on one, and verified that this is indeed the case.

As for Cyberduck, it is a Cocoa-java application, while Buddi is a pure Java application (using Swing as the GUI). To make a long and boring technical story short, they are compiled and launched in different ways, and are not equivalent to each other. Since Buddi is designed to be cross platform, I have no plans to convert it to Cocoa-java, as it would lose all cross platform support.

Basically, whatever slowdowns you are experiencing should not be due to the processor architecture; it may be due to an increase in the number of transactions, although that really should not be noticeable. Once I get some more time, and the volume of feature requests decreases a little, I may take some more time to profile Buddi and see where most of the time is being spent. If you give me a little more information, I may be able to give you a better answer (for instance, where do you notice the slowdown? Is it at startup? Is it when you resize a window? When you add a transaction?)

Hope this helps

Cheers

--Wyatt  
(Version 2.0.3)

WYATT  The problem creating a new data file, introduced in 2.0.2, has been fixed in 2.0.3. Thanks for those who pointed this out to me!

Cheers

--Wyatt  
(Version 2.0.3)

WYATT  Thanks for pointing this out! It has now been fixed.  
(Version 2.0.3)

WYATT  Thanks for pointing this out. It has been fixed now.

Cheers!  
(Version 2.0.3)