THere are the docs here: 
- http://udig.refractions.net/confluence/display/DEV/04+Commands

One of the pages is on composite commands:

They have a nice example where a set viewpoint centre; and set scale are 
combined into a single "CompoundCommand"

As for stopping the rendering; that is what Map sendCommand does; you send your 
command and it sits in a queue. When their is a gap in the rendering the 
command is run (in this case two of them) and then rendering is allowed to go 
again. 

I hope that helps; and if you have any feedback on these documentation pages 
(or want to edit them yourself) you are most welcome.

-- 
Jody Garnett


On Friday, 14 October 2011 at 3:50 PM, Trupti Pol wrote:

> Jody,
>  
> Thanks for the reply.. we will surely work on those approaches.
> But will you please explain about batch commands, (Right now we are not using 
> it)
>  
> How to stop Rendering, Run batch commands and then restart rendering....
>  
> This will be really very helpful to us because most of our processes face 
> this rendering issue.
> 
> On Mon, Oct 10, 2011 at 6:14 PM, Jody Garnett <[email protected] 
> (mailto:[email protected])> wrote:
> > Jesse is the best one to answer; my preference would be to either: 
> > a) expose this setting as a preference so it can be experimented with. 
> > b) ask the system to notice when it is getting "interrupted" and adjust the 
> > value accordingly (and then gradually reduce the speed again)
> > 
> > I should also ask; if you are doing this programatically can you ensure you 
> > are using a batch command (so the changes go in a group) 
> > 
> > This should be the same effect as if you stopped the renderer, did your 
> > changes, and then asked it to redraw. 
> > -- 
> > Jody Garnett
> > 
> > 
> > On Monday, 10 October 2011 at 5:03 PM, Trupti Pol wrote:
> > 
> > 
> > > Hi,
> > > 
> > > This is just to get some idea about Renderer,
> > > 
> > > We have a service implemented which keeps on checking/unchecking layers
> > > programatically in the LayersView.
> > > 
> > > Now in this operation we were facing flickering issue during rendering
> > >  (Raster Layers). 
> > > 
> > > After a through debugging and testing we reached to a solution according 
> > > to
> > > which if we change the "wait_period" variable value from 400 ms to 1000 ms
> > > in
> > > net.refractions.udig.project.internal.render.impl.RenderExecutorComposite.incrementalUpdate(),
> > >  the flicker does not reappear, but as we haven't yet explored the 
> > > Renderer
> > > to a great extent, we are not really very sure about the pros/cons of this
> > > change? 
> > > 
> > > Will you please give us some idea about whether there will be some
> > >  consequences which may occur due this change??
> > > 
> > > --
> > > View this message in context: 
> > > http://udig-devel.19327.n5.nabble.com/Modifying-wait-period-of-the-RenderExecutorComposite-tp4887203p4887203.html
> > >  Sent from the udig-devel mailing list archive at Nabble.com 
> > > (http://nabble.com/).
> > > _______________________________________________
> > > User-friendly Desktop Internet GIS (uDig)
> > > http://udig.refractions.net (http://udig.refractions.net/)
> > > http://lists.refractions.net/mailman/listinfo/udig-devel
> > 
> > 
> > _______________________________________________
> > User-friendly Desktop Internet GIS (uDig)
> > http://udig.refractions.net (http://udig.refractions.net/)
> > http://lists.refractions.net/mailman/listinfo/udig-devel
> > 
> 
> _______________________________________________
> User-friendly Desktop Internet GIS (uDig)
> http://udig.refractions.net
> http://lists.refractions.net/mailman/listinfo/udig-devel

_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel

Reply via email to