I’m not convinced that is the solution.
For myself, when I insert a graphic into an inline layout I will start by
inserting a FWP html item instead of a FWP graphic item. I have no logic
for this, except that I am an exceptionally lazy and well-conditioned
creature of habits.After that, then I select the html item and press the
command-e key combo which brings up the image import dialog and I can
select my image. What seems to happen is Freeway automatically converts the
inline html item into a graphic item - the html box is no longer an html
box.
Now let me switch gears here a minute.
When I started inserting html items into inline layouts – especially into
runs of text – I noticed that it was a bit tricky getting the placement.
My natural instinct was to place a carriage-return after a block of text
then insert the new html item. This would always end up with an extra
linefeed (return for you youngsters), which can be miserable to erase if
you haven’t yet grokked the navigation of inline layouts. What I learned
was that at least with a block-element like a div, FWP seems to insert the
element on it’s own line (or at least that is the way it appears to behave)
so that I simply insert my divs on the same line of text either before the
first letter or after the last… the first will insert the div before the
line while the latter inserts it after.
So, back to graphic boxes.
Because of the way I insert graphics, I find that I must treat it like a
div until I import my image. Which means watching my insertion point. Now,
I’ve been doing this so long now that even if I cock-up and get that extra
space, I’m still very comfortable deleting it. I wish that I could just say
how I do it - if you were watching me work, you’d see it – it’s not
impossibly difficult. It’s simply an extra, empty paragraph line.
Sometimes you can spot it by using arrow keys to advance the cursor back
and forth through that portion of inline elements – after all, they are
just like letters in a sentence. You can see items hilite as the cursor
fixes on their position… or stroll through bits of text, if you have them.
When you happen on that stray, empty line you’ll see the cursor blinking
there with no items selected. Freeway Pro deletes extra spaces for us (the
web couldn’t show them anyway, unless they were non-breaking) however when
we carriage-return vertical spaces in FWP, the app interprets those as
non-breaking characters wrapped in paragraph tags. Your natural instinct
will be to backspace and delete the line, but what FWP does is delete the
line and the inline div preceding it… go ahead, you can say it -
AAAGGGHHHH!!! The trick is to think different.
If you don’t have Show Invisibles enabled, give yourself a good forehead
thwacking then turn it on. You’ll see the darned paragraph symbol next to
your flashing cursor. Simply hold down the shift-key and tap the
right-arrow key ONCE… you’ll see the paragraph symbol hilited. Tap the
delete key ONCE, and your problem should be solved.
I’ve noticed that if I copy an html item and paste it somewhere else in the
inline structure that I end up with an extra carriage return – weird,
because I select the item itself and not by dragging around it (like a word
of text).
So, all of that to tell you that I think the “rogue space” issue is a
function of FWP’s natural user interaction – changing how you insert
graphics is up to you, but I don’t think it will stop rogue spaces.
Learning how to anticipate Freeway’s behavior is like learning to dance –
sometimes with a partner with sometimes big clumsy feet – but, again, not
impossible.
Best of luck,
–
Ernie Simpson
On Mon, Jun 3, 2013 at 10:22 AM, RavenManiac email@hidden wrote:
I think I figured this out. I need to enclose the graphic box inside an
HTML box to eliminate the rogue spacing. Please correct me if I’m wrong.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options