UI feedback: Color panel

I think the colour panel design could be improved with a few relatively small changes:
IMO the sliders are too narrow. Changing values using the slider arrows is very imprecise as a 1px horizontal movement moves at least three units of colour - if not more.
There is some wasted space to the right of the  entry fields. It would be better if those fields were moved right over to the right hand side, made smaller in size to accommodate the three digits they display, and the slider bars were made wider, using the space that was released.
Ideally I'd like to see the slider bars in this panel 'auto-expand' - perhaps up to 3x their current width (1px = 1/255 unit)  when the panel itself is widened.
I'd also like to see the spectrum bar widened to match - and made about 1.5x as deep as it is now. Currently it's too small to be of any significant use IMO.
Mike A

Good catch, I found several  percentages that are not slider selectable anymore for anything with a 0-100% field. Based on some quick tests these percentages are not selectable:
color panel  (only in CS6)
92  75  58  42  25  8
layers panel opacity/fill  (same as CS5)
75  25
layer style popup  (only in CS6)
87  37  12
options bar  (same as CS5)
75  26

Similar Messages

  • How to use IMAQ extract color panel in a LabView file?

    I want to change a color image into a greyscale image. Therefore I want to use the function IMAQ extract color panels but I don't know how to insert it in my LabView application.
    Please, can anyone give me some advice ?!!!
    Thx, Birgit

    Birgit,
    If you want all of the color planes, you can use IMAQ ExtractColorPlanes. Allocate an 8-bit image for each of the color planes. Wire the original color image and each of the 8-bit images for the color planes on the left and bottom of the vi. The outputs on the right side will be the same images, and they will each contain the desired color plane. The input at the top of the vi controls which color planes are extracted (RGB, HSI, etc.) Grayscale will probably be the I plane in HSI.
    If you just want a grayscale image, use IMAQ ExtractSingleColorPlane instead. Wire the color image to Image Src, and wire an 8-bit image to Image Dest. Select the color plane using the top input, and it will come out on the right side.
    Bruce
    Bruce Ammons
    Ammons Engineering

  • Photoshop CC 2014 - color panel resizing by itself?

    Hello,
    I am wondering if anyone else has reported (or even experienced) the new color panel in Photoshop CC 2014 resizing itself when maximizing and then restoring the Photoshop CC 20114 application frame?
    Here are some images to illustrate the issue I am experiencing:
    This is on initial launch of PS CC 2014 after install and then reboot.
    This is the initial maximize of PS CC 2014 application frame (using green button).
    This is the initial restore command (using green button).
    This is the second maximize (using green button).
    This is the second restore command (using green button).
    This is the third maximize (using green button).
    ... and the fourth maximize (using green button).
    As you can probably see through the progressive process that the color panel is stretching vertically with each maximize / restore combination. It seems to stop stretching after the fourth series.
    Machine specs:
    MacBook Pro 17" (late 2011)
    2.5 Ghz. i7 Intel Processor
    AMD Radeon HD 6770M - 1 GB VRAM
    16 GB RAM - OWC Brand
    480 GB SSD - OWC Brand
    OS X 10.9.3 - Clean Install (all updates installed)
    PRAM and SMC refreshed
    Permissions repaired
    Disk verified
    Clean Install of:
    Adobe Creative Cloud app
    Adobe Photoshop CC 2014 app
    Adobe Illustrator CC 2014 app
    No plug-ins or other third-party add-ons.
    I thought I would mention it in case this hasn't been reported yet (or perhaps there is something bizarre going on with my machine).
    Thanks for any insight or acknowledgement.

    Just giving this a bump and a quick note.
    I just performed a clean install of OS X 10.9.3 again on machine spec'd above and then installed Photoshop CS6 and Illustrator CS6 perpetual license versions. While the new color panel seen in PS CC 2014 is not part of CS6, I wanted to test to see if the color panel was resizing itself as I saw with PS CC 2014. It is not.
    I am running Adobe CC 2014 versions at work on a Dell workstation under Windows 7 Professional. I will test on that system to see if the same resizing of color panel by itself occurs and post back sometime tomorrow.
    Note - if an engineer, staff member or moderator could mention whether this has been logged as a potential issue that would be great. I will of course log a report with a link to this post this morning.
    Thanks for any response.

  • Using the Color Panel in HSB mode

    Using the Color Panel in HSB mode. I start by selecting a color in the spectrum at the bottom using the eyedropper.
    As I drag the eyedropper through the spectrum it seems the H slider moves to the same color.
    1. Is the H slider showing the same exact thing that is in the color spectrum at the bottom?
    Thanks.

    Yes if you drag a strait line so that the other two sliders don't move. In other words you are changing only the Hue (H). If you drag up and down the other two sliders Saturation and Brightness will be affected.
    Hi Grant, nice to see you again

  • Breaking Apart Images and Bitmaps in Color Panel

    When I break apart a bitmap and use the eyedropper to sample
    it and then fill in a shape, I notice that the bitmap also stays in
    the color panel as a bitmap. Will this become a permanent part of
    my Flash installation or is it only accessible for this file? I
    opened a new file and it did not seem to appear for it. I just want
    to make sure I understand the purpose of it displaying in the color
    panel. What is the point of this?
    Thanks.

    Not sure I totally understand - the point is so you can pick
    this swatch "color" again in this
    document. If you delete the bitmap from the document's
    library it will go away. If you open a new
    doc it won't be there because the new doc doesn't contaqin
    any imported/broken apart/color-picked
    bitmaps.
    I have to ask, what were you expecting to happen with this
    particular swatch? Or rather, is there a
    better workflow solution for you perhaps? Just curious.
    Chris Georgenes
    Adobe Community Expert
    www.mudbubble.com
    www.keyframer.com
    www.howtocheatinflash.com
    StanWelks wrote:
    > When I break apart a bitmap and use the eyedropper to
    sample it and then fill
    > in a shape, I notice that the bitmap also stays in the
    color panel as a bitmap.
    > Will this become a permanent part of my Flash
    installation or is it only
    > accessible for this file? I opened a new file and it did
    not seem to appear for
    > it. I just want to make sure I understand the purpose of
    it displaying in the
    > color panel. What is the point of this?
    >
    > Thanks.
    >

  • Title Window - Colors Panel

    I seem to have lost my colors panel in the title window.
    The first time I tried TITLER, I couldn't find the colors panel to change text colors, any colors, etc.  I then found it was behind the panel that TITLE opened in. OK, fine. There it was, behind it.
    Now, the colors panel is not behind it nor anywhere to be found. I even asked my dog if he maybe thought it was a bone and buried it (LOL-he just scratched and went to sleep).
    Where oh where did that color panel go, ohhhh, where oh where can it be?
    expeditionwest

    Bill -
    Nope, tried that then looked everywhere, undocked windows, everywhere - no colors panel.  WOW - CS5 is just a learning workhorse.
    With luck, an employee might show up and advise. That would be great customer service!
    expeditionwest

  • Select Color Panel - Color Picker

    The select color panel should allow you to select a color from any part of the screen, not just the spectrum in the color panel itself.
    This would make local adjustments MUCH easier, especially in the case where there are tonal gradations of an object.

    Click in the panel and drag onto the image to get the color picker.

  • Issues with color panel and other windows on right side of flash

    Ok the issue I'm having with flash is that the windows on the right side of my flash window do not snap up when I collapse a window. I am attaching a screen shot to better explain this issue.
    As you can see I have the color panel collapsed up, when I expand this panel and it goes down everything shifts down. however when I collapse it back up a huge gap is left behind in CS5.5 as is displayed in screen shot number 2. In CS4 I never had this problem. I could expand and collapse panels as I saw fit with no problems what so ever. Everytime now that I expand a panel and collapse it, the library or other panels do not move up with the collapsing. This causes a workspace issue. and forces me to drag up the library via the black line that is just above it but below the align panel so that I have better access to my library or properties panel for when I'm working. I find this highly annoying and would like it if there could be a fix produced to make it so this collapsing issue can be fixed and I don't have to waste time dragging up the library/properties panel everytime I need to access stuff in my library when I have a huge list of graphics I'm going through.
    Thanks
    h_cline2

    I already tried that, first thing I thought of before coming to the forums for a solution.
    Thanks anyways.
    Any other ideas?

  • Switching color modes in color panel?

    When designing within the RGB color space, why would you switch between using RGB and HSB colors when applying color to shapes?
    Thanks.

    HSB is simply more "human" or intuitive. The Color panel has no direct relation to the document color mode other than that the panel will consistently default to whatever the document's mode is. For example, switch it to HSB, click around a few times and you'll notice the color panel is back on RGB. Annoying.. but that's for another thread.
    HSB is simply an easier way to change the hue, saturation or brightness of the current color. It can be difficult to remove 10% saturation from R144G234B115, but it's very easy to remove 10% from the Saturation slider in HSB mode. Using ANY setting in the color panel won't change your document, it simply changes how color data in the panel is displayed.
    In short... it's just an easier way to visually change colors at times.

  • Selective Color panel is unavailable (greyed out) in PS CS5

    Hi!
    I've had this problem occur in previous versions as well.
    I work on an image and use Selective Color to make adjustments, then, out of nowhere, the panel no longer operates.
    I can no longer select the colors from the drop down menu for adjustments because the menu is grayed out...here is a photo to demonstrate...
    Do any of you know why this is happening?
    Thanks!
    ~LA

    I know this is old, but in case you come across it again this is one fix that works about 75% of the time.
    Edit>Preferences>General>Reset All Warning Dialogs.'
    Jeremy

  • Feedback: Elements Panel + div hirarchy

    Hello,
    selecting multiple divs (Strg or Shift+Left Mouse Button) within the Elements Panel would be a great enhancement in workflow. When building a responsive grid as a base for e.g. Drupal with divs having height auto and no content, it's difficult to select multiple divs at once using the stage. Another enhancement with renaming divs inside Elements Panel would be the possiblitiy to select specific characters of the div name and make copy+paste work.
    As far as the hirarchy and naming of the divs goes, reflow currently uses this hirarchy with html+css:
    -  primaryContainer
    then designer adds custom divs e.g.
    - -  Outer_Wrapper_Header
    - - -  Inner_Wrapper_Header
    - -  Outer_Wrapper_Content
    - - -  Inner_Wrapper_Content
    With Reflow Stage, "primaryContainer" (name in css and html) div is just called "Container". Maybe a better way with reflowstage+html+css would be:
    - Body (no custom name possible)
    - - Page (designer can apply a custom name)
    - - - Container (no custom name possible)
    then designer adds custom divs e.g.
    - - - - Outer_Wrapper_Header
    - - - - - Inner_Wrapper_Header
    - - - - Outer_Wrapper_Content
    - - - - - Inner_Wrapper_Content
    I am sure you you will find best practice with the hirarchy. What would be the next instance after Container?
    Body->Page->Container->Wrapper
    or maybe...
    Body->Page->Container->Outer_Wrapper->Inner_Wrapper
    Greets...

    Didn't notice that partial selection on element names in the DOM panel were not allowed, filling a bug for that one, for sure.
    thanks for this, I'm taking a look through some of this feedback. Appreciate you taking the time to write it out!

  • Like Microsoft Paint-is it possible to display the color panel

    My project requires whiteboard facility also....If i used JcolorChooser all the colors are displayed...If u see in Microsoft paint only 20 colors are displayed...How can we do using java?Please help me

    import java.awt.*;
    import java.awt.event.*;
    import java.awt.geom.*;
    import java.awt.image.BufferedImage;
    import javax.swing.*;
    public class ColorChart extends JPanel
        int[] colorInts;
        BufferedImage image;
        Color foregroundColor;
        Color backgroundColor;
        double x0;
        final int SIDE = 13;
        final int PAD = 3;
        public ColorChart()
            colorInts = new int[]
                0x000000, 0x808080, 0x800000, 0x808000, 0x008000, 0x008080, 0x000080,
                0x800080, 0x808040, 0x004040, 0x0080ff, 0x004080, 0x8000ff, 0x804000,
                0xffffff, 0xc0c0c0, 0xff0000, 0xffff00, 0x00ff00, 0x00ffff, 0x0000ff,
                0xff00ff, 0xffff80, 0x00ff80, 0x80ffff, 0x8080ff, 0xff0080, 0xff8040
            createImage();
            foregroundColor = Color.black;
            backgroundColor = Color.white;
        protected void paintComponent(Graphics g)
            super.paintComponent(g);
            Graphics2D g2 = (Graphics2D)g;
            g2.setRenderingHint(RenderingHints.KEY_ANTIALIASING,
                                RenderingHints.VALUE_ANTIALIAS_ON);
            double w = getWidth();
            double h = getHeight();
            int cols = colorInts.length/2;
            // demo image area
            // darker highlight adjacent to black shadow
            g2.setPaint(UIManager.getColor("Panel.background").darker());
            g2.draw(new Line2D.Double(0, PAD-1.0, image.getWidth()+1.0, PAD-1.0));
            g2.draw(new Line2D.Double(0, PAD, 0, PAD+image.getHeight()));
            g2.drawImage(image, 1, PAD, this);
            double x = 1.0 + image.getWidth() + 1.0;
            double y = PAD + image.getHeight() + 1.0;
            // white highlight
            g2.setPaint(Color.white);
            g2.draw(new Line2D.Double(x, PAD-1.0, x, y));
            g2.draw(new Line2D.Double(0, y, x, y));
            // foreground/background tiles over image
            g2.setPaint(backgroundColor);
            Rectangle2D.Double bg = new Rectangle2D.Double(12.0, PAD+12.0, 12.0, 12.0);
            g2.fill(bg);
            g2.setPaint(UIManager.getColor("Panel.background"));
            g2.draw(bg);
            g2.setPaint(foregroundColor);
            Rectangle2D.Double fg = new Rectangle2D.Double(5.0, PAD+5.0, 12.0, 12.0);
            g2.fill(fg);
            g2.setPaint(UIManager.getColor("Panel.background"));
            g2.draw(fg);
            // darker shadow outlines
            g2.setPaint(UIManager.getColor("Panel.background").darker());
            g2.draw(new Line2D.Double(bg.x+bg.width+1.0, bg.y,
                                      bg.x+bg.width+1.0, bg.y+bg.height));
            g2.draw(new Line2D.Double(bg.x, bg.y+bg.height+1.0,
                                      bg.x+bg.width + 1.0, bg.y+bg.height+1.0));
            g2.draw(new Line2D.Double(fg.x+fg.width+1.0, fg.y,
                                      fg.x+fg.width+1.0, fg.y+fg.height));
            g2.draw(new Line2D.Double(fg.x, fg.y+fg.height+1.0,
                                      fg.x+fg.width + 1.0, fg.y+fg.height+1.0));
            // color swatches
            x0 = x;
            for(int row = 0; row < 2; row++)
                y = PAD + row*(SIDE+PAD);
                for(int col = 0; col < cols; col++)
                    int index = row*cols + col;
                    g2.setPaint(new Color(colorInts[index]));
                    x = x0 + PAD + col*(SIDE+PAD);
                    g2.fill(new Rectangle2D.Double(x, y, SIDE, SIDE));
                    g2.setPaint(Color.black);
                    g2.draw(new Line2D.Double(x, y, x+SIDE-1.0, y));
                    g2.draw(new Line2D.Double(x, y, x, y+SIDE-1.0));
            // darker highlight trim that borders black shadow
            g2.setPaint(UIManager.getColor("Panel.background").darker());
            // inter-cell vertical trim
            y = 2*(PAD + SIDE);
            for(int col = 0; col < cols; col++)
                x = x0 + col*(SIDE+PAD) + 1.0;
                g2.setPaint(UIManager.getColor("Panel.background").darker());
                g2.draw(new Line2D.Double(x+1.0, PAD-1.0, x+1.0, y));
            x = x0 + cols*(SIDE+PAD) + 1.0;
            // top trim
            g2.draw(new Line2D.Double(x0+PAD, PAD-1.0, x-1.0, PAD-1.0));
            // horizontal center trim
            y = PAD + SIDE + 1.0;
            g2.draw(new Line2D.Double(x0+PAD, y+1.0, x-1.0, y+1.0));
            // white highlight trim
            g2.setPaint(Color.white);
            y = 2*(PAD + SIDE);
            // inter-cell vertical trim
            for(int col = 0; col < cols; col++)
                x = x0 + col*(SIDE+PAD) + 1.0;
                g2.draw(new Line2D.Double(x, PAD-1.0, x, y));
            // horizontal center trim
            x = x0 + cols*(SIDE+PAD) + 1.0;
            y = PAD + SIDE + 1.0;
            g2.draw(new Line2D.Double(x0+PAD, y, x-1.0, y));
            // bottom trim
            y = 2*(PAD + SIDE);
            g2.draw(new Line2D.Double(x0+PAD, y+1.0, x, y+1.0));
            // right side trim
            g2.draw(new Line2D.Double(x, PAD, x, y));
        public Dimension getPreferredSize()
            return new Dimension(260, 36);
        public void setBackgroundColor(int index)
            backgroundColor = new Color(colorInts[index]);
            repaint();
        public void setForegroundColor(int index)
            foregroundColor = new Color(colorInts[index]);
            repaint();
        private void createImage()
            int w = 27, h = 29;
            image = new BufferedImage(w, h, BufferedImage.TYPE_INT_RGB);
            int white = Color.white.getRGB();
            int bg = UIManager.getColor("Panel.background").getRGB();
            int[] data = new int[w*h];
            for(int j = 0; j < data.length; j++)
                data[j] = j%2 == 0 ? white : bg;
            image.setRGB(0, 0, w, h, data, 0, w);
            Graphics2D g2 = image.createGraphics();
            g2.setPaint(Color.black);
            g2.draw(new Line2D.Double(0,0,w,0));
            g2.draw(new Line2D.Double(0,0,0,h));
            g2.dispose();
        public static void main(String[] args)
            ColorChart colorChart = new ColorChart();
            colorChart.addMouseListener(new ColorSelector(colorChart));
            JFrame f = new JFrame("mimics v5.1");
            f.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
            f.setContentPane(colorChart);
            f.pack();
            f.setLocation(200,200);
            f.setVisible(true);
    class ColorSelector extends MouseAdapter
        ColorChart chart;
        public ColorSelector(ColorChart cc)
            chart = cc;
        public void mousePressed(MouseEvent e)
            Point p = e.getPoint();
            Dimension d = chart.getPreferredSize();
            if(p.x > d.width || p.y > d.height)
                return;
            int x = (int)(p.x - chart.x0);
            int col = x / (chart.SIDE + chart.PAD);
            int row = p.y / (chart.SIDE + chart.PAD);
            int cols = chart.colorInts.length/2;
            if(row < 0 || row > 2 || col < 0 || col > cols-1 || x < 0 ||
                          row*col > chart.colorInts.length-1)
                return;
            int index = row*cols + col;
            //System.out.printf("p.x %d p.y %d x %d row %d col %d index %d\n",
            //                   p.x, p.y, x, row, col, index);
            if(SwingUtilities.isLeftMouseButton(e))
                chart.setForegroundColor(index);
            else if(SwingUtilities.isRightMouseButton(e))
                chart.setBackgroundColor(index);
    }

  • Adobe seeking feedback about panels, palettes, workspaces, and other UI elements

    Several folks within Adobe are discussing the user interfaces for our various applications, and we'd like your feedback.
    Do you use After Effects, Premiere Pro, Photoshop, Illustrator, and Lightroom? Other Adobe applications?
    If so, please post your comments on this forum thread comparing your experiences with the user interfaces of these applications.
    Regarding the panels, palettes, workspaces, and overall UI paradigms in these applications: What do you like? What do you hate? Do you care that the applications are different in this regard? What differences do you even notice?

    Primarily using AE/PP with often PS as well, some illustrator.
    I don't think the UI itself -- panels palettes workspaces etc -- need much work, they are overall greatly improved in the last 5+ years & for the most part much ahead of competition. More attention should probably be put into other items that need improved, many of which already came up listed here.
    One thing, I wish text brightness was added as customizable as well as the UI slider; I don't like the text brightness on the lower and higher end of the slider, wish I could customize it.
    BUG since as far as I can remember, maybe CS3 or earlier: workspaces need to remember multiple monitor setups!
    The problem is, I snap off my timeline into a separate window, and make it full screen.
    Now, if have an explorer/finder window open on the screen where the project & monitors panels where, everything opens fine & my full, double screen layout opens just as I left it.
    However, if I open the project from the monitor that say, my full screen timeline is in, the project/monitor panels etc come up in that same screen, undernearth the timeline.  So I have to nudge the timeline window down, and double click the primary premiere pro window, and for some reason that maximizes it to the other screen).  Then bring my timeline window back into place.
    For this reason alone I kind of like making a single window layout that's just 2-screens wide (Avid-esk), however, I run different resolutions on the monitor and this really complicates things if I'm trying to use all of my screenspace, when two or more monitors have different heights for resolution.  Also, in this setup, all progress windows appear right in the middle, so it's split between the two monitors.  This could be improved.
    Another request would definitely be to make hotkeys and things like timeline navigation more universal among your apps.  I run Avid+custom setup on my hotkeys in PP--I jump into AE, and every last button is different, and in AE it's not nearly as easily customizable. Same for Encore's, etc.  I'd LOVE for a change in PP's hotkey to reflect how it works in AE, Encore, and even PS in video mode, etc.
    Simarly, as mentioned on this forum, I hate how blending mode changes in PS is arrows keys, on AE is shift + or -, and totally manual (mouse--annoying) in PP.  If there's one thing I wished was improved, it would be to make this particular task universal among Adobe apps.
    I also really miss the hotkey property drop downs from AE when in any other program (c for opacity, a for anchor, etc).  I'd love to see them make it into other apps.
    Try not to hide things in the panel's window, coming from "hamburger menu's", I like that CS5 has kept things well enough organized to not have a bunch of important options there that are easy to miss.
    Speaking of buttons, I think you'd find it rewarding to add 'fit to fill' and other fit clip options into buttons. They are extremely hidden right now, because you only see the options if you set 4 in/out points and don't drag/drop, which most users will never do.  Additionally, "solo" & "mute" buttons for audio tracks, which are right there on the audio mixer, just makes sense, add them.
    Another important one is you need to make everything keyboard mappable.  Like in MC, all buttons and actions need to be mappable--just the drop down menus and the few extras you have listed doesn't cut it.  I agree with others here, the keyboard visual layout would be dandy here.
    Definitely a +1 to improving thumbnail views.  Really quite bad right now.  Need much more customization in sizes thatn just 3 sizes, and a thumbnail + info view (like script view in MC) makes it so you can both see and sort the info, and see the clip at the same time, which is ideal for me.  Be able to customize the thumbnail, maybe a special type of marker that's put in from the preview window?
    Hope this helps.  For the most part the UI's are really great; it's the thing that most other NLE users are complaining about in their software, not Adobe users.  Often in their forums I'll see posts comparing things to PPro's UI and pointing out how much better developed it is & that particular app should do something similar to what Adobe did.  In my experience, anyway
    - wb

  • White rule appearing below colored panel (bug?)

    I am making a long web page for a client, temporarily hosted at Business Catalyst:
    http://col2013micro.businesscatalyst.com
    At the bottom of the page there is currently a yellow panel. It butts to the blue browser fill. It looks fine in Muse; but, there is always a white line at the bottom of the panel when seen in a browser. It shows up that way in Muse Preview, too.
    Am I doing something wrong, or is his a bug?

    Yes, that is the line. And, yes, I think you are on the right track.
    The Footer and Bottom of Page are both set at the same setting. I checked this on the Master Page. Also, the Bottom of Page on the page is set as high up as it can go. And, I don't think I can adjust the Footer on the page itself. So, that white line must be the white page showing. I would hate to make the page yellow, just for this one area, though. In any case, it looks like it must be a Muse bug to me.
    I had another issue with white lines appearing where they should not: I butted two image frames together. I did this again nemerically to make sure they are exactly touching. No strokes or spaces, and the images are bigger than the image frames. There is a vertical line where the two images butt together. I have to overlap the images to remove the white line. The white line shows in a browser, but not so much in Muse.

  • Adobe Color Panel CC Empty in PS CC 2014

    WAS working great... now the panel is empty. Yes, I'm logged in and connected.
    It also works in Photoshop CC. I've uninstalled and reinstalled so... what am I missing?
    Thanks in advance for any assistance or direction you can give me

    Julie, with so much already written in the thread, I hope I am not duplicating a previous response, but have you tried downloading the zxp file directly from this page
    https://creative.adobe.com/addons/patches/5071/install
    I'm thinking that would give you more control of the process, seeing as the whole Extension Manager thing is a closed black box so you have no idea if it is working or not.  Having said that, double clicking the zxp file launches the Extension Manager anyway, but you can at least see it say it is installing.
    Perhaps remove the current installation before doing this, and resetting Photoshop Preferences.  In fact my gut feeling is that resetting Preferences might be a one stop fix in itself!

Maybe you are looking for