bug report - when slice is locked on 4.1.5 smartSDR, memory channels change mode split tx/rx mode

Hi,

when I have my slice locked, I found if I accidentally hit a memory channel from another mode, for example, I am on 40 meters LSB, and I touch 6 meters USB memory, it will change my mode to USB on tx all the time, and sometimes the rx will change to USB, sometimes it will stay on LSB, resulting in a "split" operation between rx of LSB and tx on USB. the latter is harder to replicate, but the shift to USB tx happens every time. I would think locking the slice should prevent this? I assume it will also change between FM, AM, etc. but I haven't tried it.

This was causing some of my earlier ticketed issues causing confusion of what I thought was "split operation" but may have just been wrong tx mode of operation, compared to the selected RX mode of operation. I classify this as a bug because I can't think of any use case to tx on LSB, and RX on USB for example.

photo shows tx in usb, rx in LSB. see the filter pattern and flag.

below is a video how to reproduce it.

you will need

a memory channel on 10 meters USB.

a memory channel on 6 meters USB.

a slice beginning on LSB, Locked on 40 meters.

not sure why the two memory channels interact the way they do, but watch the video.

UPDATE: here is how it is 100 percent repeatable for me:

1. put on 40 meters and lock slice in LSB.
2. click on 6 meters USB memory channel, and the mode will swap to USB in tx and RX.
3. click on 10 meters USB channel, and the mode will change to LSB for rx, and USB for TX (split)
4. rx will be LSB, tx will be USB.

wI can see where it was a form of operator error to touch a memory while locked, but I can see lots of use cases where it can happen, using 2 slices for example. I was editing the memory list, adding names and found this problem.

thanks, MN