Wave wrote:

>
> Has anyone seen information on custom window classes.  I looked  
> through
> documentation about classes but I was not able to fine what I  
> remembered.
> I thought there was a way to add a modifier to a window class so  
> that you
> can treat one window differently than another based on its class.   
> As an
> example of what I mean if you have two document windows that are  
> derived
> from _kDocumentWindowClass but one document is considered a  
> spreadsheet
> while the other is considered a chart.  To distinguish one from  
> another you
> added created the window as _kDocumentWindowClass + _spreadSheet or
> _kDocumentWindowClass + _chart as needed.  If you needed to cycle  
> through
> just the spreadsheets you did something like this
>
> local fn UpdateAllSpreadsheetWindows( windClass as long )
> '~'1
> dim as WindowRef w
>
> w = fn GetFrontWindowOfClass( windClass, _true )
>
> long if ( w )
> fn UpdateSingleWindow( w )
> while ( w != _nil )
> w = fn GetNextWindowOfClass( w, windClass, _true)
> long if ( w != _nil )
> fn UpdateSingleWindow( w )
> end if
> wend
>
> end if
>
> end fn
>
>
> windClass = _kDocumentWindowClass + _spreadSheet
>
> fn UpdateAllSpreadsheetWindows( windClass  )
>
> OK, that was the long-winded version of asking, has anyone seen  
> where you
> add custom window classes.  I was sure they existed.  As an  
> alternative I
> could add a window property denoting the custom class and check it  
> when
> I cycle through windows but I thought I've seen what I've described  
> before.
>
> Any ideas?
>

Could it be the class (category) param of the old window statement  
you're thinking of? AFAIK, FBtoC ignores that param but it can be set  
(after creating the window) by:

	fn WindowCategory( wNum, wCategory )

and retrieved with:

	wCategory = window( _outputWClass )
and:
	wCategory = window( _activeWClass )

Bernie