Title: Bug: Newton-Raphson not working correctly Post by: Pauldelbrot on August 09, 2016, 08:58:52 PM Quite reproducible at this location.
Re: -0.743189435094232865061500555556185 Im: 0.109415945466685695602317222252745 Zoom to 1e13 and there's a minibrot near-centered in the view. Control-D and click in the cardioid of the mini. The period is detected as 1760 and then KF incorrectly gives an error message instead of centering itself exactly on the mini. It claims to not be zoomed close enough to the mini, as if you were less than half-way down to it, even if you zoom enough to nearly fill the screen with the mini's cardioid. This is clearly not correct. Interestingly, zooming out, to 8e8, seems to result in it working. At best the message claiming it needs to be zoomed in closer is misleading. But it should converge if the minibrot center is on the screen and it's zoomed far enough for that minibrot's atom domain to fill the screen, to say nothing of the minibrot itself doing so. More is going wrong if it has trouble converging from point-blank range. Title: Re: Bug: Newton-Raphson not working correctly Post by: Pauldelbrot on August 09, 2016, 09:03:10 PM Oh, and a side note: KF has an unfortunate bug in common with UF, which is that ctrl+A does not seem to work correctly in text input fields, such as the Re and Im fields. Ctrl+A in a text control should have the effect of "select all", but KF dings and doesn't alter the selection, and UF actually freaks out, doing unexpected things like opening new windows or dialog boxes when you attempt to select a number to copy (e.g. back and forth between the two apps). Obviously there's nothing you can do about UF's violation of UI norms in this area, but KF's is another story...
Title: Re: Bug: Newton-Raphson not working correctly Post by: Kalles Fraktaler on August 10, 2016, 01:30:13 PM Hi Paul The purpose of the Newton Raphson function is more like not having to manually zoom from e2000 to e3000 to find the next inflection point. I have not even tried to use it to find information about an already found minibrot or at levels less than e13... ...and after all I don't understand much of the function, it is like magic to me 88) The edit boxes in Visual Studio doesn't implement Ctrl+A per default, and in order to do so one must override the dialogs' message loop to be able to catch that key combination. Famous programs like Microsoft Excel don't support Ctrl+A in edit boxes either. Try to use tab to set focus to the next object in the dialog, and then Shift+Tab to jump back, then all the content will be selected. And I am sorry but I don't have much time to do anything with KF these days... The really cool new formulas added recently were so excited that I had to steal time from other things... :) |