By "manually enter" I mean to trigger the entry into the register of the next scheduled instance of a single scheduled transaction [SX] without invoking the Since Last Run druid. I would expect that to be an action available in the SX editor.
Since one SX may contain more than one separate register transaction, I would expect the entire contents of the SX to be executed, including all the register transactions therein. I guess there would need to be some logic to detect that there were no pending edits, invalid arguments, to update the SX status and whatever to remain valid for the Since Last Run druid . On Thu, Jan 11, 2024 at 9:14 PM Adrien Monteleone < adrien.montele...@lusfiber.net> wrote: > What do you mean by "manually enter a SX?" > > Regards, > Adrien > > On 1/11/24 4:19 PM, David Carlson wrote: > > I think that we need to see how SX's will work after the Since Last Run > > druid is fixed before proposing more improvements. If I understand > > correctly, there is an unresolved issue preventing nightly builds, so it > > will be difficult to test anything right now anyway. > > > > As for balancing SX's, I often resort to entering each value on both > sides, > > using plus [or minus] signs instead of summing multiple values. > > > > A long time ago I submitted a feature request to provide the ability to > > manually enter a SX. I think that would help in some cases. > > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. > -- David Carlson _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
