Re: Compiling Gnucash 2.2.0 on Solaris 10 x86 using GCC - error

2007-07-29 Thread Peter FELECAN
Slightly OT but if you just need a GnuCash on Solaris you can get it
from http://www.blastwave.org/ It's 2.0.2 and I think that I'll
package 2.2 later in August.
-- 
Peter
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel


Re: Compiling Gnucash 2.2.0 on Solaris 10 x86 using GCC - error

2007-07-29 Thread Derek Atkins
Quoting Peter FELECAN [EMAIL PROTECTED]:

 Slightly OT but if you just need a GnuCash on Solaris you can get it
 from http://www.blastwave.org/ It's 2.0.2 and I think that I'll
 package 2.2 later in August.

You REALLY should use 2.0.5, not 2.0.2..
Or, of course, 2.2.0, but I suspect 2.2.1 will be out in a few weeks.

 Peter

-derek

-- 
   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
   Member, MIT Student Information Processing Board  (SIPB)
   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
   [EMAIL PROTECTED]PGP key available

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel


Re: Compiling Gnucash 2.2.0 on Solaris 10 x86 using GCC - error

2007-07-29 Thread alanpae
Quoting Peter FELECAN [EMAIL PROTECTED]:

 Slightly OT but if you just need a GnuCash on Solaris you can get it
 from http://www.blastwave.org/ It's 2.0.2 and I think that I'll
 package 2.2 later in August.

Thanks for the offer but I don't use Blastwave.

===
You REALLY should use 2.0.5, not 2.0.2..
Or, of course, 2.2.0, but I suspect 2.2.1 will be out in a few weeks.
===

Any chance that we can get this nailed down before then?

thanks,
alan
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel


Small feature request: better tab behavior in Split transactions

2007-07-29 Thread Christopher Blunck
Hello,

I've been using GnuCash since 2004 and love it.  I've talked it up to  
several different people and they're now happy GnuCash users.  It's a  
great tool that fills a huge gap in the OSS community.

All that being said, I'm absolutely pulling my hair out over the  
behavior of tab (keystroke), return (keystroke), Delete (button  
on the toolbar), and Cancel (button on the toolbar) when journaling  
split transactions.  I'll do my best to describe my frustrations, and  
hopefully this will start a discussion that will result in a ticket  
being that improves the end user experience when journaling split  
transactions.

Here are some scenarios that cause me great heartburn.  Maybe there  
are workarounds that I'm unaware of?

Issue #1: The tab key behavior.
Steps to reproduce:
1.) Press Split
2.) Create a description for the entire split transaction.  Call it  
My Credit Card.
3.) Press tab once, and you get to the Action column.
4.) Press tab again, and you're at the Memo.  Tab again to get to the  
account.  Tab another 2 times and you're at Charge.  Enter 500.
5.) Hit tab.  You are brought to a new line in the split  
transaction.  That's great!  That's what I expect!
6.) Enter a description.  Hit tab to get to the Account, and choose  
an account.  Hit tab and enter 25 for the payment.
7.) Hit tab and you're at the Charge column.  Hit tab again.  THIS IS  
WHERE THE PROBLEM IS.

Rather than taking you down to a new subtransaction in the existing  
split transaction it takes you back up to the date column for the  
entire transaction.  This behavior is inconsistent with the behavior  
seen in step #5.  If you press tab on step #5 and you are brought to  
a new subtransaction line why doesn't that ALWAYS happen?

I tried using return at the end of #7 to get to a new  
subtransaction.  That gives me a new subtransaction but the account  
is set to Imbalance-USD.  When I enter a memo that I've already  
entered before (e.g. Exxon) GnuCash doesn't auto-populate the Account  
based upon what Account was used the last time I entered that memo  
(Expenses:Auto:Gas).  As a result, the return behavior, while it  
solves the problem of creating subtransactions, creates a NEW problem  
of not auto-populating the Account.

Note: I've also tried going down to the bottom of the split  
transaction and hitting Enter.  You get a blank subtransaction  
line, and the auto-populate of the Account works.  But hitting  
Enter at the end of that subtransaction brings you to the line that  
contains the split transaction itself.

The bottom line is that there doesn't appear to be a keyboard only  
way of journalling a split transaction, and that's a huge pain in the  
neck when I'm journalling my credit card statement (it has over 200  
transactions sometimes).  Going from keyboard to mouse and then back  
to keyboard significantly slows me down.

GnuCash 1.x didn't have this behavior.  Please help restore the  
GnuCash 1.x behavior of tabs in split transactions.


Issue #2: Cancel button in a split transaction doesn't work.
This is a usability and interface improvement issue.  Delete,  
Cancel, and Blank are very similar to non-programmers.  I  
understand the subtleties, as I'm a programmer.  But my Dad wouldn't  
know what Delete means vs Cancel vs Blank.  There are lots of  
times that I'm in a split transaction and I want to remove one of the  
transactions involved in the Split.  Since the Cancel button has a  
big red X it catches my eye faster than a garbage can.  As a result I  
tend to click the Cancel button when I mean to click the Delete  
button.  Can you maybe disable the Cancel button when you're in a split?

Issue #3: Blank doesn't blank a transaction.  It takes you to the  
bottom of the ledger.  I understand that this is intuitive to you  
all, but it's not at all intuitive to an end-user.  If I'm in the  
middle of a 200 transaction split and I hit Blank I'm expecting that  
it will blank out the current transaction I'm on.  I don't expect it  
to take me to the end of the account ledger.

Note that I'm using GnuCash 2.1.1 (from r16107:16109M) built from  
source under OSX.

I love GnuCash, but every time my credit card statement comes in I  
hate journalling it because of the time it takes.  And no, I don't  
care to set up QIF imports of my statements.  The last time I did  
that it didn't work very well at all...

Thanks for your time, and I look forward to your responses to my  
above issues.



-c

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel


Re: Small feature request: better tab behavior in Split transactions

2007-07-29 Thread Josh Sled
Christopher Blunck [EMAIL PROTECTED] writes:
 seen in step #5.  If you press tab on step #5 and you are brought to  
 a new subtransaction line why doesn't that ALWAYS happen?

Because there's a bug in the tab handling.  I believe it's already been
filed, but I don't have time at present to find it at
http://bugzilla.gnome.org/browse.cgi?product=GnuCash.


 The bottom line is that there doesn't appear to be a keyboard only  
 way of journalling a split transaction, and that's a huge pain in the  
 neck when I'm journalling my credit card statement (it has over 200  
 transactions sometimes).  Going from keyboard to mouse and then back  
 to keyboard significantly slows me down.

I regularly only use the keyboard.  With auto-split mode and a bit of extra
tab-/arrow-ing after it resets back up to the description, I get by.  It is
annoying that the focus resets to the description, however.


 GnuCash 1.x didn't have this behavior.  Please help restore the  
 GnuCash 1.x behavior of tabs in split transactions.

What you're seeing isn't an intentional change in behavior so much as a side
effect of a change in an overly-complex piece of GnuCash (the register).

I'm not saying the bug shouldn't get fixed or the behavior shouldn't change,
of course.  But if you're conceiving of it as an intentional change we can
revert, you're wrong.


 Issue #2: Cancel button in a split transaction doesn't work.

The Cancel button in a transaction works exactly as it should: it cancels
editing the Transaction.

(A bit of clarification: a Transaction contains Splits (lines).  All
Transactions are split transactions, even if we only show one of the Splits
(i.e., in Basic register mode)).

 Issue #3: Blank doesn't blank a transaction.  It takes you to the  
 bottom of the ledger.  I understand that this is intuitive to you  

Given that we have the following concepts:

- Cancel Transaction (being edited)
- Enter Transaction (being edited)
- Delete Transaction
- Delete Split (in Transaction)
- Remove (all) Transaction Splits
- Blank (goto the Blank Transaction)

What other names would you suggest?

Blank could be safely renamed New Transaction, I think.  I think the icon
is appropriate, but I'd agree the name there is not as unambiguous as it
could be.

-- 
...jsled
http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED]


pgpKroHsEgFru.pgp
Description: PGP signature
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel


Re: r16102 - gnucash/trunk/src/gnome-utils - Unregister option dialogs from gui component list while destroying.

2007-07-29 Thread Chris Shoemaker
On Sat, May 19, 2007 at 07:19:47PM -0400, Andreas Köhler wrote:
 Author: andi5
 Date: 2007-05-19 19:19:44 -0400 (Sat, 19 May 2007)
 New Revision: 16102
 Trac: http://svn.gnucash.org/trac/changeset/16102
 
 Modified:
gnucash/trunk/src/gnome-utils/dialog-options.c
 Log:
 Unregister option dialogs from gui component list while destroying.
 

FYI, this fixes a crasher introduced by r15976.  r15976 was backported
to to the 2.0 branch, in case we were to ever release a 2.0.6.
However, this commit wasn't marked for backport.  So, we should either
backport this, or just decide not to do anymore releases from the 2.0
branch.

-chris

 
 Modified: gnucash/trunk/src/gnome-utils/dialog-options.c
 ===
 --- gnucash/trunk/src/gnome-utils/dialog-options.c2007-05-19 23:19:39 UTC 
 (rev 16101)
 +++ gnucash/trunk/src/gnome-utils/dialog-options.c2007-05-19 23:19:44 UTC 
 (rev 16102)
 @@ -1485,6 +1485,8 @@
  {
if (!win) return;
  
 +  gnc_unregister_gui_component_by_data(DIALOG_OPTIONS_CM_CLASS, win);
 +
gtk_widget_destroy(win-dialog);
  
if(win-tips) {
 
 ___
 gnucash-changes mailing list
 [EMAIL PROTECTED]
 https://lists.gnucash.org/mailman/listinfo/gnucash-changes
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel