CompositorType is part of the acceleratedRendering settings. If you weren't using that before then you didn't need the compositorType setting at all in your original code. Ergo, leaving it out is fine. I think you'd be better served by using a native scroller rather than a LiveCode field; the native scrollers are optimized for scrolling.
Accelerated rendering is only needed for dynamic objects that must move often; in your case that's a scrolling field. You should set acceleratedRendering of the stack to true in a preOpenCard handler when the card opens and turn it off in closeCard, because having it set on static cards without any dynamic objects actually interferes. Set the layermode of the field to "scrolling" in its property inspector. That tells the engine you want this to be a dynamic object that is affected by acceleratedRendering.
Don't worry about the compositorType for now, the defaults should work, except for Android versions less than 2.3. If you need to release for earlier versions of Android then you do need to set the compositorType to "software" because otherwise the colored boxes happen.
Buttons with unwanted box
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Re: Buttons with unwanted box
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com