if somebody wants a "C lang/linux level" bug/puzzle to figure out (could be as simple as looking at the source), I just discovered it a couple days ago: if you use a large number to set up a board in untangle, the algo is extremely slow to set the board up, probably an O(N*2) or worse or something. You can see this slowness in the web version, put in a 600 or 2000 the bug: anyway, I was running the C version of the p…
This sounds like an OS or kill bug not a with the program. Sending `kill -9`, aka `kill -KILL` is supposed to terminate the process immediately without giving it the opportunity to catch the signal and respond. (This is why you should start with `kill -TERM` and only resort to `kill -KILL` if that does not work.) So if the process is not terminated this is an OS or kill issue because the process itself is not given a…
Simon Tatham's Portable Puzzle Collection
41–50 of 52 posts
Re: Simon Tatham's Portable Puzzle Collection
#42Re: Simon Tatham's Portable Puzzle Collection
#43I love these puzzles. I find the cube rolling one just so hard to get my head around!
Re: Simon Tatham's Portable Puzzle Collection
#44Found this recently and have been loving it! The one that has stuck the most is Keen but Galaxies is a close second.
Re: Simon Tatham's Portable Puzzle Collection
#45Does anyone know of a collection of mini games like that with available source code, and preferably in a more approachable language than C? Thinking that something like this might be great for getting my 9-year interested in coding using a non-visual prog lang (so not Scratch).
Re: Simon Tatham's Portable Puzzle Collection
#46Earlier quoted context omitted.
Yeah, that's what I meant. On the other hand, something like Towers has you trying different configurations because there's not always enough information to motivate the next step.
I haven't tried Towers, but I had thought that every game in his collection was such that guessing was never required. The logic/rules might not always be obvious, but supposedly they are there.
Re: Simon Tatham's Portable Puzzle Collection
#47Given how many platforms these have been ported to, this really is the DOOM of puzzle apps. I've been using this PocketBook port on my e-reader for years: https://github.com/SteffenBauer/PocketPuzzles
Re: Simon Tatham's Portable Puzzle Collection
#48Earlier quoted context omitted.
This sounds like an OS or kill bug not a with the program. Sending `kill -9`, aka `kill -KILL` is supposed to terminate the process immediately without giving it the opportunity to catch the signal and respond. (This is why you should start with `kill -TERM` and only resort to `kill -KILL` if that does not work.) So if the process is not terminated this is an OS or kill issue because the process itself is not given a…
even if it's an OS or kill bug, most processes do reliably get killed with -9 so it's something that this program is doing is where to look/how to reproduce.
Re: Simon Tatham's Portable Puzzle Collection
#49The same puzzles can be played here with a more friendly UI: https://medmunds.github.io/puzzles/
not exactly the same, the ux cleanup has dumbed some of them down a bit I play the original untangle on 600 or higher, that "friendly" UI doesn't allow that I play the original Dominosa 6-extreme but friendly doesn't offer that either, unless it's set them all to extreme the Net doesn't not allow custom sizes, and it's also broken the mouse buttons, it only allows rotation in one direction not going to look further i…
I've recently started working on an updated PWA port that works offline and on touch devices, mainly because the iOS app hasn't been updated in years. (If you hunt around you can probably locate the work in progress, but it's not ready for critics yet. I'll post a link when it is.)
Re: Simon Tatham's Portable Puzzle Collection
#50Earlier quoted context omitted.
even if it's an OS or kill bug, most processes do reliably get killed with -9 so it's something that this program is doing is where to look/how to reproduce.
It shouldn't matter what the program is doing or not, it's an OS (or kill) level bug. Even if you can make changes to the program so it doesn't happen, it's still an OS/kill level bug. The OS is supposed to terminate the process. A process is not supposed to be able to prevent the OS from doing that.
"shouldn't" hides the flaw in your thinking, it is happening, that's the bug, so shouldn't is out the window