For all of the things that P-Suite does right....why do I continually find basic functions behaving in unreasonable, unpredictable ways?

I started a new project in 3.10.0 (17). As I am accustomed to doing, I began defining the UDS's that I was to use. I have a list of around 20 of them, some nested and others not. My next step was to create some tags of said UDS datatypes. I generated, non-consecutively, 13 different tags which instantiated anywhere from 1 to 37 copies of each UDS structure. To say that I am a fan of UDS is an understatement.

After the tags were created, my next step was to build out the task list as I find that having named tasks as a framework helps me to organize my thoughts as I begin to develop the ladder logic. I like to make things very modular when it comes to this so, in all, I created, individually, 38 different tasks.

Upon creating the 38th task, I realized that I had a spelling error in the task's name. I right-clicked on the task in the tree and accidentally clicked Delete instead of Rename Task. My mistake, surely. And what did I do? Instinctually, without ANY shred of doubt of what I was about to do, performed a CTRL-Z shortcut.

To my great surprise, I noticed that my task did not, in fact, reappear in the tree. Luckily for me, I saw something disappear out of the corner of my eye. The UDS Definition dialog was still open and, with consternation, I realized that the last UDS that I had created, lets say roughly 50 actions ago, had disappeared from the dialog!

Now, besides the fact that I had performed a host of other actions since this UDS was defined, there was something else that just blows my mind about this. I use the flyout capabilities of the editor for my Apps, Tasks, and Instructions tabs while my UDS Definitions dialog is undocked (at this point I don't even want to know if that is a setting that can be changed). So I KNOW that the UDS Definitions dialog COULD NOT have had focus at the time I did the CTRL-Z because, firstly, clicking on the Tasks flyout removes focus from the UDS Definitions window and, secondly, a RIGHT-CLICK into the task list generates a context dialog that would put focus in the Tasks tree.

My final (maybe?) gripe about this situation is that HOW IS IT EVEN POSSIBLE to remove a UDS that has not only been nested into another UDS, but also have 6 instances of this UDS data type with 30 separate tags associated to it? I can't even make this happen when I TRY to intentionally delete a UDS. I get an error message telling me that it is referenced by other UDS's and cannot be deleted.

So, how is it then, that this can happen? Is it me? What did I do wrong?

I want, for many good reasons, to keep using this software. But it is becoming hard for me to justify it. I just can't for the life of me understand how some of these bugs make it past ANY amount of regression testing. Its free software, I know. But what good is to me for it to be free when I cant even trust that it will follow a command with the the expectation of predictable functionality?

This is UNACCPTABLE to me.