What are color adjustment

what are color adjustments

They are operations (both useable as destructive Adjustments and Adjustment Layers) that change the values (depending on the Color Mode of the image RGB, CMYK, Lab, grayscale) of pixels in an image based on user input both in the form of the settings of the respective Adjustment and Selections/Layer Masks/Layer settings.

Similar Messages

  • What are Color Moods and how can I use them?

    Color Moods allow you to select color themes from an image based on a pre-set mood.  Moods can be accessed by tapping on the flower icon after you take a picture. The preset Color Moods are: colorful, bright, muted, deep, dark, custom. You can experiment with each mood to see different color themes.
    As soon as you move one of the cursors on the image, the mood setting changes to Custom. The custom Mood allows you to select specifc colors.

    how would i make a server applet that can be accesed by 2 specific pll or random which ever makes it easier for the time being i just want 2 ppl to have acces to one applet and have a variable like a paddle in pong under each persons controll

  • Exporting photos for UHDTV or Native 4K TV, what are the best settings ? (File: Quality File: Color Space, Image Sizing and resolution)   Or in other words; How can I get the smallest files but keep good quality for display on new UHDTV

    Exporting photos for UHDTV or Native 4K TV, what are the best settings ? (File: Quality File: Color Space, Image Sizing and resolution)   Or in other words; How can I get the smallest files but keep good quality for display on new UHDTV

    You're welcome, and thank you for the reply.
    2) Yesterday I made the subclips with the In-Out Points and Command-U, the benefit is that I've seen the clip before naming it. Now I'm using markers, it's benefit is that I can write comment and (the later) clip name at once, the drawback is that I have to view to the next shot's beginning before knowing what the shot contains.
    But now I found out that I can reconnect my clips independently to the format I converted the master clip to. I reconnected the media to the original AVI file and it worked, too! The more I work with, the more I'm sold on it... - although it doesn't seem to be able to read and use the date information within the DV AVI.
    1) Ok, I tried something similar within FCE. Just worked, but the file size still remains. Which codec settings should I use? Is the export to DV in MOV with a quality of 75% acceptable for both file size and quality? Or would be encoding as H.264 with best quality an option for archiving, knowing that I have to convert it back to DV if I (maybe) wan't to use it for editing later? Or anything else?
    Thank's in advance again,
    André

  • Apple TV: what are the specific settings I should adjust to?

    Hi, there
    I really need your help now. I use a DVD ripper to rip DVD to MP4 for Apple TV. I am trying to achieve quality that is close to a movie (m4v) from iTunes. What are the best settings to get this type of quality? I am not concerned with output file size, and I just want to get the very best quality I can. If so, what are the specific settings I should adjust to? The program I am using allows me to adjust video and audio parameters as below:
    Video parameters:
    Codec: h.264
    Resolution: 1280*720
    Bit rate: ??? (it is said Up to 5 Mbps, but what is the specific bit rate?)
    Frame rate: 24 fps
    Audio parameters:
    Codec: aac
    Sample rate: ???
    Bit rate: ??? it is said 16 to 320 Kbps, but what’s the specific figure?
    Audio channel: mono, stereo and 5.1 channel, which one should I choose?
    Following are the tech specifications I copied from Apple’s official website:
    Video formats supported
    H.264 and protected H.264 (from iTunes Store): Up to 5 Mbps, Progressive Main Profile (CAVLC) with AAC-LC audio up to 160 Kbps (maximum resolution: 1280 by 720 pixels at 24 fps, 960 by 540 pixels at 30 fps) in .m4v, .mp4, and .mov file formats
    iTunes Store purchased video: 320 by 240 pixels, 640 by 480 pixels, 720 by 480 pixels (anamorphic), or high-definition 720p
    MPEG-4: Up to 3 Mbps, Simple Profile with AAC-LC audio up to 160 Kbps (maximum resolution: 720 by 432 pixels at 30 fps) in .m4v, .mp4, and .mov file formats
    Audio formats supported
    AAC (16 to 320 Kbps); protected AAC (from iTunes Store); MP3 (16 to 320 Kbps); MP3 VBR; Apple Lossless; AIFF; WAV; Dolby Digital 5.1 surround sound pass-through
    And I have selected some parameters according to this, please see the above contents, but there is no info about specific video/audio bit rate, audio sample rate, and audio channel. I just wanna know if I want to watch the movie on my 1920×1080 TV, what are the specific settings I should adjust to?
    Any suggestion is appreciated. Thanks in advance.

    Well, then how about playback Apple TV uncompatible video files? I have some other video files(such as avi, mkv,not DVD), and I also have a video converter, i know i can convert them to m4v, mp4, or mov that supported by ATV,but the thing is that i still don't know the best specific settings for conversion. Any suggestion? Many thanks for your kind reply.

  • What are the drawbacks of Selective color vs. curves?

    What are the drawbacks of Selective color vs. curves?

    There are no drawbacks to selective color that I can think of. The alternative is indiscriminate, wanton color which, as we all know, can get unruly and aggressive.
    Similarly there are only advantages to curves, especially on the right body. The era of stick figure beauty is thankfully long past. Our culture now appreciates the organic esthetic of curves.
    Beyond this, you may wish to consult the Photoshop forum. I suspect you'll get a very different answer there.

  • What are they mean for the colors which are present in RPD

    Hai
    In RPD we will find different colors right side to the databases,tables like green ,sky blue , marked as red in middle , yellow , given sysmbol like Stop with red color. Please any can give me brief idea for what they are indicated in different colors
    Thank you
    manu

    Hi
    Thank you..
    Yes i am asking about Colors to icons in RPD,in phsical layer , presentation layer, BUsiness model layer
    There are colors for icons like blue , yellow, etc...
    what are they mean with the color
    can you tell me please about this

  • What are Layers? And why do I need them?

    WHAT ARE LAYERS? AND WHY DO I NEED THEM?
    Layers are an essential part of Photoshop. With Layers you can separate pictures or design elements from each other, as if they are stacked on pieces of glass. With all elements separate, you can move or change them independent of each other.
    Layers are used for many tasks, including improving your images' color or tone; merging two or more images in one Photoshop file; and creating Web designs and animations.
    LAYER BASICS - VIDEO 06:41 min.
    WORKING WITH LAYERS - VIDEO 11:16 min.
    KEY CONCEPT: LAYER
    PHOTOSHOP/ LAYERS BASICS - Reference Guide

    After creating the mask and applying adjustment, you can also adjust and change layer mask using selection tools or, the most common way, using brush tools.
    To have a more accurate preview of what are you doing, Alt + click on the layer mask thumbnail to show the mask in the image area.
    At this point, you will have a layer mask on your screen in large view, so it is easy to fine tune it, but you wont see how that affects your image.
    To seean  instant preview how changes on layer mask affects the adjustments, use New Window for (name of your image) from Window > Arrange.
    Here is a more detailed tutorial on the topic: New Window for.. Command in Adobe Photoshop.

  • FAQ: What are the JDI (Just Do It) features in Photoshop?

    What are JDI features?  They're "Just Do It" features: small features that don't take a lot of time to implement or test and seem like an obvious improvement.
    JDI list for Photoshop CC
    JDI features in Photoshop CS6, by category:
    Automation
    Contact Sheet II has been restored as an Automate option
    PDF Presentation and Layer Comps to PDF have been restored as Automate options
    Brushes
    Add ability to record brush strokes in actions with "Allow Tool Recording" option
    Brightness/contrast slider for textures when painting
    Brush projection for static tips
    Brush tip cursor reflects brush pose and jitter for round and captured tips
    HUD brush resize and hardness can now change opacity - [Control] + [Option] + click drag up/down with General>Preferences> "Vary Round Brush Hardness based on HUD vertical movement" unchecked
    Increase maximum brush size to 5000px
    Change color dynamics to per stroke instead of per tip (user option for old behavior)
    Channels
    Enable Split Channels for documents with single layer (so you can split simple transparency)
    Color Picker
    allow clipboard paste into hex field with # in contents (i.e. #aabbcc), or 0x (i.e. 0xAABBCC)
    allow shortcut hex values (i.e. #123)
    Eyedropper
    Add ignore adjustment layers options bar item for the eyedropper
    New mode for eyedropper to select layers current and below
    Show the sample size popup for the various eyedropper tools (black point, white point, etc.)
    File Formats
    Allow for reading more bit depths in TIFF files
    Give the user choices regarding how they want transparency treated in OpenEXR on file open and save
    Read BIGTIFF format (TIFF files over 4 Gig)
    Read common stereo image pair formats (JPS, MPO, PNS)
    GPU
    Increased GPU stability by prequalifying GPUs on the fly before use
    Grammar
    Grammar policed throughout app
    Use consistent grammar style in the title of dialog windows (no commands such as "Choose a color:")
    Image Resizing
    Auto-select the best resample method based on the type of resize (bicubic-automatic)
    Importing
    (Macintosh only) Import images from devices provides ImageKit scanning and camera acquisition support
    Layers
    Add bicubic sharper & bicubic smoother options when free transforming layers (menu in options bar)
    Add dither options to Layer Styles for Gradient Overlay and Gradient Stroke
    Allow 00 or Shift 00 to work when setting layer/fill opacity (previously no way to get 0%)
    Allow changing color labels on multiple layers at once
    Allow changing of blend modes for multiple layers at once
    Allow locking of multiple selected layers
    CMD+J to duplicate selected layers and layer groups (in addition to layers)
    Layer tooltips to include layer name (if defined)
    New command to rasterize layer effect into layer, merging the selected layers into themselves (Rasterize Layer Style)
    Opt+click on toggle arrows (groups and effects)in layer panel should close all targets
    Reorder effects in the layers palette to match the Z-order style/blend mode (bottom most effects in terms of blending order, drop shadow is below the other effects)
    Show blend if/Blending Effects badge on layer if they are not default values
    Show correct opacity and blend mode values for hidden layers
    Tab goes to next layer on inline layer rename, SHIFT + TAB goes to previous
    When creating a shape layer, the layer name should not be like "Shape 1" but instead reflect the tool named such as "Rectangle 1"
    Liquify
    Add option to load last mesh
    Increase maximum Liquify brush size to 15,000
    Resize Liquify brush with shortcuts: bracket keys [ ] now match same increments in Photoshop
    ctrl (win) / cmd (mac) switches to magnifying glass
    alt + right click + drag to change brush size (win)
    ctrl + alt + left click + drag  to change brush size (mac)
    Masks
    Enable Invert and Threshold adjustments for masks in 32-bit/channel
    Plugins
    Hold SHIFT during startup to disable Optional and 3rd party plugins
    Presets
    Add New Document presets for common devices (e.g. iPhone, iPad, etc.)
    Add new Gradient Map presets for traditional print toning and split-toning
    Sticky reorganization of tool presets (changes persist after relaunch)
    New HDR Pro presets from RC Concepcion and Scott Kelby
    Printing
    Add "Edit" button for the description field in the print dialog
    Allow print dialog and print preview window to be resized
    Allow user to change the "preview well" background color in the print dialog
    Allow user to manually position the printed area on the page
    Hide color profiles that are inappropriate for currently selected printer when using "Photoshop Manages Color"
    Reintroduce "Print selected area", allow user to modify selection in print dialog
    Save
    Add warning message that 16-bit images cannot display their file size in the Save as JPEG dialog
    SDK
    Add ability to access tool name associated with the tool preset name via scripting
    Add the ability to return an array of guides in a document from the scripting SDK
    Selections
    Make the marquee, lasso, and mask panel feather values support decimal places like the feather dialog
    Remember feather radius when showing dialog for selection from a path
    Transform
    Don't hide smart object icon when transforming a layer
    Improve dragging of vector curves
    Rotate 90 with even x odd pixel dimension to not land on a half pixel position
    Preference to disable auto-rotate on open
    Type
    Add command to insert "lorem ipsum" for type
    Added Gamma rendering parameter for better text rendering
    UI
    [Windows] New/open document to context click on a document tab (has always been on Mac, now Windows too)
    Add "Don't show again" checkbox to Purge warnings
    Remove the app bar and reduce the drag/app bar over 30%

    1. Mainstage - Even though I probably won't use Logic for live performance much, I love how simple, clean, and intuitive the interface looks. I will probably use this when composing as it seems to be one of the easiest ways to route drum pads, create keyboard layers, etc. really quickly, and the interface is very inviting.
    2. Delay designer looks really fun. I remember spending 30 minutes once in Sonar trying to get the stupid delay to do a really simple thing. I finally gave up and layered the audio data to make my own delay because it didn't give me enough control to make it happen in the plugin. It looks like I could have just drawn it into the Delay Designer and been done with it.
    3. Import from Garageband - Not a new feature, but I love using Garageband as a musical notepad when all I want to do is create something simple or jot down an idea. In this period, I don't need all the features of Logic, but I will eventually, and then I just open it up in Logic and get more advanced.

  • Vignetting added and color adjusted immediately post import into Lightroom5.

    Vignetting added and color adjusted immediately post import into lightroom5.
    My photos from my most recent trip, when imported into Lightroom, have a heavy vignette very close to all 4 corners of the photo, and seem to have some small adjustments being done to them immediately when I import. The thumbnail looks great, and when i import --> then select it to open it as if I was going to view it full size in Lightroom, it looks great [no vignetting or tone/color adjustment] for about 1-2 seconds while a 'loading' footer is shown, following which the color is slightly altered and the vignetting is added (at this point then the thumbnail changes as well). This is a significant and noticable change to the photo. The pictures also do not have these issues if I view them through any other software. I have Can any one help me figure out what is causing this and remove it?
    I shoot
    with a Sony Alpha6000
    shoot in RAW (.ARW)
    use the standard sony kit lens that comes with the camera bundle, lens SELP1650 (3.5-5.6/16mm-50mm)
    edit on Windows 7 64bit with Lightroom5
    and don't believe I've adjusted any camera settings since last taking pictures 1 week ago with the exact same lens. I looked at photos from my last trip (only one week ago), and none of them are having these or an alterations/changes upon import.
    I took over 300 photos last weekend wthout any sign of these issues post import
    Every single photo I took this weekend seems to have this same issue.
    Any help is appreciated!

    Vignetting added and color adjusted immediately post import into lightroom5.
    My photos from my most recent trip, when imported into Lightroom, have a heavy vignette very close to all 4 corners of the photo, and seem to have some small adjustments being done to them immediately when I import. The thumbnail looks great, and when i import --> then select it to open it as if I was going to view it full size in Lightroom, it looks great [no vignetting or tone/color adjustment] for about 1-2 seconds while a 'loading' footer is shown, following which the color is slightly altered and the vignetting is added (at this point then the thumbnail changes as well). This is a significant and noticable change to the photo. The pictures also do not have these issues if I view them through any other software. I have Can any one help me figure out what is causing this and remove it?
    I shoot
    with a Sony Alpha6000
    shoot in RAW (.ARW)
    use the standard sony kit lens that comes with the camera bundle, lens SELP1650 (3.5-5.6/16mm-50mm)
    edit on Windows 7 64bit with Lightroom5
    and don't believe I've adjusted any camera settings since last taking pictures 1 week ago with the exact same lens. I looked at photos from my last trip (only one week ago), and none of them are having these or an alterations/changes upon import.
    I took over 300 photos last weekend wthout any sign of these issues post import
    Every single photo I took this weekend seems to have this same issue.
    Any help is appreciated!

  • What are the technical specifications of the monitor Macbook

    What are the technical specifications of the monitor Macbook Pro 15 "and 17"
    The screen is IPS?
    Qawl the viewing angle?
    etc.

    For example:
    Monitor Size: 24 "LCD
    Maximum Resolution: 1920 x 1200 at 60 Hz
    Best: 1920x1200 at 60 Hz
    Viewable Image Size (VIS): 24 "
    Panel Technology: IPS
    Color Gamut: 110% (CIE1976) / 102% (1931) / 100% (sRGB coverage)
    Aspect Ratio: 16:10
    Dot Pitch: 0.270 mm
    Response Time: 6 ms Typical
    Brightness: 400 cd / m²
    Contrast Ratio: 1000:1 / 80,000:1 DCR
    Horizontal Viewing Angle: 178 ° / 178 °
    Connector Type Video Input: VGA, 2xDVI-D, S-Video,
    Composite Video, Component Video, DisplayPort, HDMI
    USB: Yes
    Card Reader 8 in 1: Yes
    Compatible with AX510 (Sound bar): Yes
    Compatible with VESA wall mount: Yes 100mm
    Screen Rotation: Yes
    Height Adjustment: Yes
    Compliance Energy Star: No

  • What are the ranges for correct skin tones using RGB%?

    What are the ranges for correct skin tones using RGB%?  Used to using a scale from 0 to 255.  But with LR it's RGB  , I know 100% RGB is white.  What do you use for %?

    While I whole heartedly agree that we should not be constrained to hard and fast numbers for accurate skin tones ... LR does offer an RGB color readout ... I am assuming they made those percentages available for the user to monitor the breakdown of specific color values for a reason ... so we could have an indication of how a specific color in an image will be reproduced ...
    I liken this to using a speedometer ... while many experienced drivers in well tuned vehicles can travel on the highway at the prescribed legal speed limit without really monitoring the readout on the dashboard ... however, there are times when they would like to verify the speed at which they are traveling ... the RGB color percentage readout in LR is no different ... just a source of information to verify you are achieving what you desire ...
    Again, going by specific numbers in this instance, I believe, could lead to problems ... there may be times when you may desire or actually need to adjust skin tones ... even though a pleasing WB has been achieved ... the relationship of R, G and B can be used to get you there.
    From what I have researched and put into practice with LR the following seems to be a good starting point and the data was borrowed from "the pixelation" blog:
    R: highest %
    G: middle %
    B: lowest %
    To get a little more specific. In general,
    R: Y + (15-20)
    G: average of R and B
    B: R – (15-20)
    For example, the following values represent common Caucasian skin tones using the rules above:
    * R: 80%; G: 70%; B: 60%. R is 20 points higher than B, and G is midway between R and B. That’s perfect.
    *  R: 86%, G: 78%; B: 70% also reflects a nicely balanced skin tone.  Again, G is midway between R and B, and R is 16 points higher than B. This, too, illustrates a great relationship among the colors.

  • Color Adjustment trouble

    hai,
    since yesterday, everytime I restart FCPX all my Color Adjustment pucks are set to -100% to all of my projects. I can see the images but they're uncorrected. When I move one of the pucks the image turns black until I've reset all of them to 0%. It's the weirdest thing, very bothering and time consuming.
    The latest update 10.0.8 is installed and I'm currently working on a project with Sony f5 material. Sony's new import plug-in is installed recently. I trashed my preferences but the problem is still there. I've also turned off all of the old projects with EventManagerX.
    I'd be very happy if anyone has an idea what I should do to solve this.
    thanx.

    Tom Wolsky, thnx for your reply
    i've been shooting HD (1920 x 1080 interlaced PAL) material on XAVC, not using proxy as the HD format is the proxy when shooting 4K with the Sony F5. the problem is: this situation doesn't only effect this project but the color adjustment pucks on all of the other projects are set to -100%, too. Fortunately non are important at this moment. my current project is, though, and I can't seem to return to the situation in which everything worked okay.
    you got a clue?
    again, thanks for your help.

  • Hi guru's what are the function modules are used in ALV

    hi guru's what are the function modules are used in ALV

    Hi vasu,
    There are some function modules which will enable to produce the  reports without much effort.
    All the definitions of internal tables, structures and constants are declared in a type-pool called SLIS.
    1. SIMPLE REPORT.
    The important function modules are
    a. Reuse_alv_list_display
    b. Reuse_alv_fieldcatalog_merge
    c. Reuse_alv_events_get
    d. Reuse_alv_commentary_write
    e. Reuse_alv_grid_display
    A. REUSE_ALV_LIST_DISPLAY : This is the function module which prints the data.
    The important parameters are :
    I. Export :
    i. I_callback_program : report id
    ii. I_callback_pf_status_set : routine where a user can set his own pf status or change the functionality of the existing pf status
    iii. I_callback_user_command : routine where the function codes are handled
    iv. I_structure name : name of the dictionary table
    v. Is_layout : structure to set the layout of the report
    vi. It_fieldcat : internal table with the list of all fields and their attributes which are to be printed (this table can be populated automatically by the function module REUSE_ALV_FIELDCATALOG_MERGE
    vii. It_events : internal table with a list of all possible events of ALV and their corresponding form names.
    II. Tables :
    i. t_outtab : internal table with the data to be output
    B. REUSE_ALV_FIELDCATALOG_MERGE : This function module is used to populate a fieldcatalog which is essential to display the data in ALV. If the output data is from a single dictionary table and all the columns are selected, then we need not exclusively create the field catalog. Its enough to mention the table name as a parameter(I_structure name) in the REUSE_ALV_LIST_DISPLAY. But in other cases we need to create it.
    The Important Parameters are :
    I. Export :
    i. I_program_name : report id
    ii. I_internal_tabname : the internal output table
    iii. I_inclname : include or the report name where all the dynamic forms are handled.
    II Changing
    ct_fieldcat : an internal table with the type SLIS_T_FIELDCAT_ALV which is
    declared in the type pool SLIS.
    C. REUSE_ALV_EVENTS_GET : Returns table of possible events for a list type
    Parameters :
    I. Import :
    Et_Events : The event table is returned with all possible CALLBACK events
    for the specified list type (column 'NAME'). For events to be processed by Callback, their 'FORM' field must be filled. If the field is initialized, the event is ignored. The entry can be read from the event table, the field 'FORM' filled and the entry modified using constants from the type pool SALV.
    II. Export :
    I_List_type :
    0 = simple list REUSE_ALV_LIST_DISPLAY
    1 = hierarchcal-sequential list REUSE_ALV_HIERSEQ_LIST_DISPLAY
    2 = simple block list REUSE_ALV_BLOCK_LIST_APPEND
    3 = hierarchical-sequential block list
    REUSE_ALV_BLOCK_LIST_HS_APPEND
    D. REUSE_ALV_COMMENTARY_WRITE : This is used in the Top-of-page event to print the headings and other comments for the list.
    Parameters :
    I. it_list_commentary : internal table with the headings of the type slis_t_listheader.
    This internal table has three fields :
    Typ : ‘H’ – header, ‘S’ – selection , ‘A’ - action
    Key : only when typ is ‘S’.
    Info : the text to be printed
    E. REUSE_ALV_GRID_DISPLAY : A new function in 4.6 version, to display the results in grid rather than as a preview.
    Parameters : same as reuse_alv_list_display
    This is an example for simple list.
    2. BLOCK REPORT
    This is used to have multiple lists continuously.
    The important functions used in this report are:
    A. REUSE_ALV_BLOCK_LIST_INIT
    B. REUSE_ALV_BLOCK_LIST_APPEND
    C. REUSE_ALV_BLOCK_LIST_HS_APPEND
    D. REUSE_ALV_BLOCK_LIST_DISPLAY
    A. REUSE_ALV_BLOCK_LIST_INIT
    Parameters:
    I. I_CALLBACK_PROGRAM
    II. I_CALLBACK_PF_STATUS_SET
    III. I_CALLBACK_USER_COMMAND
    This function module is used to set the default gui status etc.
    B. REUSE_ALV_BLOCK_LIST_APPEND
    Parameters :
    Export :
    I. is_layout : layout settings for block
    II. it_fieldcat : field catalog
    III. i_tabname : internal table name with output data
    IV. it_events : internal table with all possible events
    Tables :
    i. t_outtab : internal table with output data.
    This function module adds the data to the block.
    Repeat this function for all the different blocks to be displayed one after the other.
    C. REUSE_ALV_BLOCK_LIST_HS_APPEND
    This function module is used for hierarchical sequential blocks.
    D. REUSE_ALV_BLOCK_LIST_DISPLAY
    Parameters : All the parameters are optional.
    This function module display the list with data appended by the above function.
    Here the functions REUSE_ALV_FIELDCATALOG_MERGE, REUSE_ALV_EVENTS_GET, REUSE_ALV_COMMENTARY_WRITE can be used.
    3. Hierarchical reports :
    Hierarchical sequential list output.
    The function module is
    A. REUSE_ALV_HIERSEQ_LIST_DISPLAY
    Parameters:
    I. Export:
    i. I_CALLBACK_PROGRAM
    ii. I_CALLBACK_PF_STATUS_SET
    iii. I_CALLBACK_USER_COMMAND
    iv. IS_LAYOUT
    v. IT_FIELDCAT
    vi. IT_EVENTS
    vii. i_tabname_header : Name of the internal table in the program containing the
    output data of the highest hierarchy level.
    viii. i_tabname_item : Name of the internal table in the program containing the
    output data of the lowest hierarchy level.
    ix. is_keyinfo : This structure contains the header and item table field
    names which link the two tables (shared key).
    II. Tables
    i. t_outtab_header : Header table with data to be output
    ii. t_outtab_item : Name of the internal table in the program containing the
    output data of the lowest hierarchy level.
    slis_t_fieldcat_alv : This internal table contains the field attributes. This internal table can be populated automatically by using ‘REUSE_ALV_FIELDCATALOG_MERGE’.
    Important Attributes :
    A. col_pos : position of the column
    B. fieldname : internal fieldname
    C. tabname : internal table name
    D. ref_fieldname : fieldname (dictionary)
    E. ref_tabname : table (dictionary)
    F. key(1) : column with key-color
    G. icon(1) : icon
    H. symbol(1) : symbol
    I. checkbox(1) : checkbox
    J. just(1) : (R)ight (L)eft (C)ent.
    K. do_sum(1) : sum up
    L. no_out(1) : (O)blig.(X)no out
    M. outputlen : output length
    N. seltext_l : long key word
    O. seltext_m : middle key word
    P. seltext_s : short key word
    Q. reptext_ddic : heading (ddic)
    R. ddictxt(1) : (S)hort (M)iddle (L)ong
    S. datatype : datatype
    T. hotspot(1) : hotspot
    some theory regarding alv:
    This table tells ALV which events are processed by the caller by CALLBACK.
    The table of possible events per list type can be initialized using the module REUSE_ALV_EVENTS_GET.
    You can display the names of the constants in the type pools SLIS which represent the individual events using the individual test function in the function module
    REUSE_ALV_EVENT_NAMES_GET. Only events with a form routine name are processed.
    The table structure contains the fields:
    • IT_EVENTS-NAME
    Name of the Callback event.
    Possible Callback events:
    • Action
    USER_COMMAND USING R_UCOMM LIKE SY-UCOMM RS_SELFIELD TYPE SLIS_SELFIELD
    Process actions on the list
    As this is a frequently-used Callback event, the form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_USER_COMMAND.
    PF_STATUS_SET USING RT_EXTAB TYPE SLIS_T_EXTAB
    If a user list status is to be set, it must be done in the form routine assigned to this event. The ALV function codes, which must not be active, are in the Parameter RT_EXTAB. This table must be passed with the SET PF-STATUS command (with inactive user function codes as well, if necessary).
    The STANDARD status of the function group SALV should be used as a template for a user-specific status.
    As this is a frequently-used Callback event, its form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_PF_STATUS_SET.
    ITEM_DATA_EXPAND USING RS_SELFIELD TYPE SLIS_SELFIELD RFLG_ALL TYPE C
    Only relevant for hierarchical-sequential lists using the layout parameter IS_LAYOUT-EXPAND_FIELDNAME of the structure IS_LAYOUT.
    Exit for passing item entries (ITEM table) for a header record which was expanded interactively by the user.
    RS_SELFIELD-TABINDEX contains the header table index for which the item entries are to be put in the global item output table (T_OUTTAB_SLAVE). The Callback is only called if ALV has no items for a header which is to be expanded.
    RFLG_ALL is passed with 'X' if the user shows all items. The application must ensure that entries are not repeated in the item table. RS_SELFIELD is initial in this case.
    CALLER_EXIT USING RS_DATA Is called at the beginning of the function module to make special settings. It is not usually used.
    • List processing events
    IMPORTANT: The application Callback routine must not manipulate the internal output table and/or its header record. This restriction applies to all Callbacks which are called in the list output and run under the 'List processing events'.
    TOP_OF_LIST no USING parameter. Information output at the start of the list
    END_OF_LIST no USING parameter. Information output at the end of the list
    TOP_OF_PAGE no USING parameter
    Equivalent to the list processing TOP-OF-PAGE event
    END_OF_PAGE no USING parameter. Not available for hierarchical-sequential lists.
    Information output at the end of a page. This is only called for printing.
    TOP_OF_COVERPAGE no USING parameter
    The selection information and list status are output together (if they exist) on a separate page by default. See also the documentation of the parameters:
    IS_PRINT-NO_COVERPAGE
    IS_PRINT-NO_PRINT_SELINFOS
    IS_PRINT-NO_PRINT_LISTINFOS
    IS_LAYOUT-GET_SELINFOS
    The user can format the header area of the 'cover page' himself or herself by specifying a Callback routine for this event.
    END_OF_COVERPAGE no USING parameter
    Analogously to TOP_OF_COVERPAGE the user can add other information to the information output by ALV (selection information, list status) at this event.
    FOREIGN_TOP_OF_PAGE no USING parameter
    The Top-of-page event is always processed in ALV and is only passed to the caller via the Callback mechanism. This is still the case if the caller, e.g. by a user action, processes a branch list which was not formatted by ALV (e.g. a popup with additional information about the list record selected and displayed by ALV).
    In this case, top-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event top-of-page still occurs in ALV. When ALV notices a top-of-page which was not caused by an ALV output, the form routine in FOREIGN_TOP_OF_PAGE is called.
    FOREIGN_END_OF_PAGE no USING parameter
    The event end-of-page is always processed in ALV and only passed to the caller via callback. This is still the case, e.g. when the caller processes a details list which was not formatted by ALV (e.g. a popup with further information about selected list records which were displayed by ALV).
    In this case, end-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event end-of-page still occurs in ALV. When ALV notices an end-of-page that was not caused by an ALV output, the form routine in FOREIGN_END_OF_PAGE is called.
    BEFORE_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO
    Output information before each output line. Should only be used in justified cases because it costs a lot of performance.
    AFTER_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO
    Output information after each output line. Should only be used in justified cases because it costs a lot of performance.
    • Internal use only
    LIST_MODIFY USING R_TABNAME TYPE SLIS_TABNAME
    R_INDEX LIKE SY-TABIX
    R_INDEX_ITEM LIKE SY-TABIX
    R_INDEX_SUM LIKE SY-TABIX
    • IT_EVENTS-FORM
    Name of the form routine which should be called in the calling program at the event.
    Field_catalog:
    Field catalog with field descriptions
    2.7.1. Description
    Field catalog containing descriptions of the list output fields (usually a subset of the internal output table fields). A field catalog is required for every ALV list output.
    The field catalog for the output table is built-up in the caller's coding. The build-up can be completely or partially automated by calling the REUSE_ALV_FIELDCATALOG_MERGE module
    See also the documentation of the function module REUSE_ALV_FIELDCATALOG_MERGE.
    The minimal field catalog is documented under 'default'. The caller can use the other optional parameters to assign output attributes to a field which differ from the default.
    A field catalog need not be built-up and passed explicitly only under the following conditions:
    • The internal table to be output has the same structure as a Data Dictionary structure which is referred to in the internal table declaration using LIKE or INCLUDE STRUCTURE.
    • all fields in this structure are to be output
    • the structure name is passed to ALV in the parameter I_STRUCTURE_NAME.
    See also the documentation of the IMPORTING paramter I_STRUCTURE_NAME.
    Positioning
    • row_pos (row position)
    value set: 0, 1 - 3
    Only relevant if the list output is to be multi-line (two or three lines) by default.
    A multi-line list can also be defined by the user interactively if the default list is one-line.
    The parameter specifies the relative output line of the column in a multi-line list.
    • col_pos (column position)
    value set: 0, 1 - 60
    only relevant when the default relative column positions differ from the field catalog field sequence. The parameter specifies the relative column position of the field in the list output. The column order can be changed interactively by the user. If this parameter is initial for all field catalog entries, columns appear in the field catalog field sequence.
    Identification
    • fieldname (field name)
    value set: internal output table field name (required parameter)
    Name of the internal output table field which is described by this field catalog entry
    • tabname (internal output table)
    value set: SPACE, internal output table name
    This parameter is used in 'manual' field catalog build-up only for hierarchical-sequential lists.
    Name of the internal output table which contains the field FIELDCAT-FIELDNAME.
    Data Dictionary reference
    • ref_fieldname (reference field name)
    value set: SPACE, Data Dictionary field name
    Name of the Data Dictionary field referred to.
    This parameter is only used when the internal output table field described by the current field catalog entry has a reference to the Data Dictionary (not a program field), and the field name in the internal output table is different from the name of the field in the Data Dictionary. If the field names are identical, naming the Data Dictionary structure or table in the FIELDCAT-REF_TABNAME parameter is sufficient.
    • ref_tabname (reference table/structure field name)
    value set: SPACE, name of a Data Dictionary structure or table
    Structure or table name of the referred Data Dictionary field.
    This parameter is only used when the internal output table field described by the current field catalog entry has a Data Dictionary reference (not a program field).
    Reference to fields with currency/measurement unit
    Each internal output table sum or quantity field whose decimal places are to be formatted appropriately for the unit in the list must follow the convention:
    • the field is of data type QUAN or CURR (internal type P) (the field must really have this physical data type. Overwriting the physical data type with the parameter FIELDCAT-DATATYPE has no effect)
    • There is a field in the internal output table which contains the associated unit.
    • There is also an entry in the field catalog for the unit field.
    (If the unit is not to appear as a column in the list, and cannot be interactively displayed as a column, e.g. because it is always unambiguous and is therefore explicitly output by the caller in the list header, the field catalog units field entry can take the parameter FIELDCAT-TECH = 'X'.
    The association of a value field to a unit affects the output as follows:
    • appropriate decimal places display for the unit
    • an initialized field with a link to a non-initial unit is output as '0' for the unit (if FIELDCAT-NO_ZERO is initial). When this field is summed, this unit affects whether the units are homogeneous.
    • an initialized field with a link to an initial unit is output as SPACE. When this field is summed, the unit SPACE does not affect the homogeneity of the units.
    • When non-initial fields with an initial unit are summed, the unit SPACE is considered to be a unit.
    Link to currency unit
    • cfieldname (currency unit field name)
    value set: SPACE, output table field name
    Only relevant for amount columns with associated unit.
    Name of the internal output table field containing the currency unit associated with the amount field FIELDCAT-FIELDNAME. The field in FIELDCAT-CFIELDNAME must have its own field catalog entry.
    • ctabname (internal currency unit field output table)
    value set: SPACE, output table field name
    only relevant for hierarchical-sequential lists
    Name of the internal output table containing the FIELDCAT-CFIELDNAME field.
    Link to measurement unit
    • qfieldname (measurement unit field name)
    value set: SPACE, output table field name
    only relevant for quantity columns with unit link.
    Name of the internal output table field containing the measurement unit associated with the quantity field FIELDCAT-FIELDNAME.
    The field in FIELDCAT-QFIELDNAME must have its own field catalog entry.
    • qtabname (internal measurement unit field output table)
    value set: SPACE, output table field name
    only relevant for hierarchical-sequential lists
    Name of the internal output table containing the FIELDCAT-QFIELDNAME field.
    Column output options
    • outputlen (column width)
    value set: 0 (initial), n
    For fields with a Data Dictionary link this parameter can be left initial.
    For fields without a Data Dictionary link (program field) the parameter must be given the value of the desired field list output length (column width).
    initial = column width is the output length of the referred Data Dictionary field (domain).
    n = column width is n characters
    • key (key column)
    value set: SPACE, 'X' 'X' = kex field (key field output in color)
    Key fields can not be interactively hidden. Parameter FIELDCAT-NO_OUT must be left initial.
    For exceptions see the documentation of the FIELDCAT-KEY_SEL parameter.
    • key_sel (hideable key column)
    value set: SPACE, 'X'
    only relevant when FIELDCAT-KEY = 'X'
    Key field which can be hidden interactively.
    The key column sequence cannot be changed interactively by the user.
    The output is controlled by the FIELDCAT-NO_OUT parameter analogously to non-key fields.
    • no_out (field in field list)
    value set: SPACE, 'X' 'X' = field is not displayed in the current list.
    The user can interactively choose the field for output from the field list.
    The user can display the contents of these fields at line level using the 'Detail' function.
    See also the 'Detail screen' documentation of the parameter IS_LAYOUT.
    • tech (technical field)
    value set: SPACE, 'X' 'X' = technical field
    Field cannot be output in the list and cannot be displayed interactively.
    Field can only be used in the field catalog (not in IT_SORT, ...).
    • emphasize (highlight columns in color)
    value set: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off '1'=on)
    'X' = column is colored with the default column highlight color.
    'Cxyz' = column is colored with a coded color:
    • C: Color (coding must begin with C)
    • x: color number
    • y: bold
    • z: inverse
    • hotspot (column as hotspot)
    value set: SPACE, 'X'
    'X' = column cells are output as hotspots
    • fix_column (fix column)
    value set: SPACE, 'X'
    Not relevant for block lists (output of several lists consecutively)
    'X' = column fixed (does not scroll horizontally)
    All columns to be fixed must have this flag, starting from the left. If a column without this flag is output, only the columns to the left of this column are fixed. The user can change the column fixing interactively. See also the documentation of the Layout parameter
    IS_LAYOUT-NO_KEYFIX of the IMPORTING paramter IS_LAYOUT.
    • do_sum (sum over column)
    value set: SPACE, 'X' 'X' = a sum is to be calculated over this internal output table field.
    This function can also be called by the user interactively.
    • no_sum (sums forbidden)
    value set: SPACE, 'X' 'X' = no sum can be calculated over this field, although the data type of the field would allow summing.
    • input (column ready for input)
    Function not available
    Format column contents
    • icon
    value set: SPACE, 'X' 'X' = column contents to be output as an icon.
    The caller must consider the printability of icons.
    • symbol
    value set: SPACE, 'X' 'X' = column contents are to be output as a symbol.
    The internal output table column must be a valid symbol character.
    The caller must consider the printability of symbols.
    Symbols can usually be printed, but may not always be output correctly, depending on the printer configuration.
    • just (justification)
    value set: SPACE, 'R', 'L', 'C'
    Only relevant for fields of data type CHAR or NUMC
    ' ' = default justification for this data type
    'R' = right-justified output
    'L' = left-justified output
    'C' = centered output
    The justification of the column header always follows the justification of the columns. Independent justification of the column neader is not possible.
    • lzero (leading zeros)
    value set: SPACE, 'X'
    Only relevant for fields of data type NUMC
    ALV outputs NUMC fields right-justified without leading zeros by default.
    'X' = output with leading zeros
    Note: If a NUMC field is output left-justified or centered by FIELDCAT-JUST, leading zeros are output. If the output of leading zeros is suppressed by a Data Dictionary reference ALPHA conversion exit, the output is always left-justified.
    • no_sign (no +/- sign) Only relevant for value fields
    value set: SPACE, 'X' 'X' = value output without +/ sign
    • no_zero (suppress zeros) Only relevant for value fields
    value set: SPACE, 'X' 'X' = suppress zeros
    • edit_mask (field formatting)
    value set: SPACE, template
    template = see documentation of WRITE formatting option USING EDIT MASK template
    The output conversion conv can be made by template = '== conv'.
    Texts
    The following text parameters should be specified for program fields without a Data Dictionary reference. The texts are taken from the Data Dictionary for fields with a Data Dictionary reference. If this is not desired, the text parameters can also be specified. The Data Dictionary texts are then ignored. If the user changes the column width interactively, the column header text with the appropriate length is always used. The interactive function 'Optimize column width' takes account of both the field contents and the column headers: if all field contents are shorter than the shortest column header, the column width depends on the column header.
    The 'long field label' is also used in display variant definition, sort, etc. popups.
    • seltext_l (long field label)
    • seltext_m (medium field label)
    • seltext_s (short field label)
    • reptext_ddic (header)
    analogous to the Data element maintenance 'Header'
    The specified text is not necessarily output in the list, an optimum among all texts is sought.
    • ddictxt (specify text)
    value set: SPACE, 'L', 'M', 'S'
    You can specify with values 'L', 'M', and 'S', the keyword that should always be used as column header. If the column width changes, no attempt is made in this case to find an appropriate header for the new output width.
    Parameters for program fields without Data Dictionary reference
    see also 'Text' parameters
    • datatype (data type)
    value set: SPACE, Data Dictionary data type (CHAR, NUMC,...)
    Only relevant for fields without Data Dictionary reference
    Program field data type
    • ddic_outputlen (external output length)
    value set: 0 (initial), n
    Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.
    Prerequisites:
    • FIELDCAT-EDIT_MASK = '==conv'
    see also the documentation of the parameter FIELDCAT-EDIT_MASK
    • FIELDCAT-INTLEN = n
    see also the documentation of the parameter FIELDCAT-INTLEN
    n = external format field output length
    The column width FIELDCAT-OUTPUTLEN need not be the same as the external format output length (FIELDCAT-DDIC_OUTPUTLEN).
    • intlen (internal output length)
    value set: 0 (initial), n
    Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.
    Prerequisites:
    • FIELDCAT-EDIT_MASK = '==conv'
    see also the documentation of the parameter FIELDCAT-EDIT_MASK
    • FIELDCAT-DDIC_OUTPUTLEN = n
    see also the documentation of the parameter FIELDCAT-DDIC_OUTPUTLEN
    n = internal format field output length
    • rollname (data element)
    value set: SPACE, Data Dictionary data element name
    F1 help can be provided for a program field without a Data Dictionary reference, or F1 help which differs from the Data Dictionary help can be provided for a field with a Data Dictionary reference, using this parameter.
    When F1 help is called for this field, the documentation of the specified data element is displayed.
    If the FIELDCAT-ROLLNAME is initial for fields with a Data Dictionary reference, the documentation of the data element of the referred Data Dictionary field is output.
    Others
    • sp_group (field group key)
    value set: SPACE, CHAR(1)
    Field group key.
    Keys are assigned to group names in the IT_SPECIAL_GROUPS parameter (see also the documentation of the parameter IT_SPECIAL_GROUPS).
    When such an assignment is made in the field catalog and in IT_SPECIAL_GROUPS, the fields are grouped correspondingly in the display variant popup.
    • reprep (Report/Report interface selection criterion)
    value set: SPACE, 'X'
    Prerequisites:
    • The system contains the Report/Report interface (function group RSTI, table TRSTI)
    • Parameter LAYOUT-REPREP = 'X'
    (see also the documentation of the parameter LAYOUT-REPREP of the IMPORTING parameter IS_LAYOUT )
    'X' = When the Report/Report interface is called, the value of this field is passed in the selected interface start record as a selection criterion.
    2.7.2. Default
    • The following entries are usually sufficient for internal table fields with a reference to a field defined in the Data Dictionary :
    • fieldname
    • ref_tabname
    Notes:
    ALV gets the remaining information from the Data Dictionary.
    If no relative column position (COL_POS) is specified, the fields are output in the list in the order in which they were added to the field catalog.
    REF_FIELDNAME need only be specifid when the name of the internal table field differs from the name of the referred Data Dictionary field.
    Information which is explicitly entered in the field catalog is not overwritten by information from the Data Dictionary.
    Priority rule:
    Entries in the field catalog have priority over differing entries in the Data Dictionary.
    • The following entries are usually sufficient for internal table fields without a reference to the Data Dictionary (program fields):
    • fieldname
    • outputlen
    • datatype
    • seltext_s
    • seltext_m
    • seltext_l
    Notes:
    F1 help can be provided for program fields by assigning a data element to the parameter ROLLNAME.
    If the parameters SELTEXT_S, SELTEXT_M, SELTEXT_L, and REPTEXT_DDIC contain appropriate field labels, the program field column headers are also adjusted appropriately when the column width changes
    sites :
    http://www.sapdevelopment.co.uk/reporting/alv/alv_variousfcat.htm
    <b>plese reward if useful </b>
    Message was edited by:
            sunil kairam

  • Global color adjustment for an icon illustration?

    I've built an icon, using many component parts each with a different stroke and fill characteristics.
    I now want to change the overall color of the icon, without having to go in adjust each component part that makes up the icon. (In PS, for example. you can create an adjustment layer that will allow you to tweak the overall color of the layer below).
    Please advise.

    Well might it be possible to have a panel access the fill and stroke commands and which may have been omitted as a dialogue does not access that tool?
    Are you sure you are thinking of all the workflows that maybe around. Have you ever worked in an interior design firm, a large advertising agency, a corporate art department, a greeting card company's art department, a furniture company or for half the number of other types of large users of Illustrator? Perhaps you would be a little surprised at how much color does play a roll in the creation and production of anything you can do in Illustrator and times that by ten or twenty contributors on one project and changing color can be a night mare and it is done on moment notice. Ever work for a textile design studio, heaven help you if you have.
    many clients and art directors and designers are color obsessed. And once they all settle on the colors, get it even slightly wrong and see what happens.
    It is possible for many people that this has to be a panel and if you have read the forums and followed the threads in which people have been made aware of this feature they all wonder why one it is buried in the Edit Menu and why it is not somewhere that is more accessible.
    I respect your knowledge of Illustrator a great deal but this I think is not a well thought out conclusion on your part.
    Have a great day!

  • Automatic color adjustment on different monitors ?

    Hi there,
    I have a new setup with three monitors, and I see a strange behavior when I move lightroom from one monitor to the other : there seems to be an automatic color adjustment made in the photos. On my center monitor they are warmer, and switch to a colder color on my other monitor. I have attached screen shots at the bottom.
    Here is a detailed explanation of what I do :
    - I have Lightroom opened on my center monitor. My photos have a kind of warm color cast (my screen is not very well calibrated). Lets call this color "Color A"
    - I start to drag the Lightroom window on my other monitor.
    - When I drag the window on my right (or left) monitor, I still see color A in my lightroom photos even if my window is now on my right monitor.
    - Only when I drop the Lightroom window does the color of the images switch to the colder color cast B.
    I don't see how this could be related to the monitors because the color doesn't change when the window cross from one monitor to the other, but only when I drop it (release the mouse button).
    Here is my setup :
    - Left and right monitors : Samsung XL2370 (DVI)
    - Center monitor : AOC Q2770 (Display Port)
    All these are plugged in 2 Sapphire Radeon HD 5770 Vapor-X (Crossfire).
    When I had only tow monitors (both using a DVI connection), I noticed no color change when I switched monitors... Could this be because of the DisplayPort connection ? Why is it only noticeable in Lightroom (and only in the photo part, the color of the application (buttons and such) doesn't change... Is there somewhere an option for an automatic color correction depending on the monitor into which Lightroom is visible ?
    I have tried to search on forums and support sites, but honestly, I don't really know what to search for ! Any help would be really appreciated.
    The screen shots :
    On my center monitor, and on my right monitor when I drag the window (and still hold the mouse button) :
    On my right monitor, when I drop the window (release the mouse button) :
    Thanks,
    R. Giskard

    Hello R_Giskard, did you find a solution?
    I have the same problem and I did a lot of research to solve it with no success.
    I recently bought a Dell U2713HM Monitor and plugged it on my  Dell Studio XPS M1640 (Mid 2010) laptop, which runs on Windows 7 64 bits. This laptop has a RGBled screen.
    I calibrated both screens (laptop and external) using a Spyder 3 elite device.
    Strangely, when I look at photo open in Adobe Lightroom 5 or Photoshop CS6 and I move it between the two screens, it appears way more saturated on the U2713HM Monitor. For example, the skin tone  on a person is overly orange.
    What is striking, is that when I move the LightRoom window from a screen to another, the color saturation only changes when I drop the window, i.e. if I move if from the laptop screen (where colors are paler) to the U2713HM Monitor, the colors remain pale on the external monitor until I let go of the mouse.
    It's as if a different color profile was applied to the picture as soon as it "lands" on the other screen.
    The change occurs similarly one way or another.
    best regards,
    NC

Maybe you are looking for