Drag is a MOVE, not COPY, between recipe lists

[TomG]

Michael,

I have been a user for a few years and enjoy both the Mac and iPhone versions. I have convinced a couple of other people to use MacGourmet and they like it as well.

There is one behavior that I wish were different.

In the current form, when a recipe is dragged between recipe lists (playlists), the function is a MOVE, and not a COPY. In other words, the recipe is placed into the destination recipe list as desired, but the recipe is deleted from the source list. I would prefer that the recipe be placed in the destination, yet be preserved in the source list.

To actually COPY when dragging, the source must be My Recipes (the library) - then the copy function is non-detructive.

Obviously a recipe can fit into any number of different categories, but when dragging it among recipe lists, the move deletes it from the source so the recipe is lost from the original recipe list.

In my opinion, a recipe should only be removed from a recipe list when the user specifically deletes it. In this way there can be no confusion whether the drag performed a COPY or a MOVE.

Since MacGourmet uses the same functional paradigm as iTunes and iPhoto, so I would think that the basic behavior would be similar. In each of these apps, an item dragged between playlists/albums is a COPY, not a MOVE. It is retained in the source and copied into the destination.

I'm not sure what the consensus is among MacGourmet users, but I would prefer a non-destructive COPY and not a MOVE were the default behavior within MacGourmet as well.

Anybody else have an opinion?

Thanks for your consideration, and for your efforts on MacGourmet over the years.

Cheers, TomG