Discussion: Plan ordering, memory data, timing

[fosterlynn]

This is for discussion, the next label means let's just talk about it soon. I don't have systematic screen prints for this, but have some if needed. Yesterday when I started testing after the initial save, I started making changes to the first pickup column, which needs provider agents, more pickups, etc. I was also playing with the events and the finishing, which admittedly is getting ahead of the milestone.

I had weird behavior, which I didn't stop to document well at the time. Here's some of it, and I can bring back more if needed:

• As I started making changes, not making any effort to go slow, but also not going particularly fast, the last commitment (Gas and Truck) kept moving itself up, until it was at the top.
• I added one event to a primary commitment, maybe did something else after (?), it ended up with 2 events on the UI, and double the quantity. There is only one of them on the event page.

So, I'm wondering if we have an issue worth dealing with? Things that might be involved:

• How we are saving a change, and re-saving the column order at the same time, and using the timestamp to order (which field?)
• A lot seems to be going on in memory and/or in the saves sent to hREA async (as I understand but could be wrong) relative to what the screen shows.
• Sometimes the screen updates immediately, but sometimes it takes quite a while for the screen to update, wondering if it is waiting for the actual save to report back, or not. And sometimes one aspect will update, then another (like payment provider/receiver names) after several seconds, maybe first from memory then from save, or from iterations over the memory?
• This might be related Adding new commitment didn't work #156 ?

I don't know how much of this will not happen if the user waits after each update, but I suspect at least less of it.

[fosterlynn]

When I tried the edits again, I took it very slow, got much less weirdness. I can try to test more systematically at some point. And we'll see how it goes for the users as soon as they have a plan saved.