Keep images in place

As I've written before, I'm an absolute newbie to XWDP 18, so please be gentle with me :)

When viewing the site I'm working on in XWDP, it looks like this

Attachment 129420

When previewing it in Slimjet though, it looks like this

Attachment 129421


I know that I can use 'Anchor to text' to keep images in place while I'm working within XWDP 18, so I suppose what I'm really looking for is something equivalent to that, which will work when I actually publish my website. i.e. I want to ensure that the images remain in the gap within the text.

I'm currently working with a fixed width (1200 px) design. (My Slimjet screenshot is taken from my laptop monitor, with a horizontal resolution of 1366 px). So there's no stretching or compression of the page width involved here.

I'm sure that I'm missing something incredibly simple here. Please tell me what it is!

It may be incredibly simple but I don't know either.
The only difference is that the Preview will retain a memory of past changes.
The view into your published site will have a different history.

In both Preview and Publish, I would press Ctrl+F5, or Slimjet's equivalent, to clear the browser cache and look again.

Acorn

Thanks for your post, Acorn. All of my browsers are configured to delete the cache and cookies whenever I close them. I tried your suggestion anyway though but, alas, it didn't help.

I've now worked out what is going wrong but I still can't see why it's going wrong!

I've got 'Repel Text Under' ticked for all of the images on the site (with 15px set as the repel margin). So, in XWDP, I'm seeing this

Attachment 129427

However when I preview the page in Slimjet, the 'Repel text under' command hasn't been preserved , meaning that I see this

Attachment 129428

I've tried the old trick of 'turning it off and turning it on again' (i.e. removing the 'Repel text under tick and then reinstating it) but, sadly, it seems to make no difference.

Has anyone got any clue as to why the text isn't being repelled when I preview the site?

(Incidentally, this problem wasn't present when I was using the basic XWD 18. It's only since I persuaded Magix to give me a free upgrade to XWDP 18 that the problem seems to have arisen. So I now seem to be worse off than before!)

PS: I've tried actually publishing the site to my hard drive, rather than simply previewing it but the result is still the same :(

PPS: On another variation of 'turn it off and turn it on again', I've tried deleting an image and then re-inserting it (again with 'Repel text under' then added to its attributes) but it still makes no difference at all :(

Struggler, I think we need to get your design file or at least the offending objects in a separate upload.

Have you viewed the published site in any other browser?
If it is all right then it is Slimjet at fault.

The image needs to be above the text before it repels.
The Layer the image is on needs to not have Layer properties se to repel only text in that layer.

Acorn

Does it do the same in all browsers or just Slimjet?

Thanks for the replies.

The problem is present in other Chromium-based browsers, such as Edge and Chrome, too. It's also there in Firefox.

I'm only working on the base layer.

As my illustrations at 4.59pm show, 'Repel text under' works absolutely fine within XWDP itself. (If I move an image around, the text auto-adjusts to flow around it). The problem only occurs when I preview or export my website, when XWDP produces a website where the 'Repel text under' command has been totally ignored for every image that it's been applied to.

I've exported what I've done on the design so far as an XAR file, which I attach here.
Attachment 129431

If it loads the same for you as it does for me, everything in the 'Gallery' page displays correctly. (i.e. with the text repelled by the images). However, when previewing the site in a browser, the images overlay the text.

Ideas, anyone?

Struggler, remove the Name HTMLBlockText from your Text Areas.
This changes the HTML to be inside <p> Tags and the construction of the Repel Under is destroyed.

In passing, I do truly hope you are not saving any of your works as index.xar, ever!

Acorn

Thanks, Acorn. I'll see if that helps and report back.

(I don't regularly save anything in XAR format. I only used it here because it produces a single compressed file, rather than the collection of files generated by XWDP's default WEB format).

Quote:

---

Originally Posted by Struggler

Thanks, Acorn. I'll see if that helps and report back.
(I don't regularly save anything in XAR format. I only used it here because it produces a single compressed file, rather than the collection of files generated by XWDP's default WEB format).

---

Struggler, XWDP only saves the one file (.WEB), that is actually identical to the .XAR file. I truly do not understand what you are trying to describe.

When you Export or Publish, you get a "collection of files". You never work from these directly. The .XAR / .WEB is the master design file.

Acorn

You're a genius, Acorn - but I'm sure that you knew that already anyway =D>

Being thick (as always), I was only looking at the image properties and forgetting altogether about the text ones. I can't even recall why I added 'HTMLBlockText' in the name fields now. I know it was something to do with trying to resolve a screen reader compatibility issue for the site but I don't think it was actually necessary anyway now.

Thanks a million!

(I'm a moderator myself on the UK's largest - only? - general Q & A website and I spend much of my time trying to find answers for people on that site. It's lovely to be "on the other end of the system" for a change though, especially when there are such helpful people as you around!)

Thanks again!

Crossed posts!

Whenever I save in WEB format, I get a single file and an accompanying file folder. I sort of assumed that, just like when exporting a website, there was one index file and a whole host of other files inside the folder. Now that I've actually looked though, I've found that each of those folders contains just a single image file - so I haven't got a clue as to what it's purpose is anyway!

Quote:

---

Originally Posted by Struggler

Crossed posts!

Whenever I save in WEB format, I get a single file and an accompanying file folder. I sort of assumed that, just like when exporting a website, there was one index file and a whole host of other files inside the folder. Now that I've actually looked though, I've found that each of those folders contains just a single image file - so I haven't got a clue as to what it's purpose is anyway!

---

You get a folder generated (Support Folder is filename_xar_files) whenever you link to an external resource. You might being doing it but didn't know the implication.

is filename_xar_files (or filename_web_files) the name of the folder?

Acorn

Hi again, Acorn.

Sorry for the delay in replying.

Whenever I've saved a file from XWD (or XWDP) using the WEB format, I've always ended up with both a file and a folder, as illustrated here:
Attachment 129435

That's why (since I'd never had any reason to inspect the folder contents) I'd assumed that the 'Save' process was akin to that of saving a web page from a browser, where a file is created that contains the HTML code for creating that page, together with a folder containing all of the necessary files to do so.

Now that you've prompted me to look inside those folders though, I see that every one of them contains just one image file - and it's always the same one!
Attachment 129436

Weird!

Quote:

---

Originally Posted by Struggler

Hi again, Acorn.

Sorry for the delay in replying.

Whenever I've saved a file from XWD (or XWDP) using the WEB format, I've always ended up with both a file and a folder, as illustrated here:
Attachment 129435

That's why (since I'd never had any reason to inspect the folder contents) I'd assumed that the 'Save' process was akin to that of saving a web page from a browser, where a file is created that contains the HTML code for creating that page, together with a folder containing all of the necessary files to do so.

Now that you've prompted me to look inside those folders though, I see that every one of them contains just one image file - and it's always the same one!
Attachment 129436

Weird!

---

No, it's the way Xara handles external assets.

At some point you linked to the file rather than dragged it onto the design page.
panorama_website.web doesn't have a Support Folder.

Thereafter, Xara assumes you want it so it never deletes it and you get the Support Folder, filename_web_files.
Xara does not offer any housekeeping routines and if the file was 1GB, it would appear thereafter in every Backup.
Even worse when you publish and it is not a Fast Publish, Xara uploads the 1GB file all over again.

So many fall unknowingly into this and wonder why Backups and Uploads take so long.

If you have no need for the file, you can deletes each and every folder (and contents).
That said I would always keep one copy but never the master as it will duplicate again and again.

Acorn

Thanks, Acorn.

When I first started work on my site, I used the Panorama template and then ended up deleting everything except for the navigation bar. (Yes, I know that seems an odd way of doing things now but it was my first time of using the program and I was still very much fumbling in the dark with it).

Looking inside the index_htm_files folder, that's generated when I publish the site locally to my hard drive, I see that there are quite a few image files from the Panorama template that have been preserved, even though I've deleted them within XWDP:
Attachment 129439

None of them are massive, so they're no going to greatly impede the speed of uploading the site, but I'm thinking of deleting them from the folder manually nonetheless. Could that do any harm, do you think? (Opening the 'index' file with Notepad shows that there's still a load of lorem ipsum there too but I'm prepared to live with that. As I see it, there's not much point in using a WYSIWYG program if I'm going to end up rewriting the HTML!)

Thanks again for all your help.