Selection bug?

hi, i'm finding cs4 very buggy, i've read previous articles and updated drivers etc but there's still alot of things that are driving us bonkers!
i previously commented on the marquee bug, where that jumps around the screen and have just noticed another one.. when the move tool is selected and you hold ctrl then click on a shape/image then normally it will select that layer/group but in cs4 it's making my selection jump off the page everytime on the click.
Has anyone else had this? is it a bug?
Cheers
Shelton
Johnston Press

Hey Man.
As always thanks for getting me going here.
Can I please ask you if clicking the black should change both fonts to black? I mean, I seem to be having a problem selecting all my text (which could be a bunch of different colors) and changing it all to black which seems like it should be easy.
Shouldn't I be able to click on the black box and get it to go all to black?
Same thing with changing all the fonts to arial. Shouldn't I be able to select everything pulldown to arial and have it all go to arial...
Regards.

Similar Messages

  • Tree selection bug?

    Hi,
    I don't know if this is a bug or not. When using XML as the
    data provider for the Tree component and multiple nodes have the
    same label, selecting anyone of the nodes will cause all of them to
    be selected. The problem stems from the fact that XML comparison is
    done by value. The comparison is dibe at line 6345 of ListBase. Is
    this a bug? If not, is there a known workaround?
    I attached code that reproduces the problem. Selecting the
    first node, selects the first, second and last node because, by
    value, they are all the same.
    Thanks!
    JPB

    Switch to using a strongly typed object that implements IUID,
    or just make
    sure your XML has other identifying information to it. It's
    not really that
    helpful to have 19 "foos" in your list unless there is
    something else
    different about them.
    So, something like
    <mx:XMLList id="treeData">
    <node label="Test entry 1" id="1"/>
    <node label="Test entry 1" id="2"/>
    <node label="Test entry 2" id="3"/>
    <node label="Test entry 1" id="4"/>
    </mx:XMLList>
    HTH;
    Amy
    "jpbouchard" <[email protected]> wrote in
    message
    news:g941f3$1u8$[email protected]..
    > Hi,
    >
    > I don't know if this is a bug or not. When using XML as
    the data provider
    > for
    > the Tree component and multiple nodes have the same
    label, selecting
    > anyone of
    > the nodes will cause all of them to be selected. The
    problem stems from
    > the
    > fact that XML comparison is done by value. The
    comparison is dibe at line
    > 6345
    > of ListBase. Is this a bug? If not, is there a known
    workaround?
    >
    > I attached code that reproduces the problem. Selecting
    the first node,
    > selects
    > the first, second and last node because, by value, they
    are all the same.
    >
    > Thanks!
    > JPB
    >
    > <?xml version="1.0" encoding="utf-8"?>
    > <mx:VBox xmlns:mx="
    http://www.adobe.com/2006/mxml"
    width="100%"
    > height="100%">
    > <mx:Script>
    > <![CDATA[
    > import mx.controls.Tree;
    >
    > private function selectFirst(): void {
    > myTree.selectedItem = treeData[0];
    > }
    >
    > ]]>
    > </mx:Script>
    >
    > <mx:XMLList id="treeData">
    > <node label="Test entry 1"/>
    > <node label="Test entry 1"/>
    > <node label="Test entry 2"/>
    > <node label="Test entry 1"/>
    > </mx:XMLList>
    >
    > <mx:Panel title="Tree Selection Bug" height="100%"
    width="100%"
    > paddingTop="10" paddingLeft="10" paddingRight="10"
    paddingBottom="10">
    > <mx:Button label="Select First"
    click="selectFirst()"/>
    > <mx:Tree id="myTree" width="100%" height="100%"
    labelField="@label"
    > showRoot="true" dataProvider="{treeData}"/>
    > </mx:Panel>
    >
    > </mx:VBox>
    >

  • [svn:fx-trunk] 13362: List mouse click selection bug fix

    Revision: 13362
    Revision: 13362
    Author:   [email protected]
    Date:     2010-01-07 17:22:41 -0800 (Thu, 07 Jan 2010)
    Log Message:
    List mouse click selection bug fix
    SDK-24963 - Mouse click is ignored by List if  allowMultipleSelection="true" in some cases
    Updated setSelectedIndices to perform the single index equality check if selectedIndices has only one index.
    QE notes: None
    Doc notes: None
    Bugs: SDK-24963
    Reviewer: Ryan
    Tests run: checkintests, List
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-24963
        http://bugs.adobe.com/jira/browse/SDK-24963
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/List.as

  • Switching between Acrobat DC / XI window and another application - cursor selection bug (video and test files attached)

    Hi,
    When I have Acrobat XI or DC open along side InDesign (or other programs like Acrobat or Word), I run into a bug where upon switching from InDesign to Acrobat, the mouse cursor automatically selects a bunch of text in the Acrobat PDF with a spinning beach ball, and I have to click around multiple times to release it from whatever text it has selected. It is annoyance I noticed in a few versions of Acrobat now, and I had hoped the bug would be fixed in DC. The only way to prevent this from happening is to click anywhere else on the Acrobat window (eg the menu bar or the side tools panel, but not the PDF itself).
    Video describing the problem: https://imgur.com/dXurXcB
    Note that no clicking is taking place when switching windows from InDesign to Acrobat - the text in the Acrobat window is being selected automatically by the bug.
    If you watch the video carefully, you will also notice that the Acrobat window does not look like it is taking focus during the selection bug - it only takes the focus after clicking around multiple times.
    Test documents used to record the video:
    http://s000.tinyupload.com/?file_id=14619964329420357364
    InDesign CC File
    http://s000.tinyupload.com/?file_id=18294837115907237178
    PDF File
    Computer:
    Model Name: MacBook Air 2013
      Model Identifier: MacBookAir6,2
      Processor Name: Intel Core i7
      Processor Speed: 1.7 GHz
      Number of Processors: 1
      Total Number of Cores: 2
      L2 Cache (per Core): 256 KB
      L3 Cache: 4 MB
      Memory: 8 GB
    OS: Yosemite 10.10.1

    Thanks for the reply. I think the issue is just confined to Mac machines + Adobe products (this issue doesn't occur when I switch from Word Preview 2016, or Office 2011). I can confirm this issue occurs on more than one Mac as well.
    Here is a slightly larger GIF if the first was too hard to make out
    https://i.imgur.com/CNKnkC0.gif
    It's almost as if the text manipulation / selection from InDesign is carrying over to the Acrobat window, interrupting the normal focus it should get on first click...
    Edit: It just occurred with Spotify - Switched from Spotify to Acrobat, with a scanned image PDF. The rectangular selection tool tries to grab a region of the image several times before focus returns to the Acrobat window. It also just happened after manipulating images and text in Word 2016 Preview and Word 2011.

  • Workaround for JSFL shape selection bug?

    There seems to be a bug in the document selection reporting in JSFL in  CS4 (haven't tested earlier versions).  I submitted it as a bug to Adobe  but I'd really like to find a workaround for it.  I've included my bug  report below.  Has anyone else encountered this?  If so, have you  figured out a workaround?  It's pretty annoying, making the tool I'm  working on really difficult to manage.
    ******BUG******
    After performing a publish preview, fl.getDocumentDOM().selection  reports an incorrect selection of raw shapes.
    Steps to reproduce bug:
    1. Create a JSFL command with the following contents:
    doc = fl.getDocumentDOM();
    fl.trace("there are " + doc.selection.length + " items selected");
    2. Start the authoring environment fresh, with a new document.
    3. Draw several shapes on the stage, not touching each other, all in  the same frame and layer.
    4. Select one of those shapes but leave the others unselected.
    5. Run the previously created JSFL command.  It will send the following  text to the output panel, as one would expect:
    "there are 1 items selected"
    6. Do a publish preview (either Flash or HTML).
    7. When it comes up, close the preview window.
    8. Deselect all and then select one of the shapes (again, keeping the  others unselected).
    9. Run the JSFL command again.  This time, it will say that there are n  items selected (where n is the number of shapes you drew in step 3).   So if you drew three shapes, it will print out the following:
    there are 3 items selected
    Note that this result will be the same even if you go to a different  document, do a publish preview on that document, then return to the  original.  It seems that simply doing a publish preview alters Flash's  state to report the selection incorrectly.
    Results: The JSFL command reports that all the shapes are selected,  despite the fact that only one of them is.  The only way I've found to  get Flash back to its normal behavior is to restart the authoring  environment.
    Expected results: In the steps above, the JSFL command should always  print out that there is one element selected.  There's no reason that  doing a publish preview should change that.

    When selected all shapes in selection are treated as one. You can see it if you run this script with selected multiple shapes:
    fl.trace( fl.getDocumentDOM().selection[0].contours.length );
    It will output you twise bigger number then selected shapes (because each Shape has two contours - one clockwise, other counterclockwise).
    Of course this. implementation is strange for me too. Thats how i found your post

  • Tree Select BUG?

    Came across a little problem, don't know if I'm doing something wrong or if it is a genuine bug.
    Here's what I'm seeing:
    1) I run a program that at the beginning deletes all tags in a tree using the Delete Items Invoke Node with an empty string constant and a True constant for the Delete Children part.
    2) I select all the items in the tree, and display all the tags from the tree using the All Tags Property Node, and display the selected tags directly from the output of the tree icon.
    3) I rerun the program, which deletes all the tags as mentioned before, use a different data set, select all those items, and when it displays All Tags it only has the tags from that run, BUT the Selected Tags has all the selected tags from the current run AND all the tags from the previous run.
    The solution of course is to simply create a local variable of the tree and at startupwire an empty string arrary to it. This shouldn't be necessary if the Delete Items deletes all the tags.
    Attached is a VI showing the BUG
    Michael
    Additional NOTE: If you continue running the VI, the selected tags will pile up UNTIL you manually right click on the tree and hit "Delete All Items"
    Message Edited by miguelc on 03-02-2007 10:46 AM
    Attachments:
    TreeSelectBUG.vi ‏23 KB

    No problem
    >>What is a CAR?
    CAR stands for Corrective Action Request - it's a formal bug report to R&D.
    >>Can anyone search these CARs before posting a supposed bug like I just did? Can you find them online, if so where?
    We post the CAR IDs online so that customers can follow up with them if they'd like, and easily refer to them.  The LabVIEW Champions maintain a monthly bug thread where you'll find pretty much everything BUG that's been posted online - if you search the forum for "monthly bug" (quotes not necessary) you'll see a slew of monthly bug threads returned.  You can also search the forum in general for keywords related to your bug, to see if anyone else has reported it.  Of course there is also a bug list/database which is maintained internally at NI, but the public doesn't have access to that.
    I hope this helps!
    Best Regards,
    JLS
    Message Edited by JLS on 03-08-2007 11:35 AM
    Best,
    JLS
    Sixclear

  • Aperture 3 - Multiple Image Selection Bug?

    I am experiencing an issue within Aperture (v3.0.3) where by from a project folder containing a large number of photos, I rate the ones I wish to keep (typically 3 * and above) and these are all automatically selected for an album.
    Whilst this smart album shows the correct number of images, If I use these as the basis for a book or even a static album, a larger number of images (seems to include any within a series) appear.
    Am I using Aperture incorrectly?
    Why does it show the correct number of images within the smart album, but copying everything shows a higher number within a book?
    It also doesn't seem possible to show just a subset of photos within a book, so I have to get the number correct to save having to go through all photos for the book selection.
    Is this a bug? It certainly appears to be a bug with the way in which this is working.
    Thanks for your feedback...

    Thanks for the response Kirby.
    Essentially when I refer to 'series' I am talking about Aperture's stacks (I used the wrong phrase originally).
    If I have a stack of 10 photos, however only a single one has been rated as 3 star or above (my criteria for being selected into the smart album and/or book), it seems that all 10 photos would appear in the books' photo selection.
    This means that from one photo project where approximately 1800 photos were taken, I had rated around 200 of these as 3 star and above, which is the number of photos that correctly appears in the smart album.
    If I then 'select all' from the smart album and use these as the basis for a book, I would expect to see only the 200 photos for selection within the book, however I see nearly 800 photos which is the total number of photos within the stacks visible in the smart album (whether photos are visible and rated sufficiently or not).
    It's not possible to change the view of photos for the book selection process, so it appears to only list those photos you have chosen, however I see many photos I didn't "choose"...
    Does this make it any clearer?
    Thanks

  • Shift + Enter (Play from Selection) Bug? Logic 9.1.6

    Hi. Im currently using Logic Pro 9.1.6 on USA macbookpro with OSX 10.7.2 installed.  Is there a known bug when selecting a region then Shift and  Enter (play from selection)?  Can't get mine to work.... anyone else having this issue?  Ta. Ju

    Hi
    Function Shift Return???
    CCT

  • Find "Other" search fails when "User" folder selected - bug?

    I have several partitions on my disk.
    On my boot partition, I have 2 .aiff files in a sub-directory of my Documents folder. Using the Finder's "Find" command (not spotlight),
    select search for File Type "other" and "AIFF Audio" from dropdown
    select the "Users" folder as the only folder to search - "Find" shows no files
    select only "Home" to search - finds them.
    select both "Home" and "Users" to search it doesn't find them.
    select the partition (Called "OSX") it finds them.
    select partition "OSX", folder "Users" and "Home" - it finds them
    also - I can get Finder to reset with double-click:
    With a search that finds them, select the file so its path appears in the panel at the bottom of the window.
    Modify the Find to search only "Users". The window clears and no files show, however the path of the previously selected file remains.
    Double click on the path name, the Finder resets ( - in other words, quits, closing all open FInder windows, then restarts without reopening any of those Finder windows)
    Is this a bug or what?
    MacMini - 1.42   Mac OS X (10.4.7)  

    I was having a very similar problem on my computer. I found that this discussion thread solved my problems.
    http://discussions.apple.com/thread.jspa?messageID=2635460&#2635460
    In short, try re-indexing your drive or home folder. You can do his by opening Preferences->Spotlight, select the Privacy tab. Add your hard drive or your home folder to the list by drag and drop or hit the plus symbol at the bottom. Wait a second and remove the drive or folder. It will take several hours for the drive or folder to re-index but the find/search command will start working correctly right away.
    Hope this helps.
    powerbook G4   Mac OS X (10.4.7)  

  • Template Selection Bug

    In the Topic List POD, use CTRL+A to select all topics.
    Choose a template and apply it to all... using the 'Apply'
    button.
    Wait for this operation to finish. When control comes back...
    Press 'OK' and RH7.001.01 disassociates the template from
    every topic.

    While I am at it...
    Template Bug #2: Template/Topic association is lost when
    force update is invoked.
    It'd be useful if we could 'Permanently Apply' a template to
    all topics in a project and that association would persist through
    all user activities.
    A template applied to a project in this fashion should also
    be applied to any new topics introduced to the project in any
    manner whatsoever.

  • Hidden / Locked Layer Drop Object Keeps Selection (BUG)

    For the past several versions of Illustrator (from CS5 through CC) this has been a HUGE problem:
    Whenever I turn off the visibility of a layer (and/or lock it), and I drag a selected object from a visible and editable layer and drop it into/onto the locked &/ hidden layer, the dropped selected object remains selected although I can no longer see or edit it.  The bounding box remains obscuring my work flow and prevents various boolean operations to be done on newly selected objects on editable/visible layers.
    Whenever a selected object is dropped onto a locked &/ hidden layer that selection MUST ALSO BE DROPPED.  Before CS5, to my recollection, this was the case and worked as expected.  But from CS5 onward, this logical and intuitive workflow fails.  So what I am forced to do is I have to changed the layer back to visible and editable, click somewhere off of any object to deselect, then return the layer to a locked &/ hidden state.  Now when I am working with hundreds, if not thousands, of objects that I have to sort and process using layers to manage them, this having to toggle ON, deselect, then toggle OFF to get back to work is hellish at best.
    No object on a hidden or locked layer should ever maintain its selection state --- EVER --- no matter how that object got onto that layer.  Any selection is worthless if it cannot be seen.  Any selection is worthless if it is locked.  Therefore, drop the selection state when a selection was dropped onto a locked &/ hidden layer.
    This has to change.  This issue alone accounts for adding  over 20% to my cost in hours spent on complex projects where thousands of objects need to be managed.  Such complex projects account for 75% of my workload.  So this issue costs me dearly.
    STATS:  Illustrator CC on iMac Mountain Lion w 8GB RAM.

    No.  They were both top-level layers during my latest attempt that finally worked.  In response to your post just now, I tried doing it with sublayers.  And with sublayers the problem re-emerged. I necessarily have multiple levels of sublayers to manage my assets, so I guess that's why it has failed for so long, but my earlier test (sans sublayers) worked.  So it must be the sublayers that cause the issue.
    When the problem happens boolean operations just fail to do anything, and trying to move an existing editable-layer object with a non-released object causes an outright crash.
    So this is definitely a bug that needs fixing.

  • Drag & Drop and Magic Wand and Any Selection Bug...

    Helllo,
    I am experiencing a continuous bug in Photoshop CC 2014.
    First I'm on a Mac G5 using OSX version 10.8.5.
    The bug I am experiencing is not allowing me to select anything using the Magic Wand tool or even the Arrow Selector in any layer if I drag and drop an image from the web to Photoshop.
    I have to physically click on the Mac's main background window outside of Photoshop and then click back to Photoshop to get it to work.
    Thanks,
    JW

    I am guessing you are using an ImageIcon to put the image into the JLabel. I would suggest creating your own version of "ImageIcon". In the interface Icon, the paintIcon method gives you access to the component which is your JLabel. You can get the size of this and draw the image to fit the components size. getIconHeight/Width() should work ok if you just return the initial size that you want the icon to be.
    Another option is to extend JPanel and override its paint method. This would give you direct acces to paint whatever you want, and you can resize your image accordingly when the size changes.
    As far as the flashing goes, you might want to post code (use [ code ] [ / code] tags). There might be something there that someone will see.

  • [SOLVED]Arch Chromebook keyboard selection bug

    Hi, I have an keyboard bug on my Chromebook ArchLinux.
    The selection Shift + Left (or Right) works on Chromium/SublimeText but not on Gedit/QtCreator/CLion/Nautilus.
    I'm using the Gnome3 environnement.
    Last edited by melkir (2014-12-04 01:22:02)

    Hi dhead,
    Yes, I have replace xkeyboard-config-chromebook by xkeyboard-config today and the bug is gone.
    Thx dhead ! When you say "this have been fixed recently", do you have updated your package recently ?
    Edit : Nice on Github ! I have a little pull request for your readme
    Last edited by melkir (2014-12-04 01:09:35)

  • Preview 4.0 Selection Bug!

    Hi,
    Try this. Open an image up in Preview 4.0. Zoom into it a lot. Make a selection, then try using the Move tool to move around the image. Your selection disappears! See?
    From what I understand, you can't use the Move tool while you have a Selection made. This makes it awkward to move across an image in the middle of making a selection. So basically you're forced to use the scroll bars if you're zoomed into an image while making a selection.
    Is this a bug, or just bad design? Imagine if Photoshop didn't let you use the Move tool while having a Selection.

    Everybody, report preview problems to apple at:
    http://www.apple.com/feedback/macosx.html
    My biggest problem in preview 4.0 is it freezes while trying to view large images across four apple LCD's. Sometimes I see a gray screen.

  • Serious UIR selection bug

    Hello all,
    I hope you can reproduce this bug as well as I do because this is major bug.
    In the user interface editor, I have a large canvas with a loaded image that covers the entire panel (1200x800). It's used as a background with a whole bunch of controls on top (about 150). When I start selecting controls with Shift-Clic, the entire PC locks up after about 4~5 selections. The only thing I can do is press Reset on the mobo! If I move the canvas out of the way, it doesn't happen.
    I've had problems with corrupted UIR files in the past, but that's a recently created one.
    Using CVI 2012.

    Hello,
    I had 5 crashes due to this in 2 days last week, but today I can't make it happen again, even though I haven't closed CVI since the last one. Will post again if I can reproduce it. 

Maybe you are looking for