add category to a debit trans: impossible to specify amount

[mary]

Hi,

I just upgraded to 3.3.3 and I noticed a problem with adding a category to a transaction. It seems to happen only with debit transaction.

Example:

I have an item for 550euros of cash retrieval, so debit.
I want to specify 438euros as category A (of course as debit) and the remaining as category B.

What I would normally do is: 1. adding category A; 2. edit the amount field typing 438; 3. adding category B, which would automatically cover the remaining.
If i do so, 438 is considered as credit, (green sign next to the number), if I click the green sign it turns red, but the number goes to 0.
If i type -438 the number turns into (0).
If i type (438) I get a format error.

If i specify the percentage, the corresponding number keeps being blank, I have to select another transaction and then back the current one to see the computed numbers.
So, specifying the percentage "solves" my problem, but I'd prefer to specify the amount, computing the percentage is an extra step and it's not precise.

Last, a general question: why did you change the format of debit number as (num) instead of -num? Is it possible to set it as a preference?

Thanks a lot!
Good job

-mary

[Angeman]

Are you on Leopard or Snow Leopard ?

Could you please send me a screenshot of your regional settings like this ? Thanks

Capture d’écran 2009-09-05 à 20.45.32.png (67.15 KiB) Viewed 5716 times

[hbork]

I am also having this problem, after upgrading to iCompta 3.3.3, running Snow Leopard.

I would include a screenshot of my settings, but I am not certain how to access that screen from the program. (My 'Preferences' pane has nothing like that in it.)

*EDIT* -- Ah, I just realized that was the system-wide OSX settings; I haven't gotten used to the new Pref-panes, yet.

I have attached a snap of my settings.

Language & Text.png (94.47 KiB) Viewed 5626 times

[mary]

here it is

regional_settings.png (75.1 KiB) Viewed 5616 times

And I also have the pbm with negative numbers reported in the other post.

Thanks!

[Angeman]

Thanks for you help, it should be fixed in 3.3.4.