Kurt, OpenJUMP optimization is Larry Becker's speciality! :] Maybe he has some insights.
However, it is an area the interests me. It should be too difficult to write a plug-in that can do what you are talking about. In fact, this could propbably be done using an abstract class like "NoRenderingOperation" or something like that. Let me know if you are going to pursue this further. The Sunburned Surveyor On Mon, Feb 25, 2008 at 11:54 PM, Kurt Heston <[EMAIL PROTECTED]> wrote: > If I choose more than a couple dozen items and attempt to scale them all > at once, OpenJump pegs the processor and goes out to lunch on me. I've > profiled the process and it appears to be checking the AWT event queue > quite a bit (>50% of the total time). The next largest amount of time > spent is within Math...floor() (2.59%). > > I once left it alone for a couple of days and it finally did complete > scaling all of the Polygons. My machine is new and fast, not a hardware > issue. > > Unless there's a workaround, I've resigned myself to needing to write a > plug-in that interacts with the GUI less and the features themselves > more. However, if someone wants to point me to where the same work can > be done in OpenJump itself, that would be great, too. A "repaint when > complete" or "disable preview" checkbox would do the trick I'd imagine... > _______________________________________________ > jump-users mailing list > [email protected] > http://lists.refractions.net/mailman/listinfo/jump-users > _______________________________________________ jump-users mailing list [email protected] http://lists.refractions.net/mailman/listinfo/jump-users
