Re: [GNC] Editing Scheduled Transaction

2018-05-19 Thread Robin Chattopadhyay
Dave-

I experimented a bit more based on your findings.

Additional steps to recreate:

Create new SX; close GnuCash; re-open GnuCash. Edit SX template transaction.

I tried:
*Create SX; edit template. Editing allowed
*Create SX; Run SX; edit template. Editing allowed
*Create SX; Run SX; Close/re-open Gnucash. Editing NOT allowed
*Create SX; Close/re-open Gnucash. Editing NOT allowed

Robin

On Fri, May 18, 2018 at 5:42 PM DaveC49  wrote:

> Robin,
>
> I'm also using 3.1 on Mint 18.3. I have tried to duplicate your problem
> without being able to. I am able to edit the fields in the template
> transaction without any diffculty and I don't receive that error message at
> all. I can create 2 scheduled transactions and edit them both at the same
> time. If I try and edit an already open for editing transaction again it
> just brings the open window to the front.
>
> That message seems to indicate that you may have an instance of that
> scheduled transaction open editing in one of the account register windows
> that the scheduled transaction creates entries for at the same time as you
> are editing the scheduled transaction in the. That would likely cause a
> conflict as you could be changing the values in two places simultaneously.
>
> David
>
>
>
>
>
> -
> David Cousens
> --
> Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.


Re: [GNC] Editing Scheduled Transaction

2018-05-18 Thread DaveC49
Robin,

I'm also using 3.1 on Mint 18.3. I have tried to duplicate your problem
without being able to. I am able to edit the fields in the template
transaction without any diffculty and I don't receive that error message at
all. I can create 2 scheduled transactions and edit them both at the same
time. If I try and edit an already open for editing transaction again it
just brings the open window to the front.

That message seems to indicate that you may have an instance of that
scheduled transaction open editing in one of the account register windows
that the scheduled transaction creates entries for at the same time as you
are editing the scheduled transaction in the. That would likely cause a
conflict as you could be changing the values in two places simultaneously.

David





-
David Cousens
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.


Re: [GNC] Editing Scheduled Transaction

2018-05-18 Thread Robin Chattopadhyay
Ah, sorry about that. It was clocking so long after I clicked submit the
first time that I thought I had done something wrong.

Robin

On Fri, May 18, 2018 at 4:45 PM John Ralls  wrote:

> It's actually https://bugzilla.gnome.org/show_bug.cgi?id=796248. You seem
> to have hit "submit" twice somehow and made two, and I've closed the second
> one.
>
> Regards,
> John Ralls
>
>
> > On May 18, 2018, at 2:38 PM, Robin Chattopadhyay 
> wrote:
> >
> > Done. Thanks.
> >
> > https://bugzilla.gnome.org/show_bug.cgi?id=796249
> >
> >
> > On Fri, May 18, 2018 at 7:32 AM Geert Janssens <
> geert.gnuc...@kobaltwit.be>
> > wrote:
> >
> >> Please report this as a bug in bugzilla. It risks getting lost on a
> >> mailing
> >> list.
> >> Refer to http://wiki.gnucash.org/wiki/Bugzilla to learn how to use
> >> bugzilla
> >>
> >> Thanks,
> >>
> >> Geert
> >>
> >> Op vrijdag 18 mei 2018 14:19:27 CEST schreef Robin Chattopadhyay:
> >>> On Thu, May 17, 2018 at 9:29 PM Adrien Monteleone <
> >>>
> >>> adrien.montele...@lusfiber.net> wrote:
>  You said the work around is to delete and re-add, but does the re-add
> >> not
>  generate the same error? Is this only when editing a previously
> defined
>  SX?
> >>>
> >>> Correct. Only when editing an existing transaction in an existing SX.
> >>> Doesn't happen when adding a new transaction in an existing SX or when
> >>> adding a new SX.
> >>>
> >>> I’ll admit I’ve only seen this error when actually trying to edit a
> real
> >>>
>  transaction in one account register when I was already “in” the same
>  transaction in another related account register. (usually after a
> >> ‘jump’
>  menu instruction) I’ve never seen it in the SX editor.
> >>>
> >>> Same here.
> >>>
>  Dealing with scheduled transactions in concert with this is a bit
>  perplexing, other than to suggest, as a test to narrow down the cause,
>  close everything but the Chart of Accounts, THEN open the Scheduled
>  Transaction editor and see if the same error occurs.
> >>>
> >>> No change.
> >>>
>  At least, you’ve eliminated (or confirmed) other open accounts as the
>  possibilities or causes.
> 
>  Also, please report if you are using the XML or one of the SQL
> backends
>  just to clear that up. (should there be a discrepancy)
> >>>
> >>> SQLite
> >>>
>  For myself, all of my scheduled transactions are still working as
>  expected, but all of them pre-existed my transition from 2.6 to 3.1.
> >> I’ve
>  yet to create a new SX from the 3.x series and to see how it behaves.
> I
>  also haven’t yet had a need to edit any of them.
> 
>  Regards,
>  Adrien
> 
> > On May 17, 2018, at 9:02 PM, Robin Chattopadhyay <
> >> robinra...@gmail.com>
> 
>  wrote:
> > Hi-
> >
> > Using GC 3.1 on Mint 18.3.
> >
> > I've come across something that seems like a bug, but I thought I
> >> would
> > check here first because I didn't see an open bug already.
> >
> > Under Edit Scheduled Transaction, click Template Transaction,
> >> attempt to
> > edit a value in any field of the transaction then move focus to
> >> another
> > line throws an error: "This transaction is already being edited in
> 
>  another
> 
> > register. Please finish editing it there first."
> >
> > Since it's a scheduled transaction, it seems illogical for the
> 
>  transaction
> 
> > to be in another register.
> >
> > The workaround is to delete the transaction from the SX editor window
> > and
> > re-add it, but this is not ideal because many of my SXs have multiple
> > transactions in a particular order.
> >
> > Thanks,
> > Robin
> > ___
> > gnucash-user mailing list
> > gnucash-user@gnucash.org
> > To update your subscription preferences or to unsubscribe:
> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> > If you are using Nabble or Gmane, please see
> 
>  https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> 
> > -
> > Please remember to CC this list on all your replies.
> > You can do this by using Reply-To-List or Reply-All.
> 
>  ___
>  gnucash-user mailing list
>  gnucash-user@gnucash.org
>  To update your subscription preferences or to unsubscribe:
>  https://lists.gnucash.org/mailman/listinfo/gnucash-user
>  If you are using Nabble or Gmane, please see
>  https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
>  -
>  Please remember to CC this list on all your replies.
>  You can do this by using Reply-To-List or Reply-All.
> >>>
> >>> ___
> >>> gnucash-user mailing list
> >>> gnucash-user@gnucash.org
> >>> To update your subscription preferences or 

Re: [GNC] Editing Scheduled Transaction

2018-05-18 Thread John Ralls
It's actually https://bugzilla.gnome.org/show_bug.cgi?id=796248. You seem to 
have hit "submit" twice somehow and made two, and I've closed the second one.

Regards,
John Ralls


> On May 18, 2018, at 2:38 PM, Robin Chattopadhyay  wrote:
> 
> Done. Thanks.
> 
> https://bugzilla.gnome.org/show_bug.cgi?id=796249
> 
> 
> On Fri, May 18, 2018 at 7:32 AM Geert Janssens 
> wrote:
> 
>> Please report this as a bug in bugzilla. It risks getting lost on a
>> mailing
>> list.
>> Refer to http://wiki.gnucash.org/wiki/Bugzilla to learn how to use
>> bugzilla
>> 
>> Thanks,
>> 
>> Geert
>> 
>> Op vrijdag 18 mei 2018 14:19:27 CEST schreef Robin Chattopadhyay:
>>> On Thu, May 17, 2018 at 9:29 PM Adrien Monteleone <
>>> 
>>> adrien.montele...@lusfiber.net> wrote:
 You said the work around is to delete and re-add, but does the re-add
>> not
 generate the same error? Is this only when editing a previously defined
 SX?
>>> 
>>> Correct. Only when editing an existing transaction in an existing SX.
>>> Doesn't happen when adding a new transaction in an existing SX or when
>>> adding a new SX.
>>> 
>>> I’ll admit I’ve only seen this error when actually trying to edit a real
>>> 
 transaction in one account register when I was already “in” the same
 transaction in another related account register. (usually after a
>> ‘jump’
 menu instruction) I’ve never seen it in the SX editor.
>>> 
>>> Same here.
>>> 
 Dealing with scheduled transactions in concert with this is a bit
 perplexing, other than to suggest, as a test to narrow down the cause,
 close everything but the Chart of Accounts, THEN open the Scheduled
 Transaction editor and see if the same error occurs.
>>> 
>>> No change.
>>> 
 At least, you’ve eliminated (or confirmed) other open accounts as the
 possibilities or causes.
 
 Also, please report if you are using the XML or one of the SQL backends
 just to clear that up. (should there be a discrepancy)
>>> 
>>> SQLite
>>> 
 For myself, all of my scheduled transactions are still working as
 expected, but all of them pre-existed my transition from 2.6 to 3.1.
>> I’ve
 yet to create a new SX from the 3.x series and to see how it behaves. I
 also haven’t yet had a need to edit any of them.
 
 Regards,
 Adrien
 
> On May 17, 2018, at 9:02 PM, Robin Chattopadhyay <
>> robinra...@gmail.com>
 
 wrote:
> Hi-
> 
> Using GC 3.1 on Mint 18.3.
> 
> I've come across something that seems like a bug, but I thought I
>> would
> check here first because I didn't see an open bug already.
> 
> Under Edit Scheduled Transaction, click Template Transaction,
>> attempt to
> edit a value in any field of the transaction then move focus to
>> another
> line throws an error: "This transaction is already being edited in
 
 another
 
> register. Please finish editing it there first."
> 
> Since it's a scheduled transaction, it seems illogical for the
 
 transaction
 
> to be in another register.
> 
> The workaround is to delete the transaction from the SX editor window
> and
> re-add it, but this is not ideal because many of my SXs have multiple
> transactions in a particular order.
> 
> Thanks,
> Robin
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see
 
 https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
 
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
 
 ___
 gnucash-user mailing list
 gnucash-user@gnucash.org
 To update your subscription preferences or to unsubscribe:
 https://lists.gnucash.org/mailman/listinfo/gnucash-user
 If you are using Nabble or Gmane, please see
 https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
 -
 Please remember to CC this list on all your replies.
 You can do this by using Reply-To-List or Reply-All.
>>> 
>>> ___
>>> gnucash-user mailing list
>>> gnucash-user@gnucash.org
>>> To update your subscription preferences or to unsubscribe:
>>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>>> If you are using Nabble or Gmane, please see
>>> https://wiki.gnucash.org/wiki/Mailing_Lists for more information. -
>>> Please remember to CC this list on all your replies.
>>> You can do this by using Reply-To-List or Reply-All.
>> 
>> 
>> 
>> 
>> 
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update 

Re: [GNC] Editing Scheduled Transaction

2018-05-18 Thread Robin Chattopadhyay
Done. Thanks.

https://bugzilla.gnome.org/show_bug.cgi?id=796249


On Fri, May 18, 2018 at 7:32 AM Geert Janssens 
wrote:

> Please report this as a bug in bugzilla. It risks getting lost on a
> mailing
> list.
> Refer to http://wiki.gnucash.org/wiki/Bugzilla to learn how to use
> bugzilla
>
> Thanks,
>
> Geert
>
> Op vrijdag 18 mei 2018 14:19:27 CEST schreef Robin Chattopadhyay:
> > On Thu, May 17, 2018 at 9:29 PM Adrien Monteleone <
> >
> > adrien.montele...@lusfiber.net> wrote:
> > > You said the work around is to delete and re-add, but does the re-add
> not
> > > generate the same error? Is this only when editing a previously defined
> > > SX?
> >
> > Correct. Only when editing an existing transaction in an existing SX.
> > Doesn't happen when adding a new transaction in an existing SX or when
> > adding a new SX.
> >
> > I’ll admit I’ve only seen this error when actually trying to edit a real
> >
> > > transaction in one account register when I was already “in” the same
> > > transaction in another related account register. (usually after a
> ‘jump’
> > > menu instruction) I’ve never seen it in the SX editor.
> >
> > Same here.
> >
> > > Dealing with scheduled transactions in concert with this is a bit
> > > perplexing, other than to suggest, as a test to narrow down the cause,
> > > close everything but the Chart of Accounts, THEN open the Scheduled
> > > Transaction editor and see if the same error occurs.
> >
> > No change.
> >
> > > At least, you’ve eliminated (or confirmed) other open accounts as the
> > > possibilities or causes.
> > >
> > > Also, please report if you are using the XML or one of the SQL backends
> > > just to clear that up. (should there be a discrepancy)
> >
> > SQLite
> >
> > > For myself, all of my scheduled transactions are still working as
> > > expected, but all of them pre-existed my transition from 2.6 to 3.1.
> I’ve
> > > yet to create a new SX from the 3.x series and to see how it behaves. I
> > > also haven’t yet had a need to edit any of them.
> > >
> > > Regards,
> > > Adrien
> > >
> > > > On May 17, 2018, at 9:02 PM, Robin Chattopadhyay <
> robinra...@gmail.com>
> > >
> > > wrote:
> > > > Hi-
> > > >
> > > > Using GC 3.1 on Mint 18.3.
> > > >
> > > > I've come across something that seems like a bug, but I thought I
> would
> > > > check here first because I didn't see an open bug already.
> > > >
> > > > Under Edit Scheduled Transaction, click Template Transaction,
> attempt to
> > > > edit a value in any field of the transaction then move focus to
> another
> > > > line throws an error: "This transaction is already being edited in
> > >
> > > another
> > >
> > > > register. Please finish editing it there first."
> > > >
> > > > Since it's a scheduled transaction, it seems illogical for the
> > >
> > > transaction
> > >
> > > > to be in another register.
> > > >
> > > > The workaround is to delete the transaction from the SX editor window
> > > > and
> > > > re-add it, but this is not ideal because many of my SXs have multiple
> > > > transactions in a particular order.
> > > >
> > > > Thanks,
> > > > Robin
> > > > ___
> > > > gnucash-user mailing list
> > > > gnucash-user@gnucash.org
> > > > To update your subscription preferences or to unsubscribe:
> > > > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> > > > If you are using Nabble or Gmane, please see
> > >
> > > https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> > >
> > > > -
> > > > Please remember to CC this list on all your replies.
> > > > You can do this by using Reply-To-List or Reply-All.
> > >
> > > ___
> > > gnucash-user mailing list
> > > gnucash-user@gnucash.org
> > > To update your subscription preferences or to unsubscribe:
> > > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> > > If you are using Nabble or Gmane, please see
> > > https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> > > -
> > > Please remember to CC this list on all your replies.
> > > You can do this by using Reply-To-List or Reply-All.
> >
> > ___
> > gnucash-user mailing list
> > gnucash-user@gnucash.org
> > To update your subscription preferences or to unsubscribe:
> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> > If you are using Nabble or Gmane, please see
> > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. -
> > Please remember to CC this list on all your replies.
> > You can do this by using Reply-To-List or Reply-All.
>
>
>
>
>
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember 

Re: [GNC] Editing Scheduled Transaction

2018-05-18 Thread Geert Janssens
Please report this as a bug in bugzilla. It risks getting lost on a mailing 
list.
Refer to http://wiki.gnucash.org/wiki/Bugzilla to learn how to use bugzilla

Thanks,

Geert

Op vrijdag 18 mei 2018 14:19:27 CEST schreef Robin Chattopadhyay:
> On Thu, May 17, 2018 at 9:29 PM Adrien Monteleone <
> 
> adrien.montele...@lusfiber.net> wrote:
> > You said the work around is to delete and re-add, but does the re-add not
> > generate the same error? Is this only when editing a previously defined
> > SX?
> 
> Correct. Only when editing an existing transaction in an existing SX.
> Doesn't happen when adding a new transaction in an existing SX or when
> adding a new SX.
> 
> I’ll admit I’ve only seen this error when actually trying to edit a real
> 
> > transaction in one account register when I was already “in” the same
> > transaction in another related account register. (usually after a ‘jump’
> > menu instruction) I’ve never seen it in the SX editor.
> 
> Same here.
> 
> > Dealing with scheduled transactions in concert with this is a bit
> > perplexing, other than to suggest, as a test to narrow down the cause,
> > close everything but the Chart of Accounts, THEN open the Scheduled
> > Transaction editor and see if the same error occurs.
> 
> No change.
> 
> > At least, you’ve eliminated (or confirmed) other open accounts as the
> > possibilities or causes.
> > 
> > Also, please report if you are using the XML or one of the SQL backends
> > just to clear that up. (should there be a discrepancy)
> 
> SQLite
> 
> > For myself, all of my scheduled transactions are still working as
> > expected, but all of them pre-existed my transition from 2.6 to 3.1. I’ve
> > yet to create a new SX from the 3.x series and to see how it behaves. I
> > also haven’t yet had a need to edit any of them.
> > 
> > Regards,
> > Adrien
> > 
> > > On May 17, 2018, at 9:02 PM, Robin Chattopadhyay 
> > 
> > wrote:
> > > Hi-
> > > 
> > > Using GC 3.1 on Mint 18.3.
> > > 
> > > I've come across something that seems like a bug, but I thought I would
> > > check here first because I didn't see an open bug already.
> > > 
> > > Under Edit Scheduled Transaction, click Template Transaction, attempt to
> > > edit a value in any field of the transaction then move focus to another
> > > line throws an error: "This transaction is already being edited in
> > 
> > another
> > 
> > > register. Please finish editing it there first."
> > > 
> > > Since it's a scheduled transaction, it seems illogical for the
> > 
> > transaction
> > 
> > > to be in another register.
> > > 
> > > The workaround is to delete the transaction from the SX editor window
> > > and
> > > re-add it, but this is not ideal because many of my SXs have multiple
> > > transactions in a particular order.
> > > 
> > > Thanks,
> > > Robin
> > > ___
> > > gnucash-user mailing list
> > > gnucash-user@gnucash.org
> > > To update your subscription preferences or to unsubscribe:
> > > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> > > If you are using Nabble or Gmane, please see
> > 
> > https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> > 
> > > -
> > > Please remember to CC this list on all your replies.
> > > You can do this by using Reply-To-List or Reply-All.
> > 
> > ___
> > gnucash-user mailing list
> > gnucash-user@gnucash.org
> > To update your subscription preferences or to unsubscribe:
> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> > If you are using Nabble or Gmane, please see
> > https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> > -
> > Please remember to CC this list on all your replies.
> > You can do this by using Reply-To-List or Reply-All.
> 
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information. -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.




___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] Editing Scheduled Transaction

2018-05-18 Thread Robin Chattopadhyay
On Thu, May 17, 2018 at 9:29 PM Adrien Monteleone <
adrien.montele...@lusfiber.net> wrote:

> You said the work around is to delete and re-add, but does the re-add not
> generate the same error? Is this only when editing a previously defined SX?
>

Correct. Only when editing an existing transaction in an existing SX.
Doesn't happen when adding a new transaction in an existing SX or when
adding a new SX.

I’ll admit I’ve only seen this error when actually trying to edit a real
> transaction in one account register when I was already “in” the same
> transaction in another related account register. (usually after a ‘jump’
> menu instruction) I’ve never seen it in the SX editor.
>

Same here.


> Dealing with scheduled transactions in concert with this is a bit
> perplexing, other than to suggest, as a test to narrow down the cause,
> close everything but the Chart of Accounts, THEN open the Scheduled
> Transaction editor and see if the same error occurs.
>

No change.


> At least, you’ve eliminated (or confirmed) other open accounts as the
> possibilities or causes.
>
> Also, please report if you are using the XML or one of the SQL backends
> just to clear that up. (should there be a discrepancy)
>

SQLite


> For myself, all of my scheduled transactions are still working as
> expected, but all of them pre-existed my transition from 2.6 to 3.1. I’ve
> yet to create a new SX from the 3.x series and to see how it behaves. I
> also haven’t yet had a need to edit any of them.
>
> Regards,
> Adrien
>
> > On May 17, 2018, at 9:02 PM, Robin Chattopadhyay 
> wrote:
> >
> > Hi-
> >
> > Using GC 3.1 on Mint 18.3.
> >
> > I've come across something that seems like a bug, but I thought I would
> > check here first because I didn't see an open bug already.
> >
> > Under Edit Scheduled Transaction, click Template Transaction, attempt to
> > edit a value in any field of the transaction then move focus to another
> > line throws an error: "This transaction is already being edited in
> another
> > register. Please finish editing it there first."
> >
> > Since it's a scheduled transaction, it seems illogical for the
> transaction
> > to be in another register.
> >
> > The workaround is to delete the transaction from the SX editor window and
> > re-add it, but this is not ideal because many of my SXs have multiple
> > transactions in a particular order.
> >
> > Thanks,
> > Robin
> > ___
> > gnucash-user mailing list
> > gnucash-user@gnucash.org
> > To update your subscription preferences or to unsubscribe:
> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> > If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> > -
> > Please remember to CC this list on all your replies.
> > You can do this by using Reply-To-List or Reply-All.
> >
>
>
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] Editing Scheduled Transaction

2018-05-17 Thread Adrien Monteleone
You said the work around is to delete and re-add, but does the re-add not 
generate the same error? Is this only when editing a previously defined SX?

I’ll admit I’ve only seen this error when actually trying to edit a real 
transaction in one account register when I was already “in” the same 
transaction in another related account register. (usually after a ‘jump’ menu 
instruction) I’ve never seen it in the SX editor.

Dealing with scheduled transactions in concert with this is a bit perplexing, 
other than to suggest, as a test to narrow down the cause, close everything but 
the Chart of Accounts, THEN open the Scheduled Transaction editor and see if 
the same error occurs.

At least, you’ve eliminated (or confirmed) other open accounts as the 
possibilities or causes.

Also, please report if you are using the XML or one of the SQL backends just to 
clear that up. (should there be a discrepancy)

For myself, all of my scheduled transactions are still working as expected, but 
all of them pre-existed my transition from 2.6 to 3.1. I’ve yet to create a new 
SX from the 3.x series and to see how it behaves. I also haven’t yet had a need 
to edit any of them.

Regards,
Adrien

> On May 17, 2018, at 9:02 PM, Robin Chattopadhyay  wrote:
> 
> Hi-
> 
> Using GC 3.1 on Mint 18.3.
> 
> I've come across something that seems like a bug, but I thought I would
> check here first because I didn't see an open bug already.
> 
> Under Edit Scheduled Transaction, click Template Transaction, attempt to
> edit a value in any field of the transaction then move focus to another
> line throws an error: "This transaction is already being edited in another
> register. Please finish editing it there first."
> 
> Since it's a scheduled transaction, it seems illogical for the transaction
> to be in another register.
> 
> The workaround is to delete the transaction from the SX editor window and
> re-add it, but this is not ideal because many of my SXs have multiple
> transactions in a particular order.
> 
> Thanks,
> Robin
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see 
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
> 


___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.