nissy-core/shell/shell.c, branch python-callback The "engine" of nissy, including the H48 optimal solver. https://git.tronto.net/nissy-core/atom?h=python-callback 2025-08-07T13:28:01Z Added API function for solution variations 2025-08-07T13:28:01Z Sebastiano Tronto sebastiano@tronto.net 2025-08-07T13:09:46Z urn:sha1:5355de2921126e2b75e24abd57e17556e22a6ed0 Added move sequence comparison function 2025-07-31T07:47:57Z Sebastiano Tronto sebastiano@tronto.net 2025-07-31T07:47:57Z urn:sha1:992de12cc081e7dde16c3c231f83bfa77c67825a Fix shell return value on solverinfo 2025-07-18T15:04:53Z Sebastiano Tronto sebastiano@tronto.net 2025-07-18T15:04:53Z urn:sha1:a36edab98434100422550d7271e54a723350ee38 Added stop / pause / resume solve to API 2025-04-29T08:08:04Z Sebastiano Tronto sebastiano@tronto.net 2025-04-29T08:08:04Z urn:sha1:8d3fc9f5f9c0593fcae9c451efe6c89c64dcbe84 Added orientation to getcube 2025-04-23T13:42:11Z Sebastiano Tronto sebastiano@tronto.net 2025-04-23T13:42:11Z urn:sha1:9c209afd81e4c51e4fc2717c0eeff4a5d116bcb0 Remove compose from the public API 2025-04-22T12:47:25Z Sebastiano Tronto sebastiano@tronto.net 2025-04-22T12:47:25Z urn:sha1:93522effba2f200257141189de5925a23fca93b8 Removed old scripts and updated public API 2025-04-22T07:00:15Z Sebastiano Tronto sebastiano@tronto.net 2025-04-22T07:00:15Z urn:sha1:8b72e391c7185e3da0dfbf0ab60068ac37e4d5cc Always use unsigned char * for data buffers 2025-04-21T12:44:07Z Sebastiano Tronto sebastiano@tronto.net 2025-04-21T12:33:01Z urn:sha1:510a7471348788fccba6b7c4b9f7b7cc9aee6ba9 Before this commit I was inconsistently using one of void *, char * and uint8_t *. Fixed shell usage of optimal and maxsolutions 2025-04-19T09:18:12Z Sebastiano Tronto sebastiano@tronto.net 2025-04-19T09:18:12Z urn:sha1:691da8f06614418ed847bdeefa4e708c372a3ecf Small rework of optimal vs maxsols 2025-04-17T12:36:27Z Sebastiano Tronto sebastiano@tronto.net 2025-04-17T08:50:57Z urn:sha1:0ece4b72db22139db51e8f5f37c25f24c84f3e43 I wanted to make the "optimal" and "maxsolutions" options mutually exclusive, but in the end I decided there is value in keeping both (e.g. for specifying a limit to the number of solutions when asking for "all" optimal"). Now optimal cannot be negative anymore, for the same reason of maxsolutions. The interface user (shell, UI) will have to take care of handling this in a way that makes sense for the user. Usually this means setting the maximum number of solutions to UINT_MAX (or a similar very high number) when the user wants "all optimal".