Bug: Selection Behavior

It seems in some situations the select tools will "clear" instead of deselect.  Can anyone reproduce?  Is this a "feature"?
To reproduce:
1.  Make a selection
2.  Free transform the selection
3.  Subtract from the selection
CS6x64 windows 7. 

I don't believe that's a bug, but the expected behaviour because your transforming the contents of your selection, not just the selection itself. (at least that's how it's worked for the last several versions of photoshop)
When your transforming the contents of a selection it turns into a floating selection (a temporary invisible layer, you can't see this on newer versions of photoshop)
Your actually transforming the pixels (cutting them from the layer if you will)
Even after you commit the transform but leave the selection it's still floating, so that's why subtracting from the selection actually deletes the pixels.
Once you deselect (defloat), then the invisible layer merges back down into the original layer.
You should use Select>Transform Selection if you just want to transform the selection itself, and not the contents inside the selection.
Or after you make the selection use Layer>New>Layer via Copy.
Set your background color in the toolbox to red and then try the same with a more rectangular shape to see this more clearly.
Photoshop 4:

Similar Messages

  • "resolving alias to" message using aliases on 10.6.8 plus slow text-selection behavior

    Recently after no particular change to my Mac Pro3,2 running 10.6.8 other than some routine software updates, whenever I open an alias on my desktop to standard folders or files, a message shows up "Resolving alias to" whatever the alias name and there's a 2-3 second delay before the folder/file opens. I've found discussion of this issue in some archived discussions but never found a comfirmed solution described, so I'm raising this again. As in others' encounter with this behavior, the slow opening of aliases happens (1) only in my own user account, not in a guest account I set up for test purposes [I have no other user accounts than these], and (2) only happens the FIRST time I open an alias. Subsequent uses of the alias work normally.
    Another strange but possibly related behavior that began at the same time as this alias delay is harder to describe but involves a problem when selecting text using mouse clicks or even highlighting with the mouse for editing. For example, to edit the name of a file or folder on my desktop, I would normally click on the file/folder name, pause a moment and click again: this puts me in edit mode with the current file/folder name highlighted/selected. Now when I attempt this procedure, the second time I click immediately opens the file/folder, as though I had double-clicked rather than clicked+paused+clicked. The only way I can select the name of the file/folder to edit it is to click+long pause (like 3 seconds)+click. Then the text is selected as desired. It's as though the clicks are being recognized (by whatever in the OS recognizes clicks) as much faster than actually made.  There is a similar problem in any program I use that permits text editing, whether Word (Office 2011 for Mac), TextEdit, etc. I have to consciously slow down my cursor/click behavior when selecting text. If not, my actions are misinterpreted as double clicks. This text selection behavior also disappears when using a "Guest" user account, only appearing in my own user account. I Using a different mouse has no effect.
    Steps taken so far. I've Repaired Disk Permissions and Verified Disk using Disk Utility, have Safe Booted, and have turned off all login items in my user account,and recently installed the 10.6.8 supplemental update, all to no avail. Any suggestions or has anyone had and solved this/these problems?

    I think my problem has been that in Sytem Preferences>Mouse, my "Double-Click Speed" was set to the SLOWEST setting. After some experimentation, I now have the that setting two notches from the "Fast" end of the scale. In case it's important, the "Primary mouse button" in my Preferences is set to "Left".
    This not only solves the text selection issues described, but also seems to eliminate the strange "resolving alias to" problem.
    [For the curious, I have a Logitech Performance MX wireless mouse which can be configured with "Logitech Control Center". But the LCC software doesn't control double-click speed; this setting can only be made in the Mouse System Preference pane.]

  • How do you turn off the auto select behavior when working with shape layers?

    How do you turn off the auto select behavior when working with shape layers?
    I am using either of the path selection tools to select only some of the paths on the layer. I have the proper layer targeted. I have the selection too auto select option turned off.
    If another layer has a path in that area, that layer becomes auto targeted and I get the wrong path. Turning off the layer is the only way to avoid this but then I have to  turn on the layer back on between making my selection and transforming to use the other layer as guide. Is there any way to stop this auto select? Locking the other layer does not stop the auto select, just prevents editing.

    As far as i know the move tool options don't have any effect on the path selection tools.
    You might try clicking on one of the path points or on the path itself with one of path selection tools and if you want to select multiple points
    you can shift click with the Direct Selection Tool or Alt click to select the entire path.
    more path shortcuts:
    http://help.adobe.com/en_US/photoshop/cs/using/WSDA7A5830-33A2-4fde-AD86-AD9873DF9FB7a.htm l
    http://help.adobe.com/en_US/photoshop/cs/using/WSfd1234e1c4b69f30ea53e41001031ab64-7391a.h tml

  • Overriding Default JTable Selection Behavior

    I'm attempting to override the default selection behavior of a JTable. For clicking, I want the table to behave basically as if the ctrl key was being held down all the time. That works great.
    I want the behavior of dragging a selection to behave a certain way as well. If ctrl is not held down, then a drag should cancel the current selection and start a new one at the drag interval. This works fine too.
    However, if ctrl is held down during a drag, I want the dragged interval to be added to the selection instead of replacing it. This almost works. However, if I hold ctrl while dragging, it no longer let's me "undrag" the selection: once a cell is inside the dragged interval, it's selected, even if you drag back over it to deselect it.
    I understand why that's happening given my approach, but I'm looking for a way around it. Does anybody have any ideas about how to get a JTable to behave the way I want?
    Here's a compilable program that demonstrates what I'm doing:
    import javax.swing.*;
    import java.awt.event.*;
    public class TestTableSelection{
         boolean ctrlDown = false;
         JTable table;
         public TestTableSelection(){
              JFrame frame = new JFrame("Test Table Selection");
              frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
              //give the table random data
              String [][] data = new String [10][5];
              String [] names = new String [5];
              for(int i = 0; i < 5; i++){
                   names[i] = "C: " + i;
                   for(int j = 0; j < 10; j++){
                        data[j] = "t: " + (int)(Math.random()*100);
              table = new JTable(data, names){
                   //override the default selection behavior
                   public void changeSelection(int rowIndex, int columnIndex, boolean toggle, boolean extend) {
                        if(ctrlDown){
                             //ctrl + dragging should add the dragged interval to the selection
                             super.changeSelection(rowIndex, columnIndex, toggle, extend);     
                        else{
                             //clicking adds a row to the selection without clearing others
                             //dragging without holding ctrl clears the selection
                             //and starts a new selection at the dragged interval
                             super.changeSelection(rowIndex, columnIndex, !extend, extend);
              //keep track of when ctrl is held down
              table.addKeyListener(new KeyAdapter() {
                   public void keyPressed(KeyEvent e) {
                        ctrlDown = e.isControlDown();
                   public void keyReleased(KeyEvent e){
                        ctrlDown = e.isControlDown();
              frame.getContentPane().add(new JScrollPane(table));
              frame.setSize(250, 250);
              frame.setVisible(true);
         public static void main(String[] args){
              new TestTableSelection();
    Let me know if any of that isn't clear.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

    This change seemed to work for me
              table = new JTable(data, names){
                   int prevRow = -1;
                   //override the default selection behavior
                   public void changeSelection(int rowIndex, int columnIndex, boolean toggle, boolean extend) {
                        if(ctrlDown){
                             //ctrl + dragging should add the dragged interval to the selection
                             if ( rowIndex != prevRow ) {
                                  prevRow = rowIndex;
                                  super.changeSelection(rowIndex, columnIndex, true, false);
                        else{
                             //clicking adds a row to the selection without clearing others
                             //dragging without holding ctrl clears the selection
                             //and starts a new selection at the dragged interval
                             super.changeSelection(rowIndex, columnIndex, !extend, extend);
              };

  • Disabling List View selection behavior

    Hi,
    I am using List view to display some text rows. I need the scroll bar on the right and the Sort option on top of the list but I would like to disable the selection behavior of each row. I am just using the rows for display purpose but the availability of hand-mouse pointer on each row is misleading as it lets the user to think that some action would be available if they click the mouse on a particular row. So I want to take this hand pointer off. Is there any other alternative to provide display of a table of items with a scroll bar or disable this behavior of List View ? Please help.
    Thanks,
    Veena.

    Hi Veena,
    I guess you are using Xcelsius4.5, right? (Because in X5 there is no hand-mouse point.)
    If you are using X4.5, As I know, hand-mouse point couldn't be disabled and there is no scroll bar for table component. But there maybe a walk-around for list view component:
    1.Set the color of "Mouse Over Text" and "Selected Text" to black or other same color;
    2.Set the color of "Selected Fill" and "Mouse Over Fill" to white.
    Then when mouse over a row or select a row, there will be no color effects.
    If you are using X5, you can set Table's scroll bar property in Behavior tab.
    Best regards

  • Limit JTable selection behavior

    I have a simple table with 3 columns an multiple rows. If I select a row with the left mouse button and, with out letting go, move the mouse pointer up to a higher row or down to a lower row the currently selected row changes to the row the mouse pointer is over.
    I need to stop this behavior.
    If I select a row with a left mouse press and move the mouse around when I do a mouse release I want the selected row to still be the one i did the mouse pressed action over.
    Please Help.

    This change seemed to work for me
              table = new JTable(data, names){
                   int prevRow = -1;
                   //override the default selection behavior
                   public void changeSelection(int rowIndex, int columnIndex, boolean toggle, boolean extend) {
                        if(ctrlDown){
                             //ctrl + dragging should add the dragged interval to the selection
                             if ( rowIndex != prevRow ) {
                                  prevRow = rowIndex;
                                  super.changeSelection(rowIndex, columnIndex, true, false);
                        else{
                             //clicking adds a row to the selection without clearing others
                             //dragging without holding ctrl clears the selection
                             //and starts a new selection at the dragged interval
                             super.changeSelection(rowIndex, columnIndex, !extend, extend);
              };

  • Modifying JList selection behavior

    What I want to do is change the selection behavior so that if the user clicks on the left half of the cell, the item is selected, but if the user clicks on the right half, the item is not selected. I already have the code to determine where the user clicked, but can't get the selection to not occur when I determine that the user clicked in the "non-selection area" right half.

    After overriding...
    public void setSelectedIndices(int[] indices)
    public void setSelectedValue(Object anObject, boolean shouldScroll)
    public void setSelectionInterval(int anchor, int lead)
    public void setSelectedIndex(int index)...it worked. I implemented each of these like this.
    public void methodX()
      if( clickOnSelectableRegion )
        super.methodX();
      clickOnSelectableRegion = true;
    }It is the responsibility of an outside MouseListener to determine if the click falls on a selectable region or not. If a click occurs that is not on a selectable region, the listener should call setOnSelectableRegion(false) on the List. I set the value back to true so the listener only has to notify the list of "ignorable" clicks.

  • Selecting Behavior property of the Call Behavior Action on a UML Activity Diagram

    I have 16 projects in my UML solution, and I need to be able to select a Behavior in the Call Behavior Action property that is in one Activity Diagram, from a list of Activity Diagrams that are located in different projects, but still in the same overall
    Solution.  Currently, it looks like I can only select Behaviors from within the same project.

    This is related to TFS.  I am using Visual Studio 2013, Ultimate.
    It would be more meaningful if I could insert an Activity Diagram into another Activity Diagram, which is similar to what I can do with an Activity Diagram into a Use Case Diagram.  However, TFS will not allow that.  Instead there is the option
    of using the Call Behavior Action.  When I use this item from my toolbox, I can open the Properties for it and select from a list of "Behaviors" (i.e. Activity Diagrams) that are located in the same Project.  I want to select an Activity
    Diagram from a different Project, but still within the same Solution.  Here is a picture:
    These diagrams are all within the same project.  I want to be able to select a diagram from a different project within the same Solution.  For example, select a diagram from Cash Management as the "Behavior" for an item in the Dealer
    License Project.  They are both in the same Solution, so it seems like I should be able to do that.
    Thanks for any advice.
    Jeff
    Jeff

  • CS4 bug - Selection tool yields random boxes

    Anyone else experiencing this bug in CS4 - when starting a new selection (Marquee Tool), random sized boxes will appear BEFORE dragging and releasing the mouse button to define a selection. The boxes will often extend from the first mouse click to an image edge, but it's unpredictable. I need to release the mouse button, deselect (left click), and then start over again. Once this behavior begins, it can recur repeatedly, making marquee selections VERY frustrating. I have to shut down Photoshop and restart, but eventually the bug will return (typically after 10-20 minutes of use).
    This same "random selection" can occur with other tools, such as Zoom (a single mouse click will zoom to a random magnification, just as if I made a selection).
    My video driver is current (Nvidia 8600GT, OpenGL compatible), and I've swapped the mouse (and associated driver) with no improvement. I'm running Vista (32-bit) on a fairly new PC (9 months old) with 4GB RAM and fast (RAID0) drives. Photoshop CS3 (from which I upgraded to CS4 but left installed) doesn't exhibit this bug. (BTW, I'm an experienced Photoshop user, going all the way back to PS 3.0)

    This bug has been driving me nuts for the past year.    Clicking on the canvas with the selection/move tool will cause the active layer to randomly move somewhere else.  When transforming an object or moving it, the current layer will jump sometimes a small amount but sometimes a couple thousand pixels off the canvas.  It seems to happen more often after the computer wakes from sleep.  I've seen this on two different laptops and a desktop.  Windows XP, Vista and Windows 7.  Logitech and microsoft mice.  Wired and wireless mice.  Nvidia and ATI video cards.  HP and Dell computers.
    It doesn't seem to be an issue with any particular hardware-- just bad coding on Adobe's part.  The only way to fix the issue is to close down photoshop and restart-- this is killing my workflow.  Please fix this Adobe!

  • LR 5.x crop tool bug: selection jumping on activation

    Hi,
    I did not see this reported, but I'd be rather surprised if nobody had noticed the issue before.
    I'm seeing this behavior since I upgraded from LR 4 to LR 5. I think I did the upgrade with 5.3, but at 5.6 I still have the following problem:
    After setting a cropping rectangle (usually with rotation), then change some settings (e.g. exposure, shadows, blacks, etc.) and then activate the cropping tool again, the displayed image jumps to the original frame size for half a second and then back to the previously set crop.
    Since I usually go back to cropping only for small changes in rotation, this is especially annoying, because it irritates the eye in a way that I'm sometimes not even sure if I'm seeing my previous setting again. And then I have forgotten how I actually wanted to adjust the setting
    This seems to me like a bug introduced in LR5. I'm using Lightroom since version 2 and never had this behavior until the upgrade to LR5.
    I'm using Windows 7 Pro 64-bit, nvidia Graphics.
    Steps to reproduce:
    1) Open an image in the development module (I'm using Canon CR2 raws)
    2) Set a cropping window
    3) change some image settings, e.g. exposure
    4) activate the cropping tool
    Please fix this behavior.
    Thanks,
    Karsten

    Thanks for the clarification. Too bad that the fix did not make it into LR 5.6.
    I'm new here, so please apologize my beginners question: Is there a place where I can find bug reports that were accepted as known bugs? I tried the community search on cropping tool and did not find any related bugs.
    Thanks,
    Karsten

  • Inconsistent selection behavior when deleting files in Cover Flow

    I love browsing through my pictures folder using Cover Flow. However, I've noticed that deleting a file by pressing Cmd-Delete produces inconsistent selection results. Sometimes Finder will select the next file down the list, and sometimes it will select no file at all. However, the Cover Flow portion of the window will always show the next file.
    It is misleading when Cover Flow shows the next file, but the file selection pane shows no file selected. I often hit the down-arrow (or right-arrow) key, expecting to skip to the next file, but the first file in the folder gets selected, Cover Flow re-winds its view, and I have to re-find my last position.
    There is also no way to select the current file by clicking on the Cover Flow preview currently showing. I have to click some other file and re-browse to the current file in order to sync up the two panes.
    Is this a bug? Does Apple know about it?

    As mentioned, cover flow does not change the basic Finder operation. Return allows editing the name and Cmd-O or Cmd-downarrow opens the item. It also functions similar to the list view, when you open a folder, the subfolders are added to the cover flow; they do not replace the cover flow icons.

  • Cursor selection behavior confusion...

    If you place your cursor in some text you are composing and then hold the Shift key, you can press either the left or right arrows to select content in that direction one character at a time. This is normal and expected. In all other applications by Apple if you select a few characters to the right in this manner and then press the left arrow key, it deselects the farthest characters and moves your selection back to the point of origin; however, this is NOT the case in these new forums. Here if you select in one direction in this manner, and then press the opposite direction, then the selection expands in the new direction.
    This behavior is a bit confusing...perhaps it could be addressed to be the way we've come to rely on selecting text in other Safari forms and OS X applications?

    I read your post in Firefox 4, posted text in a reply field to test, and did not see this behavior.
    I opened your post in Chrome 10.0.648.205 and then in Chrome 12.0.725.0 dev, posted text in a reply field to test, and again did not see the behavior you describe.
    I opened your post in Opera 11.10, posted text in a reply field to test, and did not see this behavior.
    I opened your post in Safari 5.0.5 and did experience the behavior you describe.
    The issue seems limited to Safari.

  • JDK1.5 table selection behavior has changed

    The default extended selection policy of JTables has changed from version 1.4.2 to 1.5.
    In 1.4.2, a user can hold down the Ctrl key and drag out a multi-row selection. The user can then hold down the Ctrl key again and drag out a second multi-row selection which leaves the first multi-row selection intact. The end result was 2 discontiguous multi-row selections.
    Now in 1.5, the process of making the second multi-row selection clears out the first. Basically any Ctrl+Drag gesture is clearing out any existing selections. This is dangerous since a user that wants to Ctrl+Click several discontiguous rows may slightly move the mouse on each click. This will be interpreted as a Ctrl+Drag and cause all existing selection to be cleared.

    I don't remember being able to do that in 1.4.2_04 without some special code. Well, at least not for a JList, never tried on a JTable. Anyway, you should make a bug for it if it's not alreay there.

  • 30EA2/30EA1 : Selection Behavior on Master-Detail Result Grid

    Hi,
    Tested on both Win XP and Win 7, SQL Dev with the included jre.
    I notice quite annoying behavior on Master-Detail Result Grid.
    This happen on either Report with master-detail layout (i.e Active Session from the built-in report), popup describe on several tabs, and objet viewer especially on Table's Partition tab.
    Here are the things :
    1. Why made the selection on header result cell lose its focus after selecting one?
    I understand, that SQL Dev needs to re-query for displaying the detail.
    But why not made the selection focus, goes back to the selected (shown by the rectangular yellow line around the cell) header cell ?
    2. Point 1 leads to another problem.
    In order to copy the cell value, we have to click once again to select the cell value (shown by the rectangular yellow line around the cell) from the master grid and press CTRL + C.
    What a waste extra effort here.
    Moreover, I noticed some strange thing on object viewer Table - Partition tab.
    It is really hard to copy the cell value from this tab, i.e copying the partition name value.
    Everytime I press CTRL + C to copy its content, suddenly the cell goes to edit mode, which is read-only of course. CTRL + V to paste seems does not work, like it has nothing in the clipboard to be copied.
    And, navigating the cursor from this point would cause the pointer goes to the last character of the cell content, as well as selecting the content using CTRL + Home, is useless.
    Is it because there is no detail record on the detail (in this case Subpartition) tab?
    However Partition tab on Popup Describe, which supposed to have the same behavior, CTRL + C works just fine.
    Is this an expected behavior?
    Regards,
    Buntoro

    Hi Raghu,
    RaghvendraSaboo wrote:
    When changing selection in Master grid, the Child grid is repopulated. This also cause the Master grid to lose focus which makes navigating & copying from master requiring to select a cell in it again.
    Right ?
    Yes. That's right.
    I see, you use Child as referred to me as Detail, on which I get the name from Reports (when create User Defined Reports on SQL Dev, there shows Master on the top panel and below is Detail. :-)
    If yes, this is the same issue as reported in other thread where executing Statement Runner in worksheet, the worksheet loses the focus & the results grid gets the focus.
    The grid has got focus hungry & I am fixing it.Maybe this explains, why there is a small delay before showing the result grid.
    I tried to compare from SQL Dev 2.1.1 and 3.0EA1.
    3.0EA1 gets a little late (a second maybe) when displaying the result.
    For the last item, here are the things :
    1. From the Schema Browser (Left Hand Side), expand Tables.
    2. Select a partitioned table from the tree, there shown Object Viewer (on Right Hand Side) for that Table. -- I use the term Object Viewer as shown on the Preferences : Automatically Freeze Object Viewer Windows
    3. Select Partitions tab
    4. Click a cell on Master grid, there you go the losen focus
    5. Now, click once again to select
    6. Press Ctrl + C
    7. It suddenly change to cell's edit mode (of course its read-only cell)
    Navigating the cursor from this point would cause the pointer goes to the last character of the cell content, as well as selecting the content using CTRL + Home, is useless
    8. Now, go to the worksheet, and press Ctrl + V, nothing happens as if the copied cell doesn't get into the clipboard.
    Regards,
    Buntoro

  • JTable multiple interval selection behavior

    How do you force a JTable to behave as if the control key is always pressed, without the user actually holding down the control key?
    My desired result is to have the user be able to select multiple independent intervals, exactly like the behavior when the ctrl key is held down. But I do not want the selection cleared like when the ctrl key is released and a new interval is selected.

    I solved my problem by subclassing JTable to invert the toggle parameter sent by BasicTableUI.java in the event that control is depressed while making a selection.
    Now instead of using javax.swing.JTable I will use my Toggle inverted version below.
    import javax.swing.JTable;
    public class JTableToggle extends javax.swing.JTable {
        public JTableToggle(){
            super();
        public void changeSelection(int rowIndex, int columnIndex, boolean toggle, boolean extend) {
            // toggle is true in the case where the control key is pressed, i will invert that case.
            toggle = !toggle;
            super.changeSelection(rowIndex,columnIndex,toggle,extend);
    }

Maybe you are looking for