CHIRP

The issue with delete-and-shift of multiple rows is a valid point of confusion and/or a bug.

The behavior with the blank lines is a little more complex. The short answer is: this is working as designed. Meaning, the code is doing what I expect it to do, but clearly not you. The idea is that this is used to close gaps, and not necessarily shift the entire set of memories up.

It sounds like maybe there needs to be two options in there, one which does what it currently does, and another which will keep marching until the end of memory. I'm not sure how to succinctly denote that in a context menu, but I'll consider it.

Fair enough. To make sure we're on the same page regarding the "issue" I would point out that, in my opinion, the current behavior doesn't close gaps it "moves gaps." That is to say, if you had two 1-line gaps in your list before executing "Delete (and shift up)" you will have one 2-line gap afterwards.

I believe that shifting the entire set of memories (including blank lines) up is more flexible since you have "Insert row above" & "Insert row below" functions. I'm not sure in what scenario the current behavior is particularly desirable.

Regardless, it's your project and you're doing all the work so I'll feel content to make my opinion known and leave it at that. I'm enjoying CHIRP so please keep up the good work.

Thanks,
Sean

No complaints, I was just trying to explain that it was WAD :)

Check out today's build. There is another option for deleting now that does what you want. Let me know what you think.

I'm leaving this open until I figure out how I want to address the case where you do one of the complex delete operations with multiple memories selected.

Looks good.

I'd say that deleting multiple rows with the "Delete ...and shift all memories up" works "correctly."

Deleting multiple rows with "Delete ...and shift block up" still does nothing at all. I think it would be consistent if you made this operation move the block up and "create" as many blank lines below the block as you deleted above the block.

Sean

Well, it doesn't do "nothing" as noted in your original report here :)

In your original example, if I wanted to close the gap at 9 and put two memories in at 21,22 then I would need to use the block delete. I could solve that with cut/paste too, but the delete-and-shift function has been in chirp since before cut & paste :)

Anyway, thanks for the feedback. Glad to get another function for chirp out of the deal :)

Yes, the complex delete operations explicitly do nothing when multiple rows are selected. I'm leaving this bug open specifically to remind me to address that.

Glad we're on the same page now -- thanks!