Spencer wrote:In the debugger, if you remove all of the panes from a ||| or ==, then delete one more, you consistently get a crash.
Thanks, I’ll look into it.
Spencer wrote:For all releases: if you remove all panes, there is no way to add any back. Changes are not saved after exiting pti.
Well, those are not bugs but come from the mere fact that the whole thing is incomplete. For the time being you can only add leaves to the tree.
Spencer wrote:However, in many ways our priorities are very different -- e.g. I'd prefer a stack trace instead of a link history, or memory i/o records instead of "hub" support.
I understand and agree with that. The reason why I chose to play with these things lately is simply that they didn’t require much effort on my part. The absolute long-term priority for me is still exact emulation, the second is full observability and controllability of the calculator state from the debugger. But I can’t work on these things as long as I can’t allocate bigger chunks of time for development, because that would leave us with ‘broken’ (impossible to release) builds for extended periods of time, and it would also make me lose my focus many times while working on it.
Spencer wrote:How about a source release?
I said this a couple of times: the code needs to be refactored from the grounds up to make certain extensions possible (like the proper support for high-end models). As soon as there are more people working on it, major cleanups will be practically impossible, and therefore I won’t release anything before reaching a stable core.
Spencer wrote:With any decent version control, changes from the 2-3 people that do code would not difficult to consolidate.
Just believe me that in the current state of the code this would lead to a lot of wasted effort. There are still so many fundamental modifications to make that any attempt at merging would be doomed to failure.