as it has been a while since i needed to use Fontbase, i am refamiliarising myself with FB use - AND problems i had before
now the latest problem i am discovering now (again?), is that drag n drop of font to Collectiopn MOVES it - does NOT copy it
why is this for am start?
second, how then do i COPY a font/s to one or more Collections?
kind regards
don
Thatās interesting, because I want to MOVE fonts into the collections, but they are always copied.
well, it definitely says āMoveā when you drag font, right?
(and of course the usual lack of any b*y support)
ok. i just test it all ā¦
and although it says āMoveā, it definitely COPIES
it ALWAYS copies, regardless, if from ALL or from another collection, or if you use Ctrl or not
so that is a bit of a pain really
so if you want to MOVE, it appears you have to do as a Copy by dragging into a Collection, and then a āRemoveā (by dragging out of a Collection to RH edge with its hidden Remove Panel)
Hello @dec, thank you for your post 
So it appears, given both of your messages here, you want to copy fonts into Collections and are able to do so as per the tutorials?
Thank you again,
Yuriy
FontBase Dev Team
No, Yuriy!
that is what the app does NOW - even though it says āMoveā
i actually want to be able to MOVE them; and i suspect that is what most users want to do most of the time, and is in fact what your app says - even if it doesnāt actually do that. 
as per previous Post, i would make the logical suggestion that you follow usual Windows convention and use the Ctrl key to copy both fonts and Collections
PS obviously all the fonts always stay in the global āAll Fontsā Folder
Thank you for your reply
I see, there must have been a type-o in the initial post then, thank you.
Thank you for the suggestion for the move/copy combination, I believe youāve expressed it quite few times over the recent weeks in this forum in multiple discussions. We will take this into account during future development for sure.
Thank you again,
Yuriy.
this should definitely moved to āGreen Lightā or whatever as a high priority; but in fact, it is a BUG fix!
and your own app agrees!
because your own app says āMOVEā, but copies instead.
and right there you would have a definitive ābugā
Thank you for your reply, glad we at least resolved the āCOPYā question in the initial post
I do understand your view on the matter, but, without getting into technicalities and linguistics, personally I do not this is a bug. You have the complete right to consider it a bug if youād like of course.
Thank you for the suggestion, Iāll add this to the Greenlight category for sure. The priority is decided based on the app development plan as well as general community feedback, i.e. higher priority is usually awarded to features requested by a considerable part of the community. Sadly we are not always able to add/change features based on every single request right away due to certain limitations of the development process 
Hope this helps,
short point, Yuriy, if a function SAY āMoveā, but actually COPIES, that is a bug by any definition.
now, the quick and easy fix for YOU, is just to change the label so it says āCopyā; but of course, for me and other users, that is not a proper fix - the real fix would change the function so that it does as it says - MOVES.
Thank you for the quick reply
Thank you again for voicing your view on the topic at hand. Move not Copy was chosen, I believe, not to confuse users as to the number of physical font copies on their hard drives. Up until now, for the last several years, we havenāt had any complaints on the wording, given the thousands or even tens of thousands of FontBase users. I understand your view on the matter is different, as youāve expressed it repeatedly in our recent communication. Thank you again for fighting for the rights of other users, not just yourself, even though they donāt seem to have any strong opinions on the matter.
Thank you again for your activity and dedication,