-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding stay with required strength #25
Comments
Test report
|
'required' is a special value, the weight factor isn't meaningful here. (Now we know what happens when the immovable object meets the unstoppable force, it appears the stay constraint wins. ;) ) |
If I got you right you are saying that the weight factor is the problem. Removing that from the unit test still yields the same output/error.
Result
|
The value remains 0 because the edit constraint is weaker than the stay constraint in this case. (Stays are weak and edits are strong by default.) |
Aha. It's details like this that would be awesome to have documented. This is quite good, but it too short IMO http://cassowary.readthedocs.org/en/latest/ |
For some reason, people started starring this project left and right in the past couple of days. Maybe this is a good time to get some documentation going. ;) That Python implementation you linked to explains the concepts of Cassowary very well, that's definitely a good basis. |
I'm not sure if this is a bug or not. I wrote some unit tests derived from the test
required_strength
which I expect to pass. Am I missing something?The text was updated successfully, but these errors were encountered: