An idea on multithreading implementation

[Richard Gaskin]

Scott Rossi wrote:
 > But fast graphics processing would be a very welcome addition.

Here's one option that would give order-of-magnitude speed increases to 
any object that takes advantage of the current graphic effects, 
implementable by merely extending existing syntax to allow an 
"alwaysBuffer" property for all controls:

<http://quality.runrev.com/qacenter/show_bug.cgi?id=9113>

As it is, any object that uses the otherwise-powerful graphic effects 
cannot be selected, moved or animated without prohibitive cost to 
performance.

We could convert such objects to bitmaps ourselves if not for a design 
decision not to allow it:
<http://quality.runrev.com/qacenter/show_bug.cgi?id=9164>

I'd be okay with the current lack of buffering of the rendering of 
graphic effects and a default of not allowing one to export snapshots of 
such objects as long as there were options to do otherwise.

But as it is, I find myself not using graphic effect nearly as often as 
I'd like to, instead making such treatments in other programs and then 
importing the masked PNGs....

--
  Richard Gaskin
  Fourth World
  LiveCode training and consulting: http://www.fourthworld.com
  Webzine for LiveCode developers: http://www.LiveCodeJournal.com
  LiveCode Journal blog: http://LiveCodejournal.com/blog.irv