{"ops":[{"insert":"I was trying to move the maybeboard from a deck to another and realised I couldn't. I got the following error:\n"},{"attributes":{"blockquote":true},"insert":"\n"},{"insert":"No ID found"},{"attributes":{"blockquote":true},"insert":"\n\n"},{"insert":"We could not find any card IDs in that drop."},{"attributes":{"blockquote":true},"insert":"\n"},{"insert":"\nTrying to move a single card from a deck to another results in the same error. I can drag and drop cards from scryfall and EDHREC without any problem. I'm on version 157.0.1 (64 bits) of Mozilla Firefox.\n"}]}
0
{"ops":[{"insert":"Dragging and dropping between Archidekt windows was never intended to work due to the way that the internal drag and drop works. To put it simply, the way the internal dragging and dropping on the deck page (moving cards between categories) functions is fundementally incompatible with the OS level file dragging and dropping that the external drag and drop system uses (dragging cards in from other sites). When dragging on archidekt, you're dragging an internal object that has more texture (eg: the card's current categories, color tags, etc); when you're dragging from an external site, you're dragging a file around (just a URL to the card image).\n\nThe way the external drag and drop works is by checking the files URL, and grabbing a card from that. \n\nIn every browser that wasn't firefox, the dragging between Archidekt winows was never possible because when dragging internally it uses the internal drag and drop, superceeding the OS level drag and drop. I was actually unaware that users were doing this until a few days ago when firefox updated it's drag/drop eventing to be more inline with how other browsers handle it. \n\nSadly I looked into it, and yea I don't think there's really a fix here. What firefox has done has put their drag and drop behavior more inline with every other browser (eg: the internal drag and drop not dragging both the OS level object and the internal object) is far more performant, but I think that functionality may be lost.\n\nIt's possible if I redo internal drag and drop completely to use only the OS level drag and drop events that I could reimplement this functionality someday. But that'll mean rewriting drag and drop completely from the ground up.\n\nHere's the good news. Moving cards between decks on archidekt is easy even without drag and drop. There's an Add to other deck button on every card's details overlay, and you can use that functionality with multi-select as well if you're looking to save clicks.\n"}]}
1
{"ops":[{"insert":"Wow, I had no idea, I always saw this a cornerstone feature and was very surprised when it stopped working and assumed it was a network issue or other bug. I would go as far as to say it is an essential feature, I build so many decks by dragging and dropping from another deck or card package. It's going to be a lot more clunky using the add to another deck feature. Great program though, keep up the good work.\n"}]}
0
{"ops":[{"insert":"Thank you for your detailed answer! I had no idea how it worked behind the scene, it's very interesting.\n\nI didn't find the \"Add to other deck\" button while you have selection, but I just found it! Previously I opened the \"Edit\" windows instead of the three dots menu, where the option is found. :-) Thank you very much!\n"}]}
0