Huh, pasting over a selected bitmap used to stay in place. Another bad
change to the UI. The align commands might be faster and more precise
than dragging.

As a user I don't find it much work to find a button by its tooltip.
Usually the icon image gives some clue.

Normally I document the most efficient way to execute a command, which
is rarely via the toolbar button.

On Mon, Sep 16, 2013 at 12:54 AM, Alastair Dent
<alastair.dent at> wrote:
> I'm using something like your suggested workflow.
> The downside of it is that pasting into the pre-formatted frame doesn't work 
> well. Even if the scratch icon bitmap is selected, pasting doesn't replace 
> it. Selecting the frame and pasting results in the bitmap appearing in the 
> centre of the page. It has to be manually dragged from there to the frame.
> Just documenting the tooltip text is a huge failure in usability for the end 
> user.
> -----Original Message-----
> From: robert.lauriston at [mailto:robert.lauriston at] On 
> Behalf Of Robert Lauriston
> Sent: 15 September 2013 18:30
> To: Alastair Dent
> Cc: David Creamer; framers at
> Subject: Re: Inserting inline graphics
> Extracting the icons from the plug-in source should not be difficult, they're 
> usually all in one directory.
> Assuming the icons are all the same size, in a separate .fm file create one 
> frame with one scratch icon bitmap with all the settings as you want them. 
> Copy and paste that into your main document, copy your new icon bitmap, 
> select the scratch icon bitmap, and paste.
> I think that's the fastest workflow you'll get unless maybe you wrote a 
> FrameScript macro.
> To me it seems like a huge waste of time. I'd just document the tooltip text.
> On Fri, Sep 13, 2013 at 1:40 AM, Alastair Dent <alastair.dent at> 
> wrote:
>> I'm documenting a complex plugin for Eclipse. I will only know which buttons 
>> I need in the text as I'm writing. To pull out the button icons from the 
>> entire product and convert them would be a huge job.

Reply via email to