Guidelines before posting an issue in ControlsFX

[samir.ha...@gmail.com]

1) Has the issue already been posted on this group or on the issue tracker?

2) Post your issue where you will be adding a SSCCE . The best is to add it with the code tag of Bitbucket. Then you know that someone who wants to help you will just have to copy/paste your code in its editor and click on "run".

If you do not provide a SSCCE, you have 99% of chance that your bug will not be looked, not be considered and will be closed.
Let me copy here what's on our home page :
ControlsFX is worked on by developers who have families and lives outside of coding. Whilst we enjoy working on open source projects, we can only do it when our personal time permits.

3) Can YOU resolve the issue? ControlsFX is based on a community. Everyone can work on it. So now that you have found a bug, why not trying to resolve it?
Maybe you won't find the solution, maybe you will find a wrong one, but at least you tried.

The bug will be resolved easily if you just put some code, some thoughts, hints, whatever.

4) You found the solution? Then don't stop here! Don't say "I've found the solution and I've fixed it in my code" .
What about the others? You can make a pull request! Just fork our code, modify it with your solution and make the pull request.

This is a community project, we are not a few privileged ones that can modify the code. Everyone can contribute.

So if you have posted some issues in our issue tracker, take the time to verify if you have respected all the points I've enumerated.