In my experience the pasting-prevents-delete-key-action bug only affects the particular register in which the pasting occurred. And fixing the problem only requires closing that register and reopening it, not relaunching gnucash itself.
Also, while the delete key is impeded, you can select text and type corrections directly. You still can’t select text and delete it, so you’ll have to type at least one character to replace any mistakes until you close and reopen the register. The bug is fixed for 3.3, scheduled for release at the end of September. The team has been very good lately at hitting release dates. -- Dave Reiser dbrei...@icloud.com > On Aug 6, 2018, at 11:12 PM, Thomas Forrester <tlforres...@gmail.com> wrote: > > Well, in particular, what I mentioned in the original post: once you use > the clipboard to paste into a transaction, all further editing of that. or > apparently anything else is just not going to happen until you restart the > program. To me, that's about the biggest show-stopper I could ever > consider with *any* program - having to restart it all the time just to get > it working again. I should think this massive problem would have been > corrected almost immediately given the magnitude of the inconvenience it > causes, but it has been quite a while and I have no clue how long it will > take. > > If someone can tell me it's already been fixed and there is a 3.2.1 (or > whatever) release due any second now, great! I'll wait it out. But a few > more months till something happens, well, um... > > On Mon, Aug 6, 2018 at 11:18 AM Adrien Monteleone < > adrien.montele...@lusfiber.net> wrote: > >> You may not get a warning or alert! >> >> Also, yes, at the very least the date/time stamps are different and this >> is particularly an issue with the MySQL backend if I recall correctly. I >> wouldn’t attempt to step back any further than 2.6.21, but I’d ask, what in >> particular are you finding that you need to step back for? >> >> There were some early issues with data but those seem to have been solved >> by 3.2. (I’m using the sqlite3 backend, and had to switch to XML during the >> interim but am back to normal with the 3.2 release) Sure there are a few >> annoyances with the 3.x series so far, but those are being worked out. >> >> Regards, >> Adrien >> >>> On Aug 6, 2018, at 10:15 AM, Thomas Forrester <tlforres...@gmail.com> >> wrote: >>> >>> Thanks, Mike. >>> >>> So from what you are saying, there is some sort of data structures check >>> that would alert me if I am using a version of the program that is >>> incompatible with the data version. Checking my downloads, I find I have >>> the .21 installer which I wouldn't have unless I had installed that >>> version. So Looks like I may be good to take a step back. >>> >>> Maybe a corollary question then - although backward compatible with a >> .21 >>> database, does 3.x introduce any new changes to the data structures that >>> would make this a really bad idea? >>> >>> On Mon, Aug 6, 2018 at 9:26 AM Michael <mjchurc...@aol.com> wrote: >>> >>>> It is my understanding that 2.6.21 is the only 2.6.x that is compatible >>>> with the 3.2 data structure. I have used 2.6.21 successfully with 3.2 >>>> data, but older 2.6.x report that they are not compatible. I believe >> that >>>> is true of xml and sql databases. Mike >>>> >>>> On Mon, Aug 6, 2018 at 4:17 AM, Thomas Forrester <tlforres...@gmail.com >>> >>>> wrote: >>>> >>>> On a Windows computer, I upgraded to 3.2 from 2.6.20 I think it was back >>>> when I first noticed version 3 had been released. Took me till 3.2 to >>>> notice, but I think it was within a few days of the 3.2 release Having >> now >>>> used 3.2 for a short while, I'm wondering if there's any issue with >> going >>>> back to 2.6.x? In other words, are there any underlying data structure >>>> changes, or other file changes, that would make this a huge mistake? I >> am >>>> using the MySQL database backend. I just feel at this point that, if I >>>> can't further edit anything after pasting something in from the >> clipboard, >>>> that it may be a better idea to go back so I can go forward. >>>> _______________________________________________ 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. _______________________________________________ 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.
