Digital Workshop

Welcome to the Digital Workshop Message Boards
It is currently December 22nd, 2024, 11:16 am

All times are UTC [ DST ]




Post new topic Reply to topic  [ 4 posts ] 
Author Message
 Post subject: Web-export/Plexus Bug?
PostPosted: November 30th, 2006, 11:02 am 
Offline

Joined: November 8th, 2004, 5:23 pm
Posts: 279
Opus: Opus Pro 9
OS: Win 10/64
Today I found something that looks like a web-export - plexus bug.

It concerns the following:

I tried to create a photo gallery. I put some photos on page "gallery". I resized the photos (Scale to fit) to create some thumbnails on which the user should click to choose a photo.

Then I created some photo pages on which the same photos were displayed. But on these pages the photos have their original size (Fixed).

Everything works fine when exporting a Stand-Alone publication. All photos are displayed correctly.

When exporting as Web publication the photos on the photo pages are displayed in the size of the thumbnails instead of their original size.

It seems that it is problematic to use the same images in different sizes when exporting as Web publication.

To solve this problem I now use different images for thumbnails and the displayed photos and everything works fine.

Maybe thereĀ“s another reason for this strange behaviour but it looks like a bug in the plexus plugin or web-export.

@DW: Please check this behaviour and fix it in Opus 6.


T.

_________________
Opus Pro 9.75, Win 10/64, 8 GB RAM, Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 CPUs), ~3.4GHz, NVIDIA GeForce GTX 660 Ti, Roland OctaCapture


For this message Tarantoga has been thanked by : mackavi


Top
 Profile Visit website  
 
 Post subject:
PostPosted: November 30th, 2006, 1:53 pm 
Offline

Joined: November 8th, 2004, 5:23 pm
Posts: 279
Opus: Opus Pro 9
OS: Win 10/64
Addendum:

I think I understand now what is the reason for this behaviour.

It seems that in the export process an image is stored when the page is processed on which the image occurs the first time in a publication.

If the same image appears on other pages with another image size Opus "thinks" that the image is already stored.

Unfortunately Opus stores the images olny in the size which the image has on the first appearance. If this size is e.g. 20% of the orginal size then only this resized image is stored.

If the same image should be displayed on another page with 100% then Opus resizes the 20%-version of the image or displays the image small image instead of the 100%-version.


T.

_________________
Opus Pro 9.75, Win 10/64, 8 GB RAM, Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 CPUs), ~3.4GHz, NVIDIA GeForce GTX 660 Ti, Roland OctaCapture


For this message Tarantoga has been thanked by : mackavi


Top
 Profile Visit website  
 
 Post subject:
PostPosted: December 1st, 2006, 5:07 pm 
Offline

Joined: November 3rd, 2004, 2:08 pm
Posts: 130
Location: Above it all
Maybe this is a Browser cache issue. Once an image gets into cache it is used there after if the same name is called for. This would give the same result as your problem but puts the blame in a slightly different spot. The work-around is still the same as in your first case which is to name the photos differently. JMHO


For this message Evereddie has been thanked by : mackavi


Top
 Profile  
 
 Post subject:
PostPosted: December 1st, 2006, 7:57 pm 
Offline

Joined: November 8th, 2004, 5:23 pm
Posts: 279
Opus: Opus Pro 9
OS: Win 10/64
Evereddie wrote:
Maybe this is a Browser cache issue. Once an image gets into cache it is used there after if the same name is called for. This would give the same result as your problem but puts the blame in a slightly different spot. The work-around is still the same as in your first case which is to name the photos differently. JMHO


I do not think it's a browser problem because this issue appears only if the first appearance of an image is the small resized version of it (e.g. 50%).

For example:

page 2: image is resized to 20 %
page 3: image is displayed in 100%

In this case Opus takes the 20% image as the orginal and pumps it up to 100% which looks very jaggy.

Vice versa:

page 2: image is 100%
page 3: image is 20%

In this case ervything is OK because it is possible to resize an image to 20% with tolerable results but noch vice versa.

So another workaround is to put all images you use in the publication on page 1 in 100% size and do not show this page in your publication. In this case everything will be allright.


However, I think it's a bug in plexus. But now it is a known bug, so I hope DW will fix it soon.

T.

_________________
Opus Pro 9.75, Win 10/64, 8 GB RAM, Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 CPUs), ~3.4GHz, NVIDIA GeForce GTX 660 Ti, Roland OctaCapture


For this message Tarantoga has been thanked by : mackavi


Top
 Profile Visit website  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 4 posts ] 

All times are UTC [ DST ]


Who is online

Users browsing this forum: No registered users and 28 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group