Scaling effects

Can anyone please tell me where the preference is that controls the scaling of effects? I recently had to enlarge an ad by 1000% for a display banner but when I entered the 1000% scale the effects didn't scale with the objects. I had to do things manually which took more time than it should have. This usually isn't a problem in Illustrator (Scale Strokes & Effects) but ID seems to behave differently. It's as if ID is somehow remembering the scaling, even after saving and closing the file, because I continued to have trouble after reopening it.
Also I noticed that type became greeked after enlarging even though it was ten times bigger than in the original ad (and no greeking there). I must be doing something wrong but I can't find out what.
The resulting pdf was o.k.; it was just the ID file that was playing up.

InDesign can scale stroke weights when the "Adjust Stroke Weight when Scaling" option is selected. This option is a flyout on the far right of the dock. And even if you have the option selected, you must use the Selection Tool (as opposed to Direct Select) to select an item for it to work.
As for effects like drop shadows, the effect itself will not transform along with the item, and this includes scale, rotate, reflect, etc.

Similar Messages

  • 9 Slice Scaling & Effects - Incompatible?

    I'm having problems with 9 slice scaling in CS5: Inner glows stretch, drop shadows disappear entirely, etc. Round corners work fine, but other than that it's nothing but a bag of hurt. I've search high and low for answers to this, to no avail. Anyone else seeing this?

    jcarpenterss wrote:
    Terrific. Undocumented limitations to common usages. I ask again:
    It doesn't work with effects
    It doesn't work with nested objects.
    It only seems to work with rounded corners.
    ... ergo, what is nine slice scaling good for? Genuinely curious. It's certainly no good for... user interface production. I can attest to that.
    So what am I doing wrong.
    This one looks like a compromise but I think tat is necessary. How would do it for parts that go off the  slice.Of course you can adjust the slices to accommodate the art better. You know you can adjust the slices? I will do that later and show you how that works. Or you can look at the help files.

  • Scaling Effects on Multiple Layers

    Is it possible to scale the effects I have applied (namely, stroke) on multiple layers at the same time?
    I currently have 20 layers with the stroke applied, and it's a tedious and time consuming task scaling them individually after I've scaled the image/design (using Layer -> Layer Styles -> Scale Effects).

    rbd_bellamy wrote:
    Is it possible to scale the effects I have applied (namely, stroke) on multiple layers at the same time?
    I currently have 20 layers with the stroke applied,
    Given that you say you have 20 layers with the same stroke effect, why don't you just scale your stroke effect on one layer (as you already did) and then right-click on layer >> copy layer style after which you select the remaining 19 layers (click first, shift-click on last) and right-click >> paste layer style ?

  • Scaling Effects in InDesign

    Hi'
    Can I scale effects in Indesign in a grouped object?

    Yes, you can scale most effects if you have 'adjust scaling percentage' set in your General prefs. This doesn't include drop shadow or gradient feather though.
    As a workaround, check out the free LayoutZone plugin to export an area to InD file which you can then place and scale.

  • What is going on with the new version of Illustrator? Just upgraded the last update and ever since scaling effects on basic shapes is not working at all!! so frustrated!!

    I cannot even scale a basic logo forms without the shape widths changing all different. Yes, I restarted the program and restarted my computer.
    what is going on? something that should take me 2 seconds Ive been spending an hour trying to resolve the issue.
    please help!!

    Look at snapshots attached. Original vs. scaled. anymore advice?

  • 9 slice scaling effect

    Does anybody know of a way to mak a 9 slice scaling symbol in Edge Animate ?
    What i did here was build a symbol with 3 pngs : one for the top round corners, one for the bottom with the pin (which is positioned 0px from the bottom), and one for the middle, which is a slice of it.
    I can design the middle one to scale up as the placed symbol grows, except, it will never make something nice from percentages.
    Any idea welcome before i start to dig into code
    (and right now, i'm not even thinking of having them scale up as transition, i'm more thinking different bubbles of text which have the right size)
    Attached should be the base folder with Ai.

    Ok, i found the answer by myself
    I just put my top and bottom OUT of the symbol boundaries, and the inside is 100%

  • How does scaling work under Windows 7 with the new MBP with retina display?

    After installing Windows in a boot camp partition on the new MacBook Pro, how does scaling work compared to OS X? Does Windows know to have several pixels imitate a single pixel like in OS X when running in 1440 x 900, or is there no scaling effect available?

    I suggest reading the following article that was published yesterday...
    Windows 7 Tested on Retina Display

  • Scaling buttons with text

    Hello,
    I work with the brand new fireworks CS6.
    I would like to make a simple navigation with 5 buttons. But there is a big problem with the scaling of text. Even if i place buttons of the standard library i can't scale correct !!!!
    After scaling the text is no more centered (vertical and/or horizontal).
    When i write long text in a button i got some horrible scaling effects.
    I tried to fix this problems many hours because i can't believe that such a basic function doesn't work.
    In my symbols (buttons) i centered the text and the rectangle exactly (horizontal and vertical).
    Do i have to change something in my properties?  
    Thanks,
    psek

    Dear Linus,
    I think the 9-slice guides does not take effect to Text. They take effect only on forms. In my case i have a rectangle with text inside. The 9-slice guides are only for the rectangle relevant.
    As explained it even doesn't works with the buttons from the fireworks standard library.
    psek

  • Scaling/Zooming ImageElements

    Hi,
    this post is not only OSMF specific but it would be great if someone can help out with my problem.
    I'm currently working on a MediaPlayer which works with VideoElement and ImageElements in a series. The VideoElements are dynamic anyway so I would like to animate the static images. My goal is a "Ken Burns - Effect" with movement and zoom. But first of all I need to find a way to access the right paramters of a ImageElement to manipluate them at runtime. Because ImageElements are static I load them as DurationElements first.
    As what I know I need to access the current DisplayObject of the MediaPlayer at runtime. I do this by adding a EventListener on a ImageElement:
    imageElement1.addEventListener(MediaElementEvent.TRAIT_ADD, onTraitAdd);
    Now in the Listener function I can access the current Element:
    var displayObjectTrait:DisplayObjectTrait = event.target.getTrait(MediaTraitType.DISPLAY_OBJECT);
    But what I can't do know it to manipluate the current DisplayObject through e.g. :
    displayObjectTrait.displayObject.scaleX = 0.5;
    Working this way makes nothing happen.
    Is there a better way to manipulate the ImageElement-Parameters at runtime? Has someone an idea how to apply a dynmic zoom or scaling effect on ImageElements?

    Have you tried using the OSMF layout API?  This might be a simpler approach since you don't have to drill down to the DisplayObject, you only need to set some layout parameters (in the form of a LayoutMetadata) object and assign it to the ImageElement.
    For an example of dynamic layout, see "Dynamic Layout" in the ExamplePlayer sample app (source here).

  • Maintaining extrude and bevel effect

    I am currently designing a logo with the extrude and bevel effect. It is fine at full size, but when I copy and paste it and scale it down for another file--a.e. a business card--the effect is lost.
    Why is this happening? Do you have to apply the effect seperately when the object is rescaled?

    This is another option of scaling effects but it slows down the computer when it comes to more than one applied effects. That's why I told him to expand the effect.  Of course when expanding he can't edit effect's properties.

  • Convert SD Material to DV-AVI First? A Little Story

    I was handed a simple little Project recently. The Assets were 18 WMV files with different Frame Sizes and different PAR’s. The end result was to be DVD-Video, Widescreen (16:9). I was in a bad mood, as I felt that there were better files to work with, than the WMV’s, but I got stonewalled on that. I also felt that those “lost files,” probably at least had uniform Frame Sizes, though there were going to be differences in PAR, as some were obviously 4:3 and some 16:9. The final Project was to be a multi-DVD set (2 discs), with a total runtime of just over 4 hours. We ended up with 14 Timelines/Sequences, with some in the 30 mins. range, and the rest shorter - some much shorter.
    Normally, I would have just converted everything to DV-AVI in one batch, but I was just anxious to rush through everything. This was a bad move, and I should have been in a better frame of mind.
    I fired up PrPro and Imported the WMV’s into it. They all Imported fine. OK, I’m off and running, or so I thought. I waited for Conforming and PEK generation to complete, and started cutting. This was all quite simple, as it was basically setting In & Out Points, and adding some rather simple Titles. I did have to use Effect>Motion>Scale, some Cropping and Motion>Position to work with the PAR differences and improve the area of the Frame that we were looking at. Add a Soundtrack, and Export to DV-AVI for Encore and then author - simple static Menus, then burn two DVD’s. Piece of cake.
    The editing went quickly, and all was fine. No need to Render, as it played back surprisingly well, and there were no real animations, or even many Transitions.
    I was working on the laptop, which is quite stout and the Project was on my E:\ internal, with media on D:\. OK, the first couple of Timelines, some shorter ones, Exported fine, albeit slowly. Then, I hit a wall. The longer Timelines were taking forever. Two of the longer ones crashed PrPro, and that never happens. I had not bothered to kill the normal processes, that I normally have at boot-up, and was using my browser to read the Adobe fora. Shut down, rebooted, killed loaded processes (as I normally do, but I was still in that bad mood, so wanted to multi-task and be online), and went back to that problematic Timeline. Man, this was taking forever and on a fast laptop. This one completed, but the next long one crashed PrPro once again.
    In disgust, I packaged everything up on an external, and dragged it to the workstation. Killed all unnecessary Processes, and then re-linked all Assets. Save_As and went back to Exporting. Dang if I didn’t have two more crashes, with one corrupted PRPROJ file along the way. My mood was not improving, but I got through the task. The longer Timelines were taking about 4:1, or 6:1 to Export. Since I normally work only with DV-AVI, real time, or better is what I am used to. Even material with a bunch of Effects does not take THIS long.
    When it completed, I went about authoring, and while Encore was Transcoding and burning, I went back to the laptop. Instead of working with those WMV’s, I loaded up my conversion program, DigitalMedia Converter, and converted everything to 720x480, leaving the original PAR alone and Exported to DV-AVI. I replaced my WMV Assets with these AVI’s, and did the Cropping and some now slight resizing, as I was at least in the “ballpark” with my Frame Sizes. Used the same Titles and Soundtracks, and basically repeated my Trimming to approximately the same as the original Project. Cleaned up everything, and tested an Export for some of the longer Timelines/Sequences. Wow, things flew with not one crash. Did the Export for the rest and they also worked fine, with no issues.
    The conversion time for all of the Assets was just over 30 mins. The Export time was about 20% of what it had been, when using the WMV’s with more Scaling done. Crops, etc., were just about the same, as were the Position changes to accommodate the Crops. The laptop did not crash once, even though I did not kill Processes, and was back online.
    I had shot myself squarely in the foot. While the WMV’s did Import fine, there was a ton more processing, that PrPro had to do with them. Also, by setting my Frame Size in the converter, there were fewer Scaling Effects that needed to be applied. In the end, this “test” version completed in about 1/3 of the total time for the first. There were zero crashes, and I wasn’t even pushing the laptop. Though I espouse conversion, prior to Import, to others, I had broken that rule for myself, and I paid the price.
    Lessons learned:
    1.) do not start any Project with a bad mind set
    2.) do not deviate from standard accepted practice - convert first, regardless. Any time saved initially is likely to be lost, and by a factor of 300%.
    Just some observations, that I wanted to share with others. I should have known better, especially as I tell others to follow the advice to convert externally.
    Hunt

    Glenn,
    Yes, that is something that I am supposed to "know," and know well, at least judging by my myriad responses to others - CONVERT that footage. Shear laziness, and a poor mindset, bit me big time. I'm still removing egg from my face...
    Hunt

  • Slow render times with large jpegs - complete system lag

    In a project i'm working on I have two large jpegs with a small zoom scaling effect. Going from 100 to 103 percent.
    I've noticed that both Adobe Media Encoder and Premiere Pro experience a heavy slow down in render time as soon as the jpegs have to be rendered.
    Not only does the render speed almost come to a halt, the complete system lags very heavy, even the mouse cursor won't respond well.
    This happens when i have GPU acceleration enabled and when i do a 2 pass H264 encoding.
    When I have the GPU acceleration disabled the render goes very smooth, and doesn't seem to slow down...
    The jpeg is 4023  x 2677, and 6,97 MB large.
    Scaling the jpeg down to about 1920x1080 in Photoshop and put that one in the timeline made the render go a lot faster.
    I understand that a large picture takes a bit more time to be rendered, but we're talking about a 10minute render whit the large jpeg file and  a 2 minute render with the jpeg resized.
    The total time of the two jpegs in the video is 5 seconds in a 3 minutes video.
    So, that made me think that the render times are exponentially long.
    In the timeline everything runs really smooth.
    Is this considered normal, I can't remember having such big differences in CS5. It's not a major thing, but I wanted to share anyway.
    My system:
    Premiere Pro CC (latest)
    i7 4930K
    32 GB RAM
    2xGTX480
    Footage and project on a Raid0 disk
    Previews/Cache on a Raid0 disk
    System and Premiere on SSD
    Render to a single 7200 rpm drive.

    >wanted to share
    Yes... known issue... I think some of the below is about P-Elements, but the same ideas
    Photo Scaling for Video http://forums.adobe.com/thread/450798
    -HiRes Pictures to DVD http://forums.adobe.com/thread/1187937?tstart=0
    -PPro Crash http://forums.adobe.com/thread/879967

  • Who's Up for a Challenge? (or who needs a good Color Picker?)

    Greetings,
    I got lost in the muck trying to figure out how to make this color-picker code initialize with the last chosen color.... This is an open source project, and I posted my predicament on the blog for it, but it's been a few weeks and no one has responded. I've been able to integrate the code with my project no problem, it's just figuring out how to change this one behavior... the startup color seems to be hardcoded in several different places...
    Seems like there's some folks here who enjoy a good challenge, so I thought I'd see if anyone might want to give it a shot.... I'm probably making it much more complicated than it is by starting from the wrong vantage point....
    The Blog: http://www.v-vent.com/blog/?p=27
    The Code: http://www.v-vent.com/source/hue/veventhuesource.zip
    Any clues you have to offer would be greatly appreciated.... the idea seems simple enough....currently starts on yellow every time you load the view... would like it to start on the last color chosen, which is getting stored in user defaults....

    Ok John, here are each of the three files I touched:
    // ColorPickerViewController.m
    #import "ColorPickerViewController.h"
    #import "ColorPickerView.h"
    #import "AboutScreenViewController.h"
    @implementation ColorPickerViewController
    @synthesize aboutScreenViewController;
    // --> added const decl
    NSString *const keyForHue = @"hue";
    NSString *const keyForSat = @"sat";
    NSString *const keyForBright = @"bright";
    // --> register default settings
    - (void)registerDefaults {
    NSMutableDictionary *defaultValues = [NSMutableDictionary dictionary];
    [defaultValues setObject:[NSNumber numberWithFloat:0.5] forKey:keyForHue];
    [defaultValues setObject:[NSNumber numberWithFloat:0.5] forKey:keyForSat];
    [defaultValues setObject:[NSNumber numberWithFloat:0.5] forKey:keyForBright];
    [[NSUserDefaults standardUserDefaults] registerDefaults:defaultValues];
    - (void)viewDidLoad {
    [super viewDidLoad];
    NSLog(@"CALL ME ! " );
    [self registerDefaults]; // <-- register default settings
    NSUserDefaults *saveColors = [NSUserDefaults standardUserDefaults];
    ColorPickerView *theView = (ColorPickerView*) [self view];
    // --> removed key existance test and explicit defaults from this block
    // since defaults are now registered
    [theView setCurrentHue:[saveColors floatForKey:keyForHue]];
    [theView setCurrentSaturation:[saveColors floatForKey:keyForSat]];
    [theView setCurrentBrightness:[saveColors floatForKey:keyForBright]];
    AboutScreenViewController *abouter = [[AboutScreenViewController alloc]
    initWithNibName:@"AboutScreenView" bundle:nil];
    self.aboutScreenViewController = abouter;
    [abouter release];
    [theView onViewDidLoad]; // <-- added
    - (void) viewWillDisappear :(BOOL)animated {
    NSUserDefaults *saveColors = [NSUserDefaults standardUserDefaults];
    ColorPickerView *theView = (ColorPickerView*) [self view];
    [saveColors setFloat:[theView currentHue] forKey:keyForHue];
    [saveColors setFloat:[theView currentSaturation] forKey:keyForSat];
    [saveColors setFloat:[theView currentBrightness] forKey:keyForBright];
    - (UIColor *) getSelectedColor {
    return [(ColorPickerView *) [self view] getColorShown];
    - (void)didReceiveMemoryWarning {
    [super didReceiveMemoryWarning]; // Releases the view if it doesn't have a superview
    // Release anything that's not essential, such as cached data
    - (IBAction) pressedAboutButton {
    [self.view addSubview:self.aboutScreenViewController.view];
    [self.view bringSubviewToFront:self.aboutScreenViewController.view];
    - (void)dealloc {
    [super dealloc];
    [aboutScreenViewController release];
    @end
    // ColorPickerView.h
    #import <UIKit/UIKit.h>
    @class GradientView;
    @interface ColorPickerView : UIView {
    GradientView *gradientView;
    UIImageView *matrixView; // <-- added
    // --> unused ivars
    // UIImage *backgroundImage; //Image that will sit in back on the view
    // UIImage *closeButtonImage; //Image for close button
    // UIImage *nextButtonImage; //Image for next button
    IBOutlet UIImageView *backgroundImageView;
    IBOutlet UIView *showColor;
    IBOutlet UIImageView *crossHairs;
    IBOutlet UIImageView *brightnessBar;
    IBOutlet UILabel *colorInHex;
    IBOutlet UILabel *Hcoords;
    IBOutlet UILabel *Scoords;
    IBOutlet UILabel *Lcoords;
    IBOutlet UILabel *Rcoords;
    IBOutlet UILabel *Gcoords;
    IBOutlet UILabel *Bcoords;
    //Private vars
    // --> ok, private.. but atm, the controller still needs to call getters
    // and setters for currentBrightness, currentHue, and currentSaturation
    @private
    // CGRect colorMatrixFrame; // <-- removed - using matrixView ivar instead
    CGFloat currentBrightness;
    CGFloat currentHue;
    CGFloat currentSaturation;
    UIColor *currentColor;
    // unused properties
    // @property (nonatomic,retain) UIImage *backgroundImage;
    // @property (nonatomic,retain) UIImage *closeButtonImage;
    // @property (nonatomic,retain) UIImage *nextButtonImage;
    @property (nonatomic,retain) GradientView *gradientView;// <-- added
    @property (nonatomic,retain) UIImageView *matrixView; // <-- added
    @property (readwrite) CGFloat currentBrightness;
    @property (readwrite) CGFloat currentHue;
    @property (readwrite) CGFloat currentSaturation;
    - (UIColor *) getColorShown;
    - (void) onViewDidLoad; // <-- added
    @end
    // ColorPickerView.m
    #import "ColorPickerView.h"
    #import "GradientView.h"
    #import "Constants.h"
    // --> declare private properties, methods and functions
    @interface ColorPickerView ()
    @property (nonatomic,retain) UIColor *currentColor;
    - (void) getStringForHSL : (CGFloat) hue : (CGFloat) sat : (CGFloat) bright;
    - (void) getStringForRGB :(CGColorRef) theColor;
    - (NSString *) hexStringFromColor : (CGColorRef) theColor;
    static int myRoundOff(CGFloat value);
    @end
    @implementation ColorPickerView
    // --> unused properties
    // @synthesize backgroundImage;
    // @synthesize closeButtonImage;
    // @synthesize nextButtonImage;
    @synthesize gradientView; // <-- added
    @synthesize matrixView; // <-- added
    @synthesize currentHue;
    @synthesize currentSaturation;
    @synthesize currentBrightness;
    @synthesize currentColor; // <-- added
    - (id)initWithCoder:(NSCoder*)coder {
    if (self = [super initWithCoder:coder]) {
    // --> changes to support gradientView, which is now a retaining property
    GradientView *gradView = [[GradientView alloc] initWithFrame:kBrightnessGradientPlacent];
    self.gradientView = gradView;
    [gradView release];
    // [gradientView setTheColor:
    // [UIColor yellowColor].CGColor]; // <-- fixed and moved to onViewDidLoad
    [self addSubview:gradientView];
    [self sendSubviewToBack:gradientView];
    // --> changes to support retaining property 'matrixView'
    // colorMatrixFrame = kHueSatFrame; // <-- removed colorMatrixFrame ivar
    UIImageView *hueSatImageView = [[UIImageView alloc] initWithFrame:kHueSatFrame];
    [hueSatImageView setImage:[UIImage imageNamed:kHueSatImage]];
    self.matrixView = hueSatImageView;
    [hueSatImageView release];
    [self addSubview:matrixView];
    [self sendSubviewToBack:matrixView];
    [self setMultipleTouchEnabled:YES]; // <-- moved to keep similar blocks together
    // currentBrightness = kInitialBrightness; // <-- removed
    // currentColor = [[UIColor alloc]init]; // <-- fixed and moved to onViewDidLoad
    return self;
    // --> several of the ivars in this class should be moved to the controller -
    // for now this method should be called at the end of the controller's viewDidLoad method
    - (void)onViewDidLoad {
    self.currentColor = [UIColor colorWithHue:currentHue
    saturation:currentSaturation
    brightness:currentBrightness
    alpha:1.0];
    [showColor setBackgroundColor:currentColor];
    [self getStringForRGB:currentColor.CGColor];
    [self getStringForHSL:currentHue :currentSaturation :currentBrightness];
    [colorInHex setText:[self hexStringFromColor:currentColor.CGColor]];
    NSLog(@"%s: hue=%1.2f sat=%1.2f bright=%1.2f",
    _func_, currentHue, currentSaturation, currentBrightness);
    - (NSString *) hexStringFromColor : (CGColorRef) theColor {
    const CGFloat *c = CGColorGetComponents(theColor);
    CGFloat r, g, b;
    r = c[0];
    g = c[1];
    b = c[2];
    // Fix range if needed
    if (r < 0.0f) r = 0.0f;
    if (g < 0.0f) g = 0.0f;
    if (b < 0.0f) b = 0.0f;
    if (r > 1.0f) r = 1.0f;
    if (g > 1.0f) g = 1.0f;
    if (b > 1.0f) b = 1.0f;
    // Convert to hex string between 0x00 and 0xFF
    return [NSString stringWithFormat:@"#%02X%02X%02X",
    // --> using myRoundOff instead of int typecast
    myRoundOff(r * 255), myRoundOff(g * 255), myRoundOff(b * 255)];
    // --> use this if needed to fudge extrema
    static int myRoundOff(CGFloat value) {
    return lround(value);
    - (void) getStringForHSL : (CGFloat) hue : (CGFloat) sat : (CGFloat) bright { // <-- CGFloat params
    // NSLog(@"%s: hue=%1.4lf sat=%1.4lf bright=%1.4lf", _func_, hue, sat, bright);
    // --> using myRoundOff instead of int typecast
    [Hcoords setText:[NSString stringWithFormat:@"%d",myRoundOff(hue*255)]];
    [Scoords setText:[NSString stringWithFormat:@"%d",myRoundOff(sat*255)]];
    [Lcoords setText:[NSString stringWithFormat:@"%d",myRoundOff(bright*255)]];
    - (void) getStringForRGB :(CGColorRef) theColor {
    const CGFloat *c = CGColorGetComponents(theColor);
    CGFloat r, g, b;
    r = c[0];
    g = c[1];
    b = c[2];
    // --> using myRoundOff instead of int typecast
    [Rcoords setText:[NSString stringWithFormat:@"%d",myRoundOff(r*255)]];
    [Gcoords setText:[NSString stringWithFormat:@"%d",myRoundOff(g*255)]];
    [Bcoords setText:[NSString stringWithFormat:@"%d",myRoundOff(b*255)]];
    - (void) updateHueSatWithMovement : (CGPoint) position {
    // --> correcting currentHue and currentSaturation calculations
    // currentHue = (position.x-kXAxisOffset)/kMatrixWidth;
    // currentSaturation = 1.0 - (position.y-kYAxisOffset)/kMatrixHeight;
    CGPoint ptInMatrix = [self convertPoint:position toView:matrixView];
    currentHue = ptInMatrix.x/(matrixView.frame.size.width-1);
    currentSaturation = 1.0 - ptInMatrix.y/(matrixView.frame.size.height-1);
    // printf("hue Of the touch is : %f
    ",currentHue);
    // printf("sat Of the touch is : %f
    ",currentSaturation);
    UIColor *forGradient = [UIColor colorWithHue:currentHue
    saturation:currentSaturation
    brightness: kInitialBrightness
    alpha:1.0];
    [gradientView setTheColor:forGradient.CGColor];
    [gradientView setupGradient];
    [gradientView setNeedsDisplay];
    self.currentColor = [UIColor colorWithHue:currentHue // --> using setter to retain color
    saturation:currentSaturation
    brightness:currentBrightness
    alpha:1.0];
    [showColor setBackgroundColor:currentColor];
    [colorInHex setText:[self hexStringFromColor:currentColor.CGColor]];
    [self getStringForRGB:currentColor.CGColor];
    [self getStringForHSL:currentHue :currentSaturation :currentBrightness];
    - (void) updateBrightnessWithMovement : (CGPoint) position {
    // --> correcting currentBrightness calculation
    // currentBrightness = 1.0-(position.x/gradientView.frame.size.width) + kBrightnessEpsilon;
    CGPoint ptInGradient = [self convertPoint:position toView:gradientView];
    currentBrightness = 1.0 - ptInGradient.x/(gradientView.frame.size.width-1);
    // printf("Brightness Of the touch is : %f
    ",currentBrightness);
    // --> setting and using currentColor ivar instead of local var
    self.currentColor = [UIColor colorWithHue:currentHue
    saturation:currentSaturation
    brightness:currentBrightness
    alpha:1.0];
    [showColor setBackgroundColor:currentColor];
    [colorInHex setText:[self hexStringFromColor:currentColor.CGColor]];
    [self getStringForRGB:currentColor.CGColor];
    [self getStringForHSL:currentHue :currentSaturation :currentBrightness];
    //Touch parts :
    // Scales down the view and moves it to the new position.
    - (void)animateView:(UIImageView *)theView toPosition:(CGPoint) thePosition
    [UIView beginAnimations:nil context:NULL];
    [UIView setAnimationDuration:kAnimationDuration];
    // Set the center to the final postion
    theView.center = thePosition;
    // Set the transform back to the identity, thus undoing the previous scaling effect.
    theView.transform = CGAffineTransformIdentity;
    [UIView commitAnimations];
    -(void) dispatchTouchEvent:(CGPoint)position
    if (CGRectContainsPoint(matrixView.frame,position)) // <-- colorMatrixFrame ivar was removed
    // NSLog(@"Color!");
    // printf("X Of the touch in grad view is : %f
    ",position.x);
    // printf("Y Of the touch in grad view is : %f
    ",position.y);
    [self animateView:crossHairs toPosition: position];
    [self updateHueSatWithMovement:position];
    else if (CGRectContainsPoint(gradientView.frame, position))
    // NSLog(@"Bright!");
    CGPoint newPos = CGPointMake(position.x,kBrightBarYCenter);
    [self animateView:brightnessBar toPosition: newPos];
    [self updateBrightnessWithMovement:position];
    else
    // printf("X Of the touch in grad view is : %f
    ",position.x);
    // printf("Y Of the touch in grad view is : %f
    ",position.y);
    // Handles the start of a touch
    - (void)touchesBegan:(NSSet *)touches withEvent:(UIEvent *)event {
    for (UITouch *touch in touches) {
    [self dispatchTouchEvent:[touch locationInView:self]];
    // printf("X IS %f
    ",[touch locationInView:self].x);
    // printf("Y IS %f
    ",[touch locationInView:self].y);
    // Handles the continuation of a touch.
    - (void)touchesMoved:(NSSet *)touches withEvent:(UIEvent *)event
    for (UITouch *touch in touches){
    [self dispatchTouchEvent:[touch locationInView:self]];
    - (void)drawRect:(CGRect)rect {
    // --> corrected calculation of crosshairs.center
    CGFloat x = currentHue * matrixView.frame.size.width;
    CGFloat y = (1 - currentSaturation) * matrixView.frame.size.height;
    CGPoint ptInMatrix = CGPointMake(x, y);
    crossHairs.center = [matrixView convertPoint:ptInMatrix toView:self];
    // --> corrected calculation of brightnessBar.center
    x = (1 - currentBrightness) * gradientView.frame.size.width;
    y = gradientView.frame.size.height/2 - 3;
    CGPoint ptInGradient = CGPointMake(x, y);
    brightnessBar.center = [gradientView convertPoint:ptInGradient toView:self];
    // NSLog(@"%s: gradientView.frame=%@", _func_, NSStringFromCGRect(gradientView.frame));
    // NSLog(@" brightnessBar.center=%@", NSStringFromCGPoint(brightnessBar.center));
    UIColor *forGradient = [UIColor colorWithHue:currentHue // added
    saturation:currentSaturation
    brightness: kInitialBrightness
    alpha:1.0];
    [gradientView setTheColor:forGradient.CGColor]; // added
    [gradientView setupGradient];
    [gradientView setNeedsDisplay];
    [colorInHex setFont:[UIFont fontWithName:@"helvetica" size:16]];
    [self sendSubviewToBack:showColor];
    - (UIColor *) getColorShown {
    // NSLog(@"Are we here ? ");
    return [UIColor colorWithHue:currentHue saturation:currentSaturation
    brightness:currentBrightness alpha:1.0];
    - (void)dealloc {
    [currentColor release]; // <-- added
    [gradientView release]; // <-- added
    [matrixView release]; // <-- added
    [super dealloc];
    @end
    Disclaimer: While the above is working, tested code, the files are not meant to be examples of good practice. The objective was to hose out most of the functional bugs while changing the old files as little as possible. This is usually the best first step in cleaning up a project, since it allows the original programmers to see the changes in the context of the existing structure. Those changes can be much more difficult to see after a complete overhaul. Improving the structure will also change the nib files, and describing those changes in the forum can be tedious.
    Thus I perpetuated the structural weaknesses instead of moving most of the ivars, along with the code that administers them, into the ColorPickerViewController class. A number of useless but harmless artifacts were also left in the files.
    Most of my tests were only for functionality on the simulator. Though I tried to take care of memory management in the code I added or changed, there's lots of memory management clean up to do. I did some brief tests on a first gen iPod Touch with iOS 3.12, and at first glance I was surprised how well things seemed to be working. I was even able to position the crosshairs in a couple corners after a few tries (e.g. at full brightness, the upper-right corner should be HSL: 255, 255, 255; RGB: 255, 0, 0). All four of these extrema are reachable on the simulator, and if you have steady hands and/or small fingers, they're probably all reachable on an iPhone as well.
    Enjoy!
    - Ray

  • Scale image from small to large(r) without losing resolution

    Does anyone know how I can create a "scale action" of an image on a slide from small to large without losing the resolution of the image. Now, when I reduce the size of an image as a starting size and use Scale from the inspector to scale the image to e.g. 200% the images looks very blurred. I want the image in the larger form to have a good resolution.
    Thanks for your help.

    That's an interesting bug you've identified -- an image that is reduced by 50% and then scaled up to 200% with a Scale action looks blurrier than the original image at 100%. It seems like Keynote is scaling up the reduced image, rather than "removing the reduction" on the original.
    One solution that works well is to make a copy of your original image at the final size you want the scaled image to be, then place this copy on top of the scaling image, and build it in immediately after the scaling action with a dissolve build in that starts automatically after the scaling action. What this will do is give you the scaling effect, but at the final size, the full(er) resolution version will dissolve on top of the lower-res version. This procedure is more cumbersome than having the scaling effect work properly, but the result is quite acceptable, and the second dissolve build is pretty much imperceptible.

  • Why is my video quality so bad?

    So I have this video which is just over 1GB and it's just under 6 mins, so surely the quality should be better than this? It was shot in 1080p with a Canon 7D. I have however scaled it up 150% using the scaling effect in Premiere Pro. Should I scale it a different way?

    The AE (Detail preserving upscale effect) worked perfectly. It's actually very effective at maintaining the quality even when scaled up 150%

Maybe you are looking for