Spinning Card

[Raincode]

Hi,

I would like to use your class in an open-source game. I am kind of inexperienced with licensing and I don't know what I have to do so I am allowed to use your code.

BTW, I would like to add you to my credits section, however, I am unsure about how to actually credit you.

Raincode

[eXpl0it3r]

It uses the same license as SFML does. As long as you don't claim you wrote that piece of code, mark modifications as sucg and keep the license with the source, you're covered.
Crediting is not necessary but usually welcome and can be done in anyway you want, e.g. stating his name and maybe add a link. But of course if Hapax has a special wish he might say it himself.

[Raincode]

Hi,

thanks for answering.

Does that mean I simply copy the license.txt from github into the game folder when I redistribute it?

Does this mean, that my game must run under the same license?

Raincode

[eXpl0it3r]

As far as I understand it, you only have to provide the license file when distributing the source code, so you won't even have to provide it, when you ship the binaries.
And no, you can pick nearly any license you want for your own source code.

[Raincode]

I think I understood it now.

I have one more question regarding the SpinningCard: In my game, I have a vector of Cards (a own class that kind of combines 2 spinning cards to get an actual card (front+back)). I want to use std::random_shuffle on it, but I get this error with VC++:

std::random_shuffle(field.begin(), field.end());

error C2582: 'operator =' function is unavailable in 'hx::Misc::SpinningCard'

As I understand it, the default Copy-Assignment-Operator is not there (and the compiler can't provide one).
I am really unsure about how this function

SpinningCard& SpinningCard::operator=(const SpinningCard&);

would have to look like. Also, do I need a copy-constructor, too?

I would be very happy if someone could help me out with that, or maybe give me some alternatives where I don't need to define these.

[Nexus]

Yes, your elements must support copy semantics (C++98) or at least move semantics (C++11) in order to be shuffled. That is, copy/move constructor and copy/move assignment operator must be accessible.

You're hijacking a project thread with basic C++ questions that are not even related to SFML... That's not nice. You should really have a look at a good C++ book, and ask programming-related questions on a different platform (e.g. StackOverflow).

Please don't pollute this thread further with off-topic discussions, let's focus on Spinning Card

[Hapax]

Hi, Raincode. I'm glad that you are interested in using this class. It's nice that it's useful

Licensing-wise, it just requires that you include the licence with the source code and that you don't claim to have created it (this class).
It doesn't require credit outside of the source code but, of course, any is extremely appreciated. That said, suggested possible ways to credit - if you do still choose to do so - would be a link to my github, a link to my profile on the SFML forum, my email (included in the licence), or just Hapax or Hapaxia 

Spinning Card wasn't designed to be used as an actual object itself (that is copied, moved, compared, sorted etc.) but rather an animation object that temporarily replaces a standard sprite (the card) during the spin animation and then re-replaced by the sprite (the card - most likely, the other side). This way, if you only spin one card at a time, you only require one instance of SpinningCard, and it only needs to exist for the duration of the spin animation.

[eXpl0it3r]

Btw it should be called license.txt and not licence.txt.

[Raincode]

thanks for mentioning possible ways to credit. Additionally, thanks for the hint about the "correct" use of the class.

Maybe I can change my Code so it works the way you described, that way seems like it makes more sense.

Sorry for posting questions beforehand that were off-topic, it was wrong to do so.

[Hapax]

@Raincode
Don't worry too much about your questions. If I was clear about how the class worked, you wouldn't've needed to ask them (for this particular case) here.
I do have one request that I forgot to mention. If you do use this class, it would be great if you could 1) mention or link your project in this thread so that I can see how people found a use for it, and 2) "star" the repository on github. Thanks 

it should be called license.txt and not licence.txt.

I beg to differ 

[eXpl0it3r]

it should be called license.txt and not licence.txt.

I beg to differ 

Ah well, it's again an British vs American English issue.

[FRex]

Ah well, it's again an British vs American English issue.

The EU calls our driver permits "licence" in English texts (and Switzerland, despite not being a member, adopted some of the legislation of EU about driving licences and Swiss one has the word "licence" written on it too.. ) so I'd say it's the correct one for us Europeans...

[Hapax]

I succumb to using American English in code for consistencies (e.g. color) but find no real reason to use it for comments, documentation, filenames, etc..
Of course, one is allowed to use which ever version one prefers/feels more comfortable with so I won't complain if anyone uses something I don't