Component Properties panel stuck/broken

Xcelsius Engage 2008 5.1.1.0, Build 12,1,1,344
MS Office 2007 (12.0.6324.5001) SP1 MSO (12.0.6320.5000)
Windows XP SP2
In the main project I have been developing for the past week, the Properties Panel appears to be completely broken all of a sudden.  With some effort, I can eventually manage to double-click on an existing object and bring up its properties, but it often requires clicking around to different components, hide/unhiding them, lock/unlocking them etc. first before I can do that.
New objects refuse to appear in the Object Browser at all even though they show up in the design area when I drag them in, and even double-clicking them after jumping through the above hoops has no perceptible effect.  (They can be resized and dragged around, though, and no, sorry, right-click context menu options are all grey).
The moment the issue seemed to begin was when, in this same project, I attempted to select multiple components in the object browser to edit one field, but aborted that attempt in favor of editing one object that was not in the group.  The objects, incidentally, were each sitting inside different groups containing other objects, and all of these groups were sitting inside one main Panel container.  All of a sudden, my selection was "stuck" and Xcelsius behaved very sluggishly and finally crashed.  I didn't connect this to my select action, however, because I chalked it up to being yet another instance of [the performance issue I documented previously|Frequent crashes when running Excel 2007, Xcelsius 4.5 and Xcelsius 2008; (Nov 7).
Realizing this connection later, I also attempted to multi-select objects again in a variety of ways, hoping to magically reverse the problem somehow, but fortune did not smile on me and the issue has remained.
After much trial and error, and several system reboots, it seems that my Xcelsius 2008 is stuck this way.  I plan to reinstall it soon, but in the interests of providing you in QA/Support with the information that you'll likely need, I'm willing to delay this step.  That said, I really don't have much time to deal with this sort of thing right now.  I really need to get past this and other issues soon so that I can move forward towards a looming project milestone, and if I can't I may have to scrap the effort and go with a different solution entirely.  I sincerely hope another SP or FP is due out soon.

Ah, I fixed it.
1. Closed project (and Xcelsius) again (no save - never saved once since this issue began for fear of making things worse)
2. Launched Xcelsius on its own
3. Started new phony project
4. Dragged in a couple of panels
5. Dragged in a bunch of random objects into panels
So far everything seemed fine.  I could see all objects both in the design area and the Object Browser, and I could edit them however I wanted.
6. Multiple-selected a bunch of objects within groupings within one of the Panel components
7. Clicked on a field within that selection as if to edit it, but didn't
8. Clicked away to some other random object (not in Panel)
Everything was fine, so far.  The issue was not recreated, and Xcelsius seemed fine.
9. Opened my real project from the File menu recent items list (closed w/o saving the phony project)
10. Double-clicked on various components - no problems
11. Dragged in new component, voila, now I could see it listed in the Object Browser, and edit its properties however I liked.
So far, so good.  Hopefully the problem remains gone.  I would love to hear feedback if you have any.

Similar Messages

  • Flex properties panel

    Hi,
    I am try to create a test application with the flexbuilder
    plugin. But when I look into the Flex properties panel I see only
    basic properties. I have already re-install the flex builder to
    lookup the details of the properties panel without success.
    I don't see in the properties panel the "Styles", "layout"
    and other advanced options... How can I get those settings back.
    Or where can I put those settings on.
    Regards,
    Guy

    The "Specific component with style name" acts as a hint to
    CSS Design View and serves to document the purpose of the style.
    However, Flex itself ignores the component name portion of the
    name.
    So, if you have Label.myLabel{} in a css file and open that
    file in CSS Design View, you will see a preview of that style with
    a Label as the sample component. If you have just myLabel{}, CSS
    Design View will not know what to use as the sample component, so
    you would need to select the sample component from the combo box at
    the top of CSS Design View.
    In the MXML source code, Flex considers Label.myLabel and
    myLabel to be the same thing. This is a limitation of Flex and the
    MXML compiler. It ignores all characters before the dot in the
    style name.
    So, the Label.myLabel syntax is only useful in Flex Builder
    CSS Design View. It saves you from having to select Label as the
    sample component. We also consider it to be a good practice because
    it makes it clear from the name that the style is intended for use
    with a Label and not some other kinds of components.
    -- Greg Dow
    -- Adobe Flex Builder Team

  • Symbol Properties panel not updating or refreshing

    Y'all,
    I'm running FW CS5 under Windows 7 Pro (64-bit), and my Symbol Properties panel has stopped updating when I select a symbol to modify. I have to close and re-open the Symbol Properties panel to force it to refresh.
    If I have the panel open and select a symbol on the page, the panel remains blank.
    If I have edited a symbol then deselected it, that symbol's properties remain visible in the Symbol Properties panel after the symbol is deselected.
    If I have edited a symbol then select another symbol, the first symbol's properties remain visible in the panel and it does not update to show the properties of the newly selected symbol.
    In all cases I must close and re-open the Symbol properties panel to force it to refresh and update.
    I've also noticed two other peculiar refresh problems lately - when the rulers are visible and I either zoom in / zoom out on the document or change the application window size, the top ruler often vanishes. I have to minimize then maximize the Fireworks application window to force a refresh and get the rulers to re-appear.
    Finally, the little document info boxes at the lower right corner of the canvas showing document size and zoom level often go blank or vanish when I either zoom in / zoom out on the document or change the application window size. I have to minimize then maximize the Fireworks application window to force a refresh and get the info boxes to re-appear.
    It seems that the problem may be related to some larger Fireworks screen refresh problem. It did not behave this way when first installed - it began happening recently, and the only thing that has changed was a minor update to all of the CS5 design tools (including FW) about the way that image metadata is handled.
    Is anyone else experiencing odd refresh errors? Is it possible that an extension could cause this?
    Any help and advice would be appreciated, because it has become really cumbersome to use component symbols.
    Thanks,
    Dave

    After digging around and looking at what has been updated or installed on my computer since these weird refresh problems began, I may have identified a possible cause.
    Adobe installs the Java runtime with the Creative Suite (I'm not sure why, but it's there), and a few weeks ago the 1.6.20 update installed itself, but it failed multiple times before installing, then Windows 7 informed me that a component was improperly installed with the incorrect privileges. Last night the 1.6.21 update installed itself without any errors, and this morning Fireworks seems to be working normally again.
    I'll keep monitoring FW for weird refresh problems, and if they return I'll post an update. It is possible that the 1.6.20 update broke something that was fixed by the 1.6.21 update.
    Can anyone tell me why the CS programs require Java and what it is used for?
    Thanks,
    Dave

  • Properties panel - bug -- does not appear --

    I have just started experiencing this problem
    im running xcelsius 2008  vs 5.1.1.0   build number 12 1 1 3 44
    the properties panel all of a sudden no longer comes up when a component is double clicked or right clicked or alt entered
    what is going on? i need help  -- i have tried to install and reinstall -- have the latest service packs and fixes -- rebooted many times - cleared temp files out etc etc
    need help  very frustrated

    Are other component property sheets not working either?
    If you want to give re-installing another shot, you can try the steps provided by Javier in this post.
    Best Practice Re-install Process?  (Xcelsius 2008 Engage)
    Also, after uninstalling, delete the folder where Xcelsius was installed to.
    (default would be C:Program FilesBusiness ObjectsXcelsius)
    Other than that, I don't really have much more information to provide.

  • I have CC and while attempting Light Effects, the Layer will appear in the layers panel, but the option bar will not appear and neither will the Properties panel. All my preferences are set correct, and my computer has a compatible video card and RAM. Ple

    I have CC and while attempting Light Effects, the Light Effects Layer will appear in the layers panel, but the option bar will not appear and neither will the Properties panel. All my preferences are set correct, and my computer has a compatible video card and RAM. Please help!
    I tried to delete the layer attempt again. I am in a Photoshop class, but the work is all online, so all my teacher is going to do is send me to this site. I am trying to edit a photo for this class, and without this working, i go to filter>render>light effects. the bar and panel will pop up for about 2 seconds, then disappear. How do i get the options bar and properties panel to display?

    I was about to suggest resetting LE from the Workspace drop-down top right corner, but if you can't see the Options Bar, I guess that is not going to happen.  The normal Tool reset is grey out for LE, so it might be a case of resetting Preferences.
    Reset Preferences
    Windows — Hold down Shift Ctrl Alt immediately after starting Photoshop
    Mac — Hold down Shift Cmd Opt immediately after starting Photoshop

  • Character Styles in CSS Properties Panel are not correct

    I am using Adobe Illustator CC.
    I am trying to export all of the charter styles as CSS. However the CSS panel is not generating the correct style.
    Right now, in the Character Styles Panel and CSS Properties Panel I have 3 styles (Default, h1, h2)
    This is how they are defined in the Character Styles Panel:
    1. [Normal Character Style]:Helvectic Neue LT Std, 55 Roman, 16px
    2. h1: Helvectic Neue LT Std, 25 Ultra Light, 35px
    3. h2: Helvectic Neue LT Std, 45 Light, 18px
    HOWEVER
    When I go to the CSS Properties panel the code is not showing the Font Style:
    This is how they are defined in the CSS Properties Panel:
    1. [Normal Character Style]:
    .NormalCharacterStyle
      font-family : Helvetica Neue LT Std;
      font-size : 16px;
      color : #19131F;
      color : rgb(25, 19, 31);
    2. h1:
    .h1
      font-family : Helvetica Neue LT Std;
      font-size : 35px;
      letter-spacing : 0.53px;
      color : #FFFFFF;
      color : rgb(255, 255, 255);
    Missing:  25 Ultra Light
    3. h2:
    .h2
      font-family : Helvetica Neue LT Std;
      font-size : 18px;
      text-transform : uppercase;
      color : #FCFCFC;
      color : rgb(252, 252, 252);
    Missing:  45 Light
    Am I not doing somethign correctly? Is it a problem with my font or with Illustrator?
    Also, in case it makes a difference, I only have the default paragraph style defined. It's style is; Helvectic Neue LT Std, 55 Roman
    Thanks!

    CSS cannot render typographical multiple weight fonts simply because that's just not how it works. All CSS does is reference a physical font file and its properties and while it's possible to use the font-weight and font-style attributes to make standard fonts lighter or bolder it does not compare to anything you would do with the font in a real design environment. That and of course you still need to define fallback/ substitution options - the Helvetica Neue you are referencing is exclusively available on Apple systems only and even if what you are trying worked off the bat, it would be useless on alternate devices that have no access to the font.
    Mylenium

  • Can I turn off the Properties Panel in Photoshop CC?

    Every
    Single
    Time
    I draw a line or a shape or do almost anything it seems in PSCC, the Properties Panel jumps out. Quite rudely, it blocks the upper right of whatever I am working on. Yes, I can simply close it, but it interrupts my workflow, and it pops out constantly. This definitely did not happen in CS6 or any previous version of PS or even in the first version of PS in Creative Cloud.
    I haven't yet come across anywhere that will let me deactivate that automatic pop-out...I was hoping someone else had found it already. I would greatly appreciate some assistance!
    Thanks!!

    You 'instruct' me; I 'should' ... Imperatives, and yet it's me who has the 'attitude'.
    Your point regarding dates on the implementation is noted - apologies to those attempting to find a viable work-around with what they had available to them - but subsequent advice to deal with this by buying an extra monitor makes multiple presumptions.
    Thanks once again for your opinion on what I should do, but I came to the Adobe forum for an answer regarding an Adobe issue, by definition precisely the right place. Not to be given commands as to how I should work or spend my money by a complete stranger. There's very little helpful about the latter two points, irrespective of how you choose to define them.
    To restate my thanks:
    Thank you to Jorge and qerhqrhbwdbs for advice on how to actually deal with the problem.
    I've got more pressing things on the agenda than bickering about this, Noel, I presume you have too.

  • CS4- properties panel not displayed correctly

    I just installed Dreamweaver v10.  The properties panel information is being clipped. Does anyone else have this problem?

    Good evening,
    make sure your dpi is set to default 96 dpi, I had this problem because working with a small screen and old eyes, I adjusted my font size, had to set back to default 96dpi, hope this helps

  • Why is my properties panel empty on photoshop cc

    Upon opening my properties panel it is empty.  The tutorial I am doing shows the property panel with adjustments ie. Curves.  How do I fix this?

    Go to the top menu and click:
    Window >> Adjustments

  • Component properties don't exist anymore.

    I have an component called: Event.cfc
    Long story short, I init() it by issuing a command like:
    <cfset eventObject = new 'com.Event'() />
    This component has 2 properties: data (a structure) and name (a string).
    The init() method calls a private method:
    <cfset VARIABLES.setName( VARIABLES.getAttribute( 'event' ) ) />
    The setName() method is implicit, ColdFusion builds it based on the name attribute.  I manually created the getAttribute() method which works with the data property.  In the getAttribute() method, I have a command that reads:
    <cfset LOCAL.retVar = VARIABLES.data[ ARGUMENTS.attributeName ] />
    Well, CF keeps saying that 'data' does not exist in VARIABLES.  But I thought that properties that were defined in a component were put into the VARIABLES scope.  So how can this variable NOT exist when I have it defined at the top of the Event.cfc component as a <cfproperty>?

    <!---
              <!--- ***************************************************************************************** ************************** --->
              <!--- ***************************************************************************************** ************************** --->
              Name:                     Event object component.
              File:                              Event.cfc
              Desc:                              Handles View-initiated Event objects.
              Version:          1.0.0 (2013-10-10T12:00:00-0500)
              Todo:                              [none]
              <!--- ***************************************************************************************** ************************** --->
              <!--- ***************************************************************************************** ************************** --->
    --->
    <cfcomponent
              output                     = "false"
              accessors          = "true">
              <!--- ========================================================================================= ========================== --->
              <!--- ========================================================================================= ========================== --->
              <!--- Component methods (explicit):
                                            Component methods (implicit):
                                            Component properties:
                                            Private variables:
                                            Public variables:
                                            --->
              <!--- ========================================================================================= ========================== --->
              <!--- ========================================================================================= ========================== --->
              <!--- Component properties: --->
              <cfproperty
                        required          = "true"
                        type                              = "struct"
                        name                              = "data"
                        getter                    = "false"
                        setter                    = "false" />
              <cfproperty
                        required          = "true"
                        type                              = "string"
                        name                              = "name" />
              <!--- ========================================================================================= ========================== --->
              <!--- ========================================================================================= ========================== --->
              <!---          Method: init(). --->
              <cffunction
                        access                              = "public"
                        returntype          = "Event"
                        name                                        = "init"
                        output                              = "false">
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- Arguments. --->
                        <cfargument
                                  required          = "true"
                                  type                              = "struct"
                                  name                              = "constructorData"
                                  default                    = "#{ 'event' = '' }#" />
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- Set LOCAL variables: --->
                        <cfset LOCAL.attributeName = '' />
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- Set instance variables: --->
                        <cfset VARIABLES.setName( VARIABLES.getAttribute( 'event' ) ) />
                        <cfif structCount( ARGUMENTS.constructorData )>
                                  <cfloop collection="#ARGUMENTS.constructorData#" item="LOCAL.attributeName">
                                            <cfset VARIABLES.setAttribute( LOCAL.attributeName, ARGUMENTS.constructorData[ LOCAL.attributeName ] ) />
                                  </cfloop>
                        </cfif>
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!---          Return.          --->
                        <cfreturn THIS />
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
              </cffunction>
              <!--- ========================================================================================= ========================== --->
              <!--- ========================================================================================= ========================== --->
              <!---          Method: getAttribute(). --->
              <cffunction
                        access                              = "private"
                        returntype          = "any"
                        name                                        = "getAttribute"
                        output                              = "false">
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- Arguments. --->
                        <cfargument
                                  required          = "true"
                                  type                              = "string"
                                  name                              = "attributeName" />
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- Set LOCAL variables: --->
                        <cfset LOCAL.retVar = '' />
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- Capture the attribute value: --->
                        <cfset LOCAL.retVar = VARIABLES.data[ ARGUMENTS.attributeName ] />
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!---          Return.          --->
                        <cfreturn LOCAL.retVar />
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
              </cffunction>
              <!--- ========================================================================================= ========================== --->
              <!--- ========================================================================================= ========================== --->
              <!---          Method: setAttribute(). --->
              <cffunction
                        access                              = "private"
                        returntype          = "void"
                        name                                        = "setAttribute"
                        output                              = "false">
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- Arguments. --->
                        <cfargument
                                  required          = "true"
                                  type                              = "string"
                                  name                              = "attributeName" />
                        <cfargument
                                  required          = "true"
                                  type                              = "any"
                                  name                              = "attributeValue" />
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- Store the attribute value: --->
                        <cfset structInsert( VARIABLES.data, ARGUMENTS.attributeName, ARGUMENTS.attributeValue, true ) />
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!---          Return.          --->
                        <cfreturn />
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
                        <!--- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::: --->
              </cffunction>
              <!--- ========================================================================================= ========================== --->
              <!--- ========================================================================================= ========================== --->
    </cfcomponent>

  • Color picker in the Properties panel used to work

    I have an object that I want to fill with a specific color. I click on the Fill property, choose the color picker, and type in the RGB numbers for the color. For example 240, 150, 100 for the RGB values. I get black. If I type those same color values into the new Swatches panel, I get an orange color. Has the color picker in the Properties panel stopped working?

    Jay, that is a known bug, reported it months ago and hope it will be fixed
    soon. The Color picker (picking colors) is still functional, it is only typing in of Hexadecimal codes that is not possible at this moment.

  • I can't edit a Line with the Properties panel - Flash CS4

    I have created a line on the stage with the Line tool, and then want to edit the Stroke and Style in the Properties panel. However, after creating the line these options are greyed out and not available to me. Even if I then select the Line with the Selection tool, I cannot edit the Stroke or the Style. It seems to me I should be able to do this, what am I missing?

    Normally after drawing the line you only need to click once on it to select it, and with it selected you should be able to access its settings in the properties panel.

  • Motion tweens from keyframe vs properties panel

    When motion tweening a grouped object in either Flash 8 or
    Flash CS3, I get different results depending on whether I use the
    keyframe or the properties panel to set the tween.
    If I right-click the first keyframe and select "Create Motion
    Tween," I get two graphic symbols named Tween 1 and Tween 2 in the
    library .
    If I select Motion from the Tween drop-down list in the
    Properties panel, I do not get those two graphic symbols in the
    library.
    Question #1: Which is the better way to create motion tweens
    -- using the keyframe or using the properties panel?
    Question #2: What other differences are there between
    creating a motion tween (or shape tween in CS3) between using the
    keyframe or using the properties panel?
    Ken Elder
    Oklahoma City

    1) either is fine, however you should not try to tween
    multiple object at the same time, put them in a moveclip and tween
    the clip, or on separate layer and tween them individually. This is
    why the symbol shows up in the Library, because it's not quite the
    right way to do it, and Flash needs to make some things to try a
    keep it straight. The best way to tween is to use the Tween class
    and script the tween.
    2) no difference, they both fire the same method. Like using
    key shortcuts vs. the menu.

  • Properties panel still a major issue - so is overall CC interface

    Hi, I have just bought into the whole Adobe CC apps things after years of working with CS4, 5 and 5.5 and remaining compatible with most of my clients, few are taking the leap to CC right now.
    Anyways, I am extremely disappointed in the interface, and completely amazed that the Properties panel in Dreamweaver is still ridiculously underwhelming.
    Case in point, the URL field.
    Why has this field remained limited to just 30 characters when the Property panel extends the full width of the screen and is completely empty from the walfway mark over to the far right?
    Can't remember the last time I had such a simple URL it even fit in there, mostly dealing with enewsletters with externally-hosted content... need hard URLs that are lengthy, this limitation adds too much time to my work and is annoying beyond belief.
    In addition, all CC apps now leave a hideous solid background that covers all other apps, and the Finder, this to me is reverting back to 1998 standards, not Mac OS X standards at all.
    Are the recent Adobe CC apps all Windoze ports? The dialogue boxes look hideous, the progress bars, etc, etc. all hideous, nothing like the slick CS4 look that was a major improvement over previous versions.
    And in any dialogue box you have to tab through every single option in the dialogue box... what?
    I used to love Adobe apps, I use them daily, several hours a day. Now I just don't want to have to deal with them.
    Please Adobe, what happened? Tell me you're working on fixing these issues and making these apps usable again.
    Right now I'd rather become a manager and not have to look at InDesign, Illustrator, PhotoShop, Dreamweaver ever again.
    Thanks.

    Hi David, thanks for the Application Frame tip... although in InDesign [the app I use most] it is also in prefs which was confusing, isn't in DW's prefs, or Ilustrator's or PhotoShop's... but the interface colouring is... the inconsistency here is annoying. There are so many issues leftover from previous versions of these apps which I have pointed out to Adobe that it's disappointing, having "upgraded" to CC and not finding any real improvement. I remember when apps moved a full version they were exciting to use and explore, just not happening any more with so much room for improvement - I could understand if the apps had everything needed and were the absolute best possible... but not the case, truly disappointed, could have stayed with CS5.5. Thanks.
    PS - that form you pointed me to is the one I used to file the request - and they replied it wasn't a bug it was a feature request, even though the title of that forms states "Feature Request/Bug Report Form" Weird.

  • Properties panel in Adobe Dreamweaver

    How do I display the properties panel once it has been closed?

    Go to Windows Menu then click on properties.
    You can use shortcuts as well.
    If you are on Windows Press <CTRL +F3> on MAC press <CMD +F3>

Maybe you are looking for

  • Remote console via an eLOM on a Sun 4150 doesn't work in Mac OS X Leopard?

    Hi, We have a pair of new Sun 4150's (with the Xeon Woodcrest CPU), and I'm playing around with the remote management features provided by the eLOM. On Mac OS X 10.5 Leopard, I am able to launch the Java Remote KVM (Sun eLOM console) Java utility, bu

  • External display freezing & phone restarting

    I've had an 8200 for just over a month now, and exchanged my original for a new one last week.  The original was powering off randomly and not turning back on without having the battery removed and replaced. This one (in use for 4 days now) has begun

  • Digitizer/Dead spots

    i have an iphone it works great in some places but i have a couple of dead spots. the phone,email,safari, and ipod icons dont work at all. since i have these dead spots on the bottom row of the phone and also in the middle of the phone. Would buying

  • Why can't I close my screen while using an external monitor?

    It goes to sleep of course. How can I change this? I'm not seeing anything in the power settings. Thanks!

  • Why has Safari become so unstable?

    Lately, Safari crashes within minutes, almost every time I use it. It crashes on an unpredictable array of websites (apple.com, nytimes.com, facebook.com). It will crash even when its not the active window. I don't remember when this began, but I rec