> On Nov 25, 2019, at 9:44 AM, Derek Atkins wrote:
>
> Adrien Monteleone writes:
>
>>> Again, if user A has a data file open, user B shouldn't also open
>>> the file. I don't see how a check for Gnucash instances could work
>>> to prevent precisely this problem, since my machine won't have an
HI,
On Mon, November 25, 2019 2:01 pm, David Carlson wrote:
> If I understand, Derek, you are proposing a change to GnuCash code to
> improve it's behavior.
Yes, I am proposing a small code change. I'll note that even changing the
text of the message involves a code change, albeit a much smaller
On 11/25/19 11:01 AM, David Carlson wrote:
> If I understand, Derek, you are proposing a change to GnuCash code to
> improve it's behavior.
>
> Going back to the original question, which was about the confusing wording
> of the warning, if the code is changed, should there be warnings tailored
> to
If I understand, Derek, you are proposing a change to GnuCash code to
improve it's behavior.
Going back to the original question, which was about the confusing wording
of the warning, if the code is changed, should there be warnings tailored
to each of the three cases?
Note: Case 1 might mean tha
Adrien Monteleone writes:
>> Again, if user A has a data file open, user B shouldn't also open
>> the file. I don't see how a check for Gnucash instances could work
>> to prevent precisely this problem, since my machine won't have any
>> Gnucash instances running--but the file IS being used.
>
>
I think PART of this problem is confusion about "another user". Remember
that need not be another human being. YOU perhaps have more than one log
in << say one with administrator rights and then a another for regular
use >>
Rather than "in use" the terminology MIGHT be "checked out but not yet
Clearly, I am in the minority here. I'll drop out of this conversation now.
David T.
On November 18, 2019, at 10:26 PM, Stan Brown
wrote:
On 2019-11-18 08:56, D wrote:
> Adding to the error message to account for when the software crashes
> seems like overkill (as does linking to the documen
On Monday, 18 November 2019 16:51:14 GMT Adrien Monteleone wrote:
> I agree, using the PID won’t work, because although GnuCash is not (yet) a
> multi-user app, some people do use it from various machines with the file
> stored on a network. A PID check won’t mean anything to one machine when
> th
On 2019-11-18 08:56, D wrote:
> Adding to the error message to account for when the software crashes
> seems like overkill (as does linking to the documentation from a
> dialog, BTW). The topic is covered both in the wiki and in the
> Tutorial, and a quick check online or in the documentation sho
> On Nov 18, 2019 w47d322, at 9:17 AM, D via gnucash-user
> wrote:
>
>
>
> On November 18, 2019, at 8:02 PM, Derek Atkins wrote:
>
>> Hi,
>> I think I have a suggestion for some better wording. See below.
>> How about:
>> The data file is currently in use. Most likely this means that the
David,
On Mon, November 18, 2019 10:27 am, David Carlson wrote:
> I like Derek 's suggestion but I would see that and call with this
> suggestion:
>
> There is a lock on the selected data file. Most likely this means that
> the data file was not cleanly closed (due to a crash) after it was last
On Mon, Nov 18, 2019 at 10:01 AM Frank H. Ellenberger <
frank.h.ellenber...@gmail.com> wrote:
> Am Mo., 18. Nov. 2019 um 16:28 Uhr schrieb David Carlson
> :
> >
> > I like Derek 's suggestion but I would see that and call with this
> suggestion:
> >
> > There is a lock on the selected data file.
On November 18, 2019, at 9:12 PM, Colin Law wrote:
>Perhaps a message saying "Error 5135 if you don't understand what this
>means then you should have read the wiki" would be a solution.
>Colin
Certainly, it could be. But it wouldn't be a good one, and I think you should
know I wasn't sugges
Am Mo., 18. Nov. 2019 um 16:28 Uhr schrieb David Carlson
:
>
> I like Derek 's suggestion but I would see that and call with this
> suggestion:
>
> There is a lock on the selected data file. Most likely this means that the
> data file was not cleanly closed (due to a crash) after it was last o
On Mon, 18 Nov 2019 at 13:59, D via gnucash-user
wrote:
> ...
> Remember that the lock file and this check exist firstly to prevent multiple
> users from opening the file at one time--and that is still a possibility.
That may be reason for the test but it is not the most common cause.
In fact ar
I like Derek 's suggestion but I would see that and call with this
suggestion:
There is a lock on the selected data file. Most likely this means that
the data file was not cleanly closed (due to a crash) after it was last
opened.
If you are sure that it is not currently in use by you or another
On November 18, 2019, at 8:02 PM, Derek Atkins wrote:
>Hi,
>I think I have a suggestion for some better wording. See below.
>How about:
>The data file is currently in use. Most likely this means that the data
>file was not cleanly closed (due to a crash) after it was last opened.
>If you are
Hi,
I think I have a suggestion for some better wording. See below.
David Carlson writes:
> I think a better and more accurate wording would be "The data file has not
> been cleanly closed since it was last opened. If you are sure that it was
> not opened by another user, click 'Open Anyway'.
I don't really agree. David's wording identifies one situation for this dialog,
and not even the primary reason for the lock file in the first place.
Remember that the lock file and this check exist firstly to prevent multiple
users from opening the file at one time--and that is still a possibi
I think David Carlson's suggestion is better than mine.
I had hoped to spark a discussion on this point, so I didn't expect my
version would be the final one. I'm delighted that it is being looked
at, and benefit to users will result.
--
Regards,
Stan Brown
Tompkins County, New York, USA
https:/
Is there a simple way to reword the warning to say that a lock file is
present thus some instance of GnuCash has either abandoned it or is not
finished working with the data. If you are sure that it was *not* opened
by another user or still opened by yourself on another screen or computer
click
Except that the file was closed immediately after completing the session load.
GnuCash will rename it and write a new one if you have made changes to the book
in memory and tell it to save those changes or let it auto-save, but you can
certainly close the session and so delete the lock file with
Am Mo., 18. Nov. 2019 um 01:24 Uhr schrieb David Carlson
:
:
There are a few other reasons, where I already have run in:
> "The data file has not been cleanly closed since it was last opened. If you
> are sure that it was not opened by another user, click 'Open Anyway'.
> Otherwise click one o
A comment about Stan Brown's suggestion.
I think a better and more accurate wording would be "The data file has not
been cleanly closed since it was last opened. If you are sure that it was
not opened by another user, click 'Open Anyway'. Otherwise click one of
the other options."
To me the imp
Hello Stan et al.
I like the idea. A short grep delivers 5 occurrences of likewise texts: 4 at
https://github.com/Gnucash/gnucash/blob/de09259f13e8e3d7f2e50f97a353bd22eb45a4b6/gnucash/gnome-utils/gnc-file.c#L276
and one further below:
https://github.com/Gnucash/gnucash/blob/de09259f13e8e3d7f2e50f9
On 16 November 2019 at 19:17, Kay Robinson said:
> Hi
>
> Whilst gnucash was minimised on my toolbar I had a short power outage.
> When I re-booted the system I couldn't open my accounts because 'another
> user was using them' I chose to open anyway, but couldn't save a change I
> made.
What do
In the two years I've been reading this list, I think the single most
common question has been about this "could not obtain the lock" message.
Seems like someone asks about it at least once a week.
The text "that database may be in use by another user," while literally
true, isn't helpful because
Kay,
If you happened to use the Open Read-Only option instead of the Open Anyway
option, you will not be able to use the Save option but will have to Save
As a different filename. If you do use the Open Anyway option you should
be able to Save the file with the same filename.
David Carlson
On S
Kay
If GnuCash is not closed properly,e.g. a crash the .LNK and .LCK files
created in your data directory prevent you from opening GnuCash. Section
2.5.3 of the Tutorial guide covers them.
2.5.3. Lock files (.LNK and .LCK)
You may occasionally see .LNK and .LCK files appear. These do not store an
Hi
Whilst gnucash was minimised on my toolbar I had a short power outage.
When I re-booted the system I couldn't open my accounts because 'another
user was using them' I chose to open anyway, but couldn't save a change
I made. The help menu tutorial tells me I can do that but use another
name
30 matches
Mail list logo
