Small book title page previews differently from layout in Aperture

I have laid out a small book and in Aperture I have:
1. The cover
2. A grey left hand page
3. A Title right hand page
4 etc - all the photos.
I've laid out some of these as double-page 1-up spreads. Looks great but the problem is when I preview it the grey left hand page right after the cover disappears, throwing everything out of sequence. This splits up the double-pagers, making the book absurd.
Any idea (a) whether Aperture or Preview correctly shows what the finished book will look like, and (b) how to bring them into line/avoid this happening again??

peter at knowhowpro wrote:
DHWachs wrote:
This post was great! Thank you so much. But I am hoping you know one more thing related to this. In the "transform" section of the definition (where the x/y coordinates are set along with height and width) there is an option called "angle". I was hoping that changing this value would allow me to offset the angle of the picture. However, if I put any value there other than 0 the template becomes unusable.
Do you happen to know what this option does?
I haven't looked into the files, so this is just a guess based on how some graphic applications work. It's common to think of rotating a shape as pivoting around a center point, but It's possible that the file sets a value for the rotation point not at the center. In some graphics applications, you can set a shape's pivot at any corner or in the middle of any side, of the rectangle that contains the whole shape.
So, your value may be rotating the shape around a pivot that moves the shape into some area that upsets the behavior of other shapes. Just a thought.
HTH
Regards,
Peter
Peter Gold
KnowHow ProServices
Peter's point is a good one. I would also assume that the "angle" property allows you to rotate an image, but I haven't tried it myself. One thing to investigate - are there any page templates included in LR that have image placeholders that are at an angle (I don't recall any, off-hand)? If so, looking at the associated .lua file could provide insight into how an angled image placeholder should be described.

Similar Messages

My firefox home page looks different from your tutorial

I am trying to learn to use firefox. Sometimes the firefox home page looks different from the one in your tutorial. Fox example, now I am looking above and the "plus sign" symbol to add a new tab is not there. Please advise me. Thank you.

You can find the New Tab button showing as a '+' on the Tab bar.
You can open the Customize window and drag the New Tab button that shows as a plus sign (+) from the Tab bar on another toolbar and it will become a regular toolbar button like the New Tab button that you have in Firefox 3 versions.
If you can't find the New Tab button then click the "Restore Default Set" button in the Customize window.
*http://kb.mozillazine.org/Corrupt_localstore.rdf
If you want the New Tab button at the far right end of the Tab bar then place a flexible space to the left of it.
* New tab toolbar button: https://addons.mozilla.org/firefox/addon/new-tab-toolbar-button/

Why do my Organizer & Editor pages look different from those in books and the brochure that came?

Why do my Organizer and Editor screens look different from the ones in books and in the brochure that came with installation cd?

Which version of the photoshop elements are you using.
You can get the help files of the latest version of photoshop elements 11 from the following link:
http://helpx.adobe.com/photoshop-elements.html
Thanks
Harshit yadav

Page preview different than live view

My new page looks fine in preview, but once I upload it to the server, the layout is wrong, and the page looks completely different. I get an error saying Some files on the server may be missing or incorrect. Clear browser cache and try again. If the problem persists please contact website author. Please help? Thanks!

Hi Sara,
Can you please help us with the URL of the website and screenshots.
Regards,
Akshay

Page margin different from column guides

i have an indb which is comprised of 80 single page files that i am updating from last year, and am resizing each one, using layout adjustment. each page opens with this artifact on the master page files: the page margins are correctly set at .25" left and right, but the column guides show them shifted over maybe an eighth of an inch. if i go into margins and columns and change the right margin up or down, and then change it back, the column guide snaps back to match up with the page guide at .25". do you know why this is happening? i would rather not do it for every single page. i have synchronized the book with the correct master page settings and it doesnt change the problem.

That seemed pretty odd to me, but I was able to reproduce it (or something similar) by unlocking the column guides and dragging a guide away from the margin and then adjusting the margins.
It might also be corrupt prefs, though, so have a look at Replace Your Preferences

Layout on iOS differs from Layout on Android

I am getting (remaining) very frustrated with my choice to use Flex and Adobe products for my mobile app. Adobe making SWFLoader an available object in mobile WITHOUT TELLING US IT WON'T WORK IN PRODUCTION cost me a lot of time and money. My last post here was at the beginning of November when I believed I was about ready to deploy my app but I've had to take all this time to re-write it given that SWFLoader was added to the dist just to make it possible for programmers to really go the wrong direction. Sorry to be so annoyed but honestly, this has cost me a lot of money and I don't have the rest of my life to screw around with software that does not do what the vendor says it will do.
In any event, my latest frustration, now that I'm back to being done with all the re-coding aspects of the app, is getting it to lay out on screen properly. On my Android device, I just add the flex component to the screen, find the registration point, center on that and it lays out properly. In iOS, it does not work. Here is an example of laying out a screen with a center registration point.
var xPixels:uint = Capabilities.screenResolutionX;
var yPixels:uint = Capabilities.screenResolutionY;
                if(xPixels < yPixels) {
                    //phone is tilted and we're measuring the incorrect orientation.
                    //reverse x and y and double them to get proper screen dim.
                    var yPix:uint = xPixels + xPixels;
                    xPixels = yPixels + yPixels;
                    yPixels = yPix;
                //the following will be sure that we've centered the
                //screen.
                xPixels = xPixels / 2;
                yPixels = yPixels / 2;
               this.busyLoader = new LoaderMessageCurtain;
                busyLoader.x = xPixels;
                busyLoader.y = yPixels;
                enemyViewContainer.addChild(busyLoader);
                loaderShowing = true;
In the above code, busyLoader was created in FlashPro (as all my screens and animations are). It was converted to a Flex component. It has registration at the center of the screen. On Android, this code causes the screen to lay out properly. On iOS, I'll get the top left corner in the center of the screen. WHY?????????????? WHY, WHY, WHY? I'm sick of it. Can anyone help me understand the voodoo that is going on behind the scenes to actually be done with this project with a professional looking piece of software that behaves as expected on ALL platforms it is touted as being able to be run on?
Notice as well that on Android, I don't have to tell busyLoader what dimensions it is. That's great. However, on iOS, if I don't set the width and height of the component, it will be giant or super small but not properly sized in either case. When I do set the dimensions, the outcome is problematic. Sometimes it fits and sometimes I need to add or subtract an arbitrary number of pixels to get it size properly. Sigh.
Also, I write software on a large monitor. Using the emulators to lay out code is a total waste. If I use the iPhone 4 emulator, for instance, it reports that my screen size is 1900 by 1200. Well, my monitor is 1900 by 1200 but an iPhone is not (it's 960 by 640 if I recall). It does me no good to have an emulator lay out based on my screen size. That too has cost me dearly. No offense and your tools are cool and I hope that I'll be able to solve my frustrations with Flex and continue to use your tools, but why don't you guys try doing what I do before I release software... make sure it works?

The reason the objects have a center registration is because the animator was trying to ensure that the animations work for different screen sizes without changing the length to width ratio of the animations. He drew a black border around the entire stage. On platforms where the screen does not fill the stage properly, the black border shows up at bottom. While I will make sure that he keeps them registered at top left from now on, I don't see why that makes any difference. A center point is a center point and should work as well as any other point on a screen (I would think).
Well the problem is that it requires you to know ahead of time how a particular asset is registered in order to properly layout and position it through code. Display objects are much easier to work with if you can assume they are always registered in their natural top left corner, and should not extend passed the desired width/height (IE. setting a negative x/y value to get a "border"). This allows the developer to know exactly where it should be positioned based on it's measured size, without having to worry about varying registration points.
I'm very interested in your thoughts on the Capabilities.screenResolutionX and Y function. Given that screens are not laying out properly without explicitly setting their size, and I want them to be the size of the screen in question (it's a full-screen mobile app), I have no choice but to call Capabilities.screenResolution X and Y and set myFlexComp.w and h as these values. If there is a better way to do this, please point me toward the resource so I can learn about it.
One should never assume the application fits the entire screen (as you have seen first hand). There are numerous better way to do this. It really depends on how your application is set up.
Here is an example AIR app that shows one possible way these assets can be correctly imported and positioned within your application. If you run the app and resize the window, you will see that the icon will always remain centered and the background will always fill the size of the window (notice how the MainView_background symbol has 9-slice scaling enabled in the fla, which is how the border remains a uniform size regardless of the window size).
<?xml version="1.0" encoding="utf-8"?>
<s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark"
                                                                              xmlns:views="views.*" width="1024" height="768">
               <fx:Style>
                              @namespace s "library://ns.adobe.com/flex/spark";
                              @namespace views "views.*";
                              views|MainView
                                             backgroundClass: Embed(source="assets.swf", symbol="MainView_background");
                                             iconClass: Embed(source="assets.swf", symbol="MainView_icon");
               </fx:Style>
               <views:MainView top="0" left="0" bottom="0" right="0" />
</s:WindowedApplication>
package views
               import flash.display.DisplayObject;
               import mx.core.IFlexDisplayObject;
               import mx.core.ILayoutElement;
               import mx.core.UIComponent;
                * This class takes 2 styles for a background and icon class. The background is
                * scaled to the size of the component, while the icon is centered within it.
                * I also copied a few utility methods from the MobileSkin to show how the various
                * class formats are supported.
               public class MainView extends UIComponent
                              public function MainView()
                                             super();
                               * Copied from spark.skins.mobile.supportClasses.MobileSkin
                              public static function getElementPreferredHeight(element:Object):Number
                                             if(element is ILayoutElement)
                                                            return ILayoutElement(element).getPreferredBoundsHeight();
                                             else if(element is IFlexDisplayObject)
                                                            return IFlexDisplayObject(element).measuredHeight;
                                             else
                                                            return element.height;
                               * Copied from spark.skins.mobile.supportClasses.MobileSkin
                              public static function getElementPreferredWidth(element:Object):Number
                                             if(element is ILayoutElement)
                                                            return ILayoutElement(element).getPreferredBoundsWidth();
                                             else if(element is IFlexDisplayObject)
                                                            return IFlexDisplayObject(element).measuredWidth;
                                             else
                                                            return element.width;
                               * Copied from spark.skins.mobile.supportClasses.MobileSkin
                              public static function setElementPosition(element:Object, x:Number, y:Number):void
                                             if(element is ILayoutElement)
                                                            ILayoutElement(element).setLayoutBoundsPosition(x, y, false);
                                             else if(element is IFlexDisplayObject)
                                                            IFlexDisplayObject(element).move(x, y);
                                             else
                                                            element.x = x;
                                                            element.y = y;
                               * Copied from spark.skins.mobile.supportClasses.MobileSkin
                              public static function setElementSize(element:Object, width:Number, height:Number):void
                                             if(element is ILayoutElement)
                                                            ILayoutElement(element).setLayoutBoundsSize(width, height, false);
                                             else if(element is IFlexDisplayObject)
                                                            IFlexDisplayObject(element).setActualSize(width, height);
                                             else
                                                            element.width = width;
                                                            element.height = height;
                              private var _background:DisplayObject;
                              private var _icon:DisplayObject;
                              override protected function createChildren():void
                                             super.createChildren();
                                             var bgClass:Class = this.getStyle("backgroundClass") as Class;
                                             if(bgClass != null)
                                                            _background = new bgClass();
                                                            this.addChild(_background);
                                             var iconClass:Class = this.getStyle("iconClass") as Class;
                                             if(iconClass != null)
                                                            _icon = new iconClass();
                                                            this.addChild(_icon);
                              override protected function measure():void
                                             super.measure();
                                             //lets say our prefered dimensions are at least the size of the icon...
                                             if(_icon)
                                                            this.measuredWidth = getElementPreferredWidth(_icon);
                                                            this.measuredHeight = getElementPreferredHeight(_icon);
                                                            trace("this.measuredWidth = " + this.measuredWidth);
                                                            trace("this.measuredHeight = " + this.measuredHeight);
                               * @private
                              override protected function updateDisplayList(unscaledWidth:Number, unscaledHeight:Number):void
                                             trace("MainView.updateDisplayList(" + unscaledWidth + ", " + unscaledHeight + ")");
                                             super.updateDisplayList(unscaledWidth, unscaledHeight);
                                             //bet let's actually scale the contents to the full size as set by the parent...
                                             if(_background != null)
                                                            setElementSize(_background, unscaledWidth, unscaledHeight);
                                                            setElementPosition(_background, 0, 0);
                                             //and we will center the icon within those bounds...
                                             if(_icon != null)
                                                            var iconWidth:Number = getElementPreferredWidth(_icon);
                                                            var iconHeight:Number = getElementPreferredHeight(_icon);
                                                            var iconX:Number = (unscaledWidth - iconWidth) / 2;
                                                            var iconY:Number = (unscaledHeight - iconHeight) / 2;
                                                            trace("iconWidth = " + iconWidth);
                                                            trace("iconHeight = " + iconHeight);
                                                            trace("iconX = " + iconX);
                                                            trace("iconY = " + iconY);
                                                            setElementPosition(_icon, iconX, iconY);
This methodology uses the appropriate stages in the flex component life-cycle to create, measure, and position its contents.
*note: I was going to attach an example project, but I can't seem to figure out how to add an attachment. Send me a PM if you would like me to email it to you.
*edited a few typos*

Session state of page item different from one region to another region

hi,
on one particular page I have two regions. A page item (LOV pop-up) is set in the first region. I leave this region with a button and jump back with a branch to the same page. The page item has now the selected value (as is shown by session state window). So far so good.
The second region (SQL query type) uses this page item. However, for some reason the page item is NULL in that second region.
Can anyone explain this behavior ?
ron

thanks Joel,
I did already what you suggested. The title in region 2 is evaluated to the same value as in region 1.
The SQL query (that actually runned with identical syntax before) is:
select bla from blatable where bla = :P920_RU
this generates:
report error:
ORA-12801: error signaled in parallel query server P000
ORA-01741: illegal zero-length identifier
So apperently the bind variable is evaluted to (or cached as) NULL.
I noticed something strange in the session window. There are several page items in the application. All of them are listed in the 'Session State' region. The page item that makes problems is the only one that is also listed in the 'Page Items' region. It is even listed when I start the session window from another page. Weird.
any other ideas ?
Actually, how could you possibly clear session state between rendering two regions ?
Ron

Live preview differs from IExplore

Hello all, i created a template in photoshop and opened it in dreamweaver. when i view the live, it seems to display clean and crisp. but when i try it in internet explore its seems a bit pixelated. it is not very obvious but my keen eye can tell me. i have also noticed when i draw a div box and place text in it, the preview is fine in the live preview but the div box shifts about 3 spaces to to the left in IExplore. i have not loaded a css to the file as am not experienced creating css layouts. Is there a way to fix these problems.

Upload your page and dependant files to a remote server space and post a URL, please.
FWIW Browser variation is nothing new. When you're experienced with CSS, you learn to build your sites and test them to perform well in the standards compliant browsers (Firefox, Chrome, Safari). Then use conditional comments or hacks to fix things that don't work in IE.
As for pixelation, it could be you optimized your images poorly in PShop or didn't save them correctly for the web as JPEG or PNG. But there's no way we can help you without seeing your page.
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
www.alt-web.com/
www.twitter.com/altweb
www.alt-web.blogspot.com

Picture Titles in Slideshow, different from filenames

I want to add a different title to each picture in a slideshow, but don't want to use filenames for this purpose. How do I do that?
My filenames work fine for filing, but are not suitable for enhancing a slideshow.

I'm new to Lightroom, but am trying to set up my slideshow first session presentation. I want the filename to show with each slide for identification purposes. But, I can't seem to find where to turn the filename on/off. I'm sure it's a simple operation, but I sure can't find it at the moment!!!!
Thanks,
Jim...

Offline preview differs from online display of Japanese text

I can't figure out why my web site in English and Japanese cannot correctly display the Japanese type when uploaded. The offline preview is fine, but the online version turns the Japanese to gibberish. I have set the charset="UTF-8" in metatags and in the javascript code.
Thinking that I may have missed a supporting file in the upload, as a test, I downloaded the entire directory and opened the file offline, but it again works fine on my desktop. The same browsers (Safari, Chrome and Firefox) used for online and offline viewing.
Why won't my Japanese text display online when the offline preview is fine ?

Have you set the correct charset on your webpage? If not try to put this within the head tags on your page:
<meta http-equiv="Content-Type" content="text/html; charset=shift_jis">
Hope this works.

Preview Differs From Final Burn

Trying to burn a dvd with chapter selection.
I preview the whole dvd before burning and it looks fine.
Test every chapter, watch the whole dvd etc. No problems. Plays how I'd like it to.
I burn it without any problems or error messages.
But, when I watch it in a regular dvd player.
Menu load and I go to play it and it starts halfway through the video.
I go to the scene selection menu and it starts from the same place.
Every scene goes right back to halfway through the movie.
The dvd won't play in the computer that I burned it on.
And when I preview the file in IDvd post burning the preview is messed up like the dvd.
Anyone else have this problem?

Welcome to the Apple Discussions. Instead of burning from iDVD use the File->Save as Disk Image menu option. That encodes the project and saves as a disk image. You can mount the disk image and play it with DVD Player. If the chapters work OK there then the problem is with the burning process. If the chapters are as they should be burn the disk image to disk with Disk Utility.
Be sure to use quality media, Verbatim-R is the most recommended brand here, and burn at the slowest speed possible.
OT

Why is page size different from my original Illustrator file?

My art board in Illustrator CS6 was set to the correct dimensions (4.25" x 5.5") with an added bleed (set to .125"). However, when I save as a PDF and viewed the resulting document in Acrobat Pro, there is now almost a half-inch ADDED to the overall page size of the document! This has never happened to me before when saving documents as PDFs. Is there a setting somewhere that I can change to make this stop happening?

Check the bleed and page framing settings in the PDF export dialog.
Mylenium

Payment term in PO print preview different from PO header

We have set payment term ZI60 for vendor 2033803, but on the PO print preview it's "Payable immediately Due net" .In PO header (In delivery/invoice tab) also, it shows payment term to be ZI60...but on print preview it shows 'Payable immediately Due net' .What could be the reason?

"Payable immediately Due net" may be the description of payment term ZI60
goto to table TVZBT give ur payment term ZI60 and see the description......
i think
in the print program they have designed to display the description of payment term...if u want to display the payment term then ask ur ABAPer to change it...

I don't have one single button for Firefox menu in spite of downloading Firefox 5 Version. The page presentation has File, Edit, View, History, Bookmarks, Tools and Help. Why my page is different from the feature shown in your product presentation ?

I have not Windows NT.
'''I have Windows 7'''

You see the orange (on Linux gray) Firefox button if the Menu Bar is hidden, so you need to hide the Menu bar via View > Toolbars, also accessible via Firefox > Options.<br />
If you need to access the hidden Menu bar then press F10 or hold down the Alt key to make the Menu Bar appear temporarily.<br />
You can place the Tab Bar on top.
* View > Toolbars : [ ] Menu Bar
* View > Toolbars : [X] Tabs on Top
* http://www.mozilla.com/firefox/features.html

Book title/cover page not appearing in exported file?

Hello, for some reason my book title page on the exported file does not appear the same as my preview copy.
On my bookshelf, my preview copy (which has a small 'proof' flash) has the cover design as produced in the Author app.
I have exported the file for somebody else to check the contents of file, when they download and open the file in iBooks the file has a white cover with 'Book Title' on it, not the design that appears in the preview file.
Many thanks

Moved to BOE Admin forum

Small book title page previews differently from layout in Aperture

Similar Messages

Maybe you are looking for