Cause was that gnc_split_register_get_account_by_name() turned of "full_refresh" if the account didn't already exist and turned it back on only if the name of the account actually created in the new account dialog box differed from the one originally entered in the transaction.
Since "full_refresh" isn't manipulated much, that effectively shut down the ledger for further editing. Probably not what the original author intended!
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19847 57a11ea4-9604-0410-9ed3-97b8803252fd
wasn't enabled before the xsltproc issue popped up, so it shouldn't
be enabled now.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19817 57a11ea4-9604-0410-9ed3-97b8803252fd
Patch by Mike E:
The current error feedback to a python scrpt/user looks something like:
call to begin resulted in the following errors, (7,)
This change in gnucash_core.py makes the feedback similar to:
call to begin resulted in the following errors, ERR_BACKEND_LOCKED
This is less cryptic and aid debugging of user python scripts. My only
issue though is whether this would break existing user scripts where checking
of this error code is used for flow control. Although since the ERR_ codes are
imported with gnucash_core_c it *should* have no effect.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19808 57a11ea4-9604-0410-9ed3-97b8803252fd
The menu items under "File" should relate only to the file (database),
not to anything within a file. The open/new for all other things (budget,
invoice, account) have been moved somewhere else.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19806 57a11ea4-9604-0410-9ed3-97b8803252fd
A fairly extensive change, because I changed may_clobber from a global
qof function (which passed through qofbackend and fetched up in the
actual backends) to a local static in the individual backends which
raise a new qof_backend_error, QOF_ABCKEND_STORE_EXISTS. This was
necessary to reorder the existence check before the lock, because with
the sql backends, locking creates the database... which then would
return may_clobber as true, even though it really wasn't.
New parameter "force" added to session_begin() functions, and
"create_if_nonexistant" is renamed to simply "create". The reason for
the latter is that the file/database is created regardless of whether it
already exists; that's what the clobber check is about. The new "force"
parameter is set to true the second time through, after the user has
responded to the clobber dialog indicating that the data should be
destroyed.
Many of the extraneous changes are just adding the new parameter to the
session_begin() calls.
gnc-file changes to handle the error in favor of calling the
no-longer-existing qof_check_may_clobber_data() call after
session_begin().
Two minor changes to gnc_file_do_save_as: gnc_add_history and
gnc_hook_run are now called on new_session instead of old_session; this
ensures that the new file/database is used at the next startup of
gnucash. Second, the filename/url is filtered before displaying the
"may_clobber" dialog box to prevent displaying plaintext database
passwords.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19798 57a11ea4-9604-0410-9ed3-97b8803252fd
Patch by Christoph Holtermann:
For the second enhancement proposal i have attached a simple patch which adds
the argument ignore_lock to Session.__init__() which is passed through to
qof_session_begin.
This patch extends the function Session.__init__() with ignore_lock
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19795 57a11ea4-9604-0410-9ed3-97b8803252fd
we can handle. Wrap fileURLWithPath in @try/@catch so that we don't
crash when it throws.
Free bonus fix: If "en" is the language and doesn't have a translation, force the C locale.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19785 57a11ea4-9604-0410-9ed3-97b8803252fd
When I open a report window (barchart in the example) and select only one
account, I get a column header saying "nil" near the only data column.
Someone accidentally wrote "nil" instead of the empty list '().
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19783 57a11ea4-9604-0410-9ed3-97b8803252fd
In the "bills due" dialog we use Bill -> Rechnung, not Lieferantenrechnung.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19782 57a11ea4-9604-0410-9ed3-97b8803252fd
If during startup a file or database turns out to beeing locked the user is
presented a dialog with the options to open anyway, create a new file or abort.
This dialog, however, closes the splash screen. This may cause confusion,
because file loading and report generation may still take quite some time.
Patch by Herbert Thoma.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19781 57a11ea4-9604-0410-9ed3-97b8803252fd
Follow-up to r19757 which was incomplete. Hopefully I now really got everything.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19758 57a11ea4-9604-0410-9ed3-97b8803252fd
The last occurrence wasn't counted because it was still valid
but turned num_occur_rem to zero, hence the counting stopped one too early.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19757 57a11ea4-9604-0410-9ed3-97b8803252fd
* Check for a null gdate before attempting to make it a string. Fixes a bunch
of CRIT errors.
* Comment out the log debug setting in dbi. It's stable enough that it
shouldn't be needed routinely. It can, of course, be enabled from the command
line.
* Add a notice to ignore the warnings about there being no lock on the
database when session 3 is closed. Session 3 has to be run with ignore
locking or it won't run at all.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19755 57a11ea4-9604-0410-9ed3-97b8803252fd
