dix: remove misleading comment in ptrvelo.c
Signed-off-by: Peter Hutterer <peter.hutterer@redhat.com>
This commit is contained in:
		
							parent
							
								
									6ca34549b8
								
							
						
					
					
						commit
						e00cd54c1a
					
				| 
						 | 
					@ -152,9 +152,8 @@ Expected result is a series of filters, each progressively more integrating.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
This allows for two strategies: Either you have one filter which is reasonable
 | 
					This allows for two strategies: Either you have one filter which is reasonable
 | 
				
			||||||
and is being coupled to account for fast-changing input, or you have 'one for
 | 
					and is being coupled to account for fast-changing input, or you have 'one for
 | 
				
			||||||
every situation'. You might want to have loose coupling then, i.e. > 1.
 | 
					every situation'. You might want to have tighter coupling then, e.g. 0.1.
 | 
				
			||||||
E.g. you could start around 1/2 of your anticipated delta t and
 | 
					In the filter stats, you can see if a reasonable filter useage emerges.
 | 
				
			||||||
scale up until several motion deltas are 'averaged'.
 | 
					 | 
				
			||||||
*/
 | 
					*/
 | 
				
			||||||
void
 | 
					void
 | 
				
			||||||
InitFilterChain(DeviceVelocityPtr s, float rdecay, float progression, int stages, int lutsize)
 | 
					InitFilterChain(DeviceVelocityPtr s, float rdecay, float progression, int stages, int lutsize)
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
		Loading…
	
		Reference in New Issue