his remark involves much more than code simplification, because as soon as one goes beyond a toy, or even in small toys, 'Inset' induces a lot of performance inconvenience when dealing with other dynamics stuff in the graphics, (either the inset stuff being static or dynamic) and much more when using locators. Particularly, in the case of locators I would avoid mixing them with 'Inset' as much as possible, and even more if locators and Bezier curves are to be put together.
As per the many times mentioned locators' issue, right now I am working on a notebook (still a small toy) which does not work with locators but works perfectly with 2D Sliders. It seems to indicate that the rest of the construct is OK, otherwise it would not work with 'Slider2D' either.
I have experienced the 'Inset' issue with locators many times; as soon as the inset stuff in the graphics is removed the problem mostly disappear.
-----Mensaje original----- De: djmpark [mailto:email@example.com] Enviado el: mi=E9rcoles, 19 de septiembre de 2012 10:58 Para: firstname.lastname@example.org Asunto: Re: Epilog/Prolog and Show Question
It has to do with the strange way that Show combines Options from the various plots. Put all of the Epilog material in a single Epilog in the Show statement. Essentially, that Epilog preempts any of the Plot Epilogs.