Pasting images: purity or usability?

[Richard Gaskin]

There's an outstanding request to fix an issue in the engine with regard 
to pasting images:

    Currently, pasting an image from the Clipboard causes one
    of two things to happen:  either the image is pasted into
    the bottom-most image object, or if there are no image
    objects it creates a new image sized to match the entire
    card.  It's rarely the case in my own work that either is
    what I want. :)
<http://support.runrev.com/bugdatabase/show_bug.cgi?id=2473>

While RunRev hasn't taken the time to address this in the engine, they 
did take the time to implement a workaround in their IDE's Edit menu:

     if the clipBoard is "image" and the selectedImage is empty then
       lock messages
       lock screen
       create image
       put the clipBoardData["image"] into last image
       unlock messages
       unlock screen
       put true into tObjects
       choose pointer tool
       select last image

So at least their IDE works, even if users will be confused when their 
standalone behaves differently.

The question for us is whether we should maintain the purity of the MC 
IDE by using the engine's Paste command as it does now, or favor 
usability by implementing the workaround script from RR.

I'd like to say be able to report that we can expect a fix on this soon, 
but it's been outstanding for half a year so I think if we want this it 
it may not be productive to wait for the engine to catch up with us.

-- 
  Richard Gaskin
  Fourth World Media Corporation
  ___________________________________________________________
  Ambassador at FourthWorld.com       http://www.FourthWorld.com