Docking palettes in CS5

How do I dock my palettes to the r/h side of the screen? They were docked when I first installed CS5, but after organising the palettes as I want them, I can no longer get them to dock - short of resetting the workspace to default.

Glad it helped.
It should be quicker than 15s. Try dragging till it's nearly out of the window.

Similar Messages

Want actions from CS2 action palette in CS5

Hello, I had Photoshop CS2 on my old laptop and created some actions for improving photographs. That computer died but I managed to save the hard drive. On my new laptop I have Photoshop CS5 and I'm desperate to be able to use my old actions. I have the action palette.psp file from my CS2 files - is there a way I can 'put that into' my CS5 folders so I can access the actions? Grateful for any help!

What you could try is to go to the preferences folder...
http://kb2.adobe.com/cps/828/cpsid_82893.html
Rename the actions file, and put the cs2 file in its place, start Photoshop then save the action sets out. Close Photoshop. Remove the CS2 file and rename the actions file back again, start Photoshop and load the actions sets you have just saved.
I don't have CS5 on a Mac but it looks as if the documentation could be wrong as it shows "Actions panel.psp" for the actions file?
Should this be "Action Palette.psp"
Edit: - yes the documentation is incorrect.

Transferring Actions Palette from CS5 on PC to CS6 on Mac

I recently upgraded from CS5 to CS6. The CS5 license was on a PC, the CS6 license is on my new Mac.
I have access to my old PC still, but I have not been able to figure out how to transfer my Actions or my Camera Raw presets (.XMP files) to the Mac. I need access to these Actions asap and am not able to recreate them. Would very much appreciate any help on this.

Hello, you need to save the actions from the Actions panel's flyout menu to a given location (some make a copy in an online folder) , and load them from the equivalent panel in CS6.
In ACR, are those presets, or develop settings for each photo? If the latter, copy them over with the photos.

No path palette in CS5

Hello,
I need help. I can't find the path palette.
Thank u for ur help....

The palette has been closed for some reason.
Click Window > Paths to re-open it

PSE 4 Docking and Grouping Palettes together

I'm looking in my manual (page 38)about how to group palettes together and how to dock them together. This whole section seems to be written by someone who hasn't ever really used PSE4.
What is the difference between grouping palettes together and docking palettes together? And how the heck to I do it?
What I want is to have my little palettes with there tabs right next to each other kind of like a filing system so when I click on a tab that is the palette that shows up on top. No need for all the expanding and contracting. That's pretty much how it looked in PSE 2.0.

First of all, drag your palettes out of the bin. Then click the arrow at the upper right of each one and uncheck "close to palette bin.." Then drag the
tab of one palette onto the tab of another one, the same way you can do in PE2. They should combine into one multi-tabbed palette.

"Fit to Screen" while in full screen mode - image fits behind palettes.

Is there a way to "fit to screen" when in full screen mode and NOT have my image go behind my open palettes (Layers, etc.)? I am hoping there's a way for me to hit command zero and have my image fit perfectly between palettes. Every time I hit command zero I have to readjust my image or zoom out so I can see the whole thing. (Photoshop CS5)

Not that I know of. I address this problem two way. I add a second display an move the Photoshop Pallets I use the most out of Photoshop's main window onto the second display docked to each other and open expanded. The Palettes I do not use often I dock to Photoshop Main windows right side collapsed. Even if you do a view actual pixel Photoshop only zoom the image area to all the space between the docked tools palette on the left and the collapse docked palettes on the right. The pallet are only over the image window when you expand one open to use it. If you view the following screen capture in a new tab or window you can scale it to its actual size and scroll around over it. My TwoScreen workspace....

CS4 always opens with palettes minimised: how to change?

Hi
For some reason my docked palettes have taken to being minimised when I launch Photoshop. Never used to be like that, they launched just how I like them to be (four groups, all open on launch), but I must have accidentally changed something 'coz they don't now.
Ok, it's only an extra four double clicks to open them all up, but it is irritating.
I can't find the setting that puts it back as I want it. I've tried saving the opened palettes as a new workspace, but no joy.
Can anyone tell me how to get my perfect workspace back, please?!
Thanks in advance.
TP

Hi panorama - thanks for the reply.
Good idea, but I had already resaved the workspace with the palettes open, but it still insisted on opening photoshop with them minimised.
I've now fixed by deleting the prefs file and recreating the preferred layout and resaving the workspace. The prefs file in W7 is in users/username/AppData/Roaming/Adobe/Adobe Photoshop CS4/Adobe Photoshop CS4 Settings and it is called Adobe Photoshop X64 CS4 Prefs.psp
I'm sure there's an easier way to fix it, but trashing the prefs file does fix it.
Thanks to everyone for their suggestions.
TP

14.2 updates changes width of Swatches palette

Hi, as soon as I updated ps cc to 14.2 the swatches palette, when docked does not behave correctly: all swatches are placed as you have resized the palette, placing them in wrong order. Undocking the palette reposition the swatches correctly.
I've made sure the docked palette is not scaled, in fact even on brand new, reset "essential" preset interface displays the issue even with default palette.
Scaling the docked palettes does not fix the problem.
Here's an example with the DEFAULT interface on a fresh installation
first one is the unlocked palette, works as expected
second one is the docked palette (wich is on the default Essentials UI!)
My guess is that the minimum docked palette width has increased by some pixels with the update. This may look like a minor issue, but it skrewed up all my custom palettes

The panel is not "broken", but its minimum width has increased due to the inclusion of the new longer phrase "Smart Object" in the Layers panel options filter list.
Specifically, for the English-language interface (on Windows using a non-4K monitor and standard font sizes), CC 14.1.x and CS6 had the same smaller Layers panel minimum width of 224px, as compared to the new wider minimum of 242px in CC 14.2:
Even for a particular version of Photoshop, things that change the length of words, such as user-interface language, and the size of the letters or symbols, such as the typeface and size of the fonts used for the user-interface, would affect minimum panel width. In other words, I suspect German users have a wider minimum Layers panel width, and Chinese users have a narrower minimum Layers panel width, and users with Retina or 4K displays also have different sizes for things due to the much higher resolution.

Transfer brushes from cs5 to adobe cc

can you transfer brushes and colour palettes from cs5 into photoshop cc?

Sure. Simply save them as abr and ase files from the flyouts in the relevant palettes and load them the same way.
Mylenium

FreeHand has a new App Icon

John Nack at Adobe has published a color wheel of ALL the
redesigned application icons and color schemes.
See
it here
If you look in the south west quadrant you will see the FH of
FreeHand Icon. Is this good news for the future?

> and last night while trying the PS CS3 beta I felt that
the interface is actually similar to FHMX.
I really don't don't see how you get that. Sounds like alot
of *really* wishful thinking to me.
It looks to me that all they've done is given PS (and
presumably the other CS3 apps) a new palette docking interface.
This is something Illustrator--in typical Illustrator fashion--has
been years behind. But PS and InD already have palette docking
ability; they just didn't match. So now Adobe is (again,
presumably) building the "next generation" of the "unified Adobe
interface", which if history tells, they will probably consider
"locked in" for at least several years thereafter. If this is all
the hullabaloo is about, we're in for another many years of
behind-the-times Adobe interface, because while this would be an
improvement for AI, it is little more than a facelift for PS and
InD.
To say this is "similar to FreeHand" or even similar to the
Macromedia structure is a far stretch. There is nothing original in
the idea of simply docking palettes to the right edge of the main
monitor. The main principle that separates the MM interface scheme
from Adobe's is the use of the "contextual inspector"
organizational model, which is followed in all the MM apps. I see
nothing to indicate that in the PS3 layout. It's just the same old
palettes now able to dock in a way different from the rather
half-baked palette docker in the previous version. What's the big
deal?
The original Adobe Creative Suite apps (AI, PS, InD) all
still cling to the long-outdated model wherein you have many
separate palettes for all the separate attributes of the selection.
That's much more tolerable in a raster imagng program, because
raster imaging is not nearly so "object oriented" as page layout
and vector illustration. That is, even with all the bells and
whistles that have been added to Photoshop over the ages, you are
still working with one raster image--or a subset selection of
pixels in that one image--at a time. Yes, PS nowadays stacks
several images with the same resolution on top of each other and
calls them "layers." And in recent years, it even allows you to
place vector clipping paths within those "layers" and calls them
"shape layers."
But that's all still a far cry from the object-oriented
nature of vector drawing programs.
Way, way back (when was it? FH3? FH5.5?), FH was rebuilt upon
the more modern (and profoundly more efficient) "contextual
inspector" model. From that day forward, you no longer had to go
scouring all over a kazillion separate palettes to set the selected
path's fill, stroke, overprint attributes, etc., etc. It is all
right there in the fully contextual Inspector Palette. (It was
actually called the "Inspector Palette" back then. It was changed
to Object Properties when a stylistic uniformity was applied across
the other and newer MM apps.)
The only CS app which comes close to a true inspector-baed
interface is the one Adobe didn't author: GoLive. (We won't even
get into Acrobat's completely arbitrary interface, which
matches--well--nothing.)
When MM stylistcally unified the interfaces, it also made
them dockable to the right edge of the main monitor. But that
docking aspect is a far less important difference from the old
fashioned interface scheme than the functional reorganization of
the contextual inspector model.
*That's* the crucial difference between MM's stylistically
unified interface and Adobe's. This is best seen by comparing not
the schemes of FH and PS3; but those of FH and AI:
Setting mere palette docking aside, In both programs you
still have a separate palette for mixing colors, for storing
swatches, for defining styles, etc. But the real difference is both
subtle and profound. In AI, those individual palettes don't only
create and store all those myriad settings, but they must be used
to *view and apply* them.
In FH, you work far more efficiently by using the various
palettes to create and store settings, but you *view and apply*
them in the context of the current selection in the all-inclusive
and much more informative Object Properties palette. Defined
(stored) swatches automatically appear as selections in the
Properties pallette's popup menu. Same for styles, brushes, stroke
weights, overprint attributes--you name it.
The Object Inspector becomes your one-stop-shop for
everything you need to know about the current selection. It tells
you the number of points in the path; the effects applied; its
position and dimensions; its overprint attributes, its applied
styles, and on and on. So it tells you everyting about the
selection that AI's Appearance Palette does, but much much more and
in a much more concise and organized way (and in less space).
It is fully cotextual. For example, subselect some points and
you can change them from corners, curves, or connectors; retract or
extend their handles, right there in the same place you looked for
whole-object attributes: the Properties Palette.
Understand this is quite different from a limited "control
bar" like AI CS2's much ballyhooed but anemic Control Palette. That
kind of thing merely shows you a grab-bag collection of someone's
idea of the "most commonly needed" settings. For example, you still
have to dig for the ill-conceived Attributes palette to see if one
of the object's fills or strokes is set to overprint; or to a
buried sub-menu selection of the Document Info palette to see its
number of points.
That last is a good example. I ask you: What would compel a
new AI user who wants to know the number of points in a path, or
whether it is open or closed, to go look for something called the
Document Info palette?
Do you see what I mean? AI's dated, scattered, and cluttered
interface is what makes it so difficult for new users. New users
then mistakenly perceive "difficult" as "sophisticated" or
"powerful" when in fact quite the opposite is true. Proficient FH
users know this. The better organizational scheme which makes
finding settings more understandable and less frustrating for
newcomers also makes every moment of every workaday situation more
efficient and less tedious for proficient users--even long after
they've learned where all that information resides in AI.
The closest thing AI has to the concept of an object
inspector is not its Control Palette, but its Appearance palette.
But this also falls very short. It now shows the weight of each
stroke, and whether it is set to overprint, but doesn't let you
*change* those attributes. It doesn't tell you what its color
values are, or what kind of endcaps and joins it has. It indents
the individual strokes, fills, and effects under its item type
(path, compound path), but clicking that item type listing doesn't
provide the object-level attributes ( number of points,
open/closed, winding rule).
So AI's Appearance Palette and Control Palette are both mere
*pretenders* (and strain) to a proper object inspector, but both
leave so much out that they end up *adding to* the overall
palette-glut rather than serving to alleviate it. Neither of them
can be trusted to provide information complete enough to let you
chose to leave other palettes closed.
The difference has little to do with style. It has everything
to do with organizational efficiency. That's why just giving AI
dockable palettes (although long overdue) will still fall very very
short if it is not accompanied by the other side of the coin: a
thorough and careful rework of its functional organization.
I take no encouragement at all in the PS3 preview to suggest
that Adobe now "gets it" about the true advantage of their acquired
MM apps' interfaces. In fact, quite the contrary.
JET

How do I unfloat windows in Photoshop 7

I have Photoshop 7.0 on a Windows XP system.
Somehow I got all the little windows operating independently of the main window. Based on appends discussing how to do this in other versions of Photoshop, I think this is called "float".
This means that if i move the main window, all the little action windows ("Tools", "Options", Navigator, Color, etc.) stay where they were. I want them all to stay together, with the window that has the picture I am editing.
I realize that it is sometimes useful to sometimes have these little windows off somewhere else, but I have two large monitors (full HD) and I'd like to keep all of these little windows with the picture.
Thanks.

Hi,
In photoshop 7 the palettes are always floating, though you can dock the palettes in the Palette Well or together and then move them around the screen all at once like the following:
Docking the Navigator and Info together
(drag the Tilte of the palette next to the other one until you see a sort of ahighlight and then release)
You can also dock palettes to the bottom of other palettes
Docking the color palette to the bottom of the navigator and info palettes
(drag the Tilte of the palette to the bottom of the others until you see kind of a double line and release)
Then you can drag the very top of the palette stack around.
You can also dock palettes in the Palette Well
Drag on the Tilte of the pallete to the Palette Well and release
Then you can click on the Title of the palette to expand it
if you find a layout that works, then you can save it under Window>Workspace>Save Workspace

[PC / Mac] Modal vs. Non-modal ScriptUI windows issue

Hi,
in Photoshop ScriptUI 'dialog' Windows are supported (they're modal windows), while 'palette' Window's behavior is peculiar (they're non-modal, and as long as there's something going on in the script, they keep displaying - otherwise they automatically close). Apparently, this is different in InDesign (for instance), where palettes can stay idle - at least this is what I've been told.
I've found a couple of workarounds to work with palette Windows (my goal is to show them in order to let the user interact with either PS and the script's GUI - just like you'd do with regular panels and extensions - that is: to work with them as non-modal, idle palettes that mimic extension behavior), namely:
// usual Window stuff
win.show()
while (isDone === false) { // isDone is set true in win.onClose() etc.
app.refresh();
or
var s2t = function(stringID) {
return app.stringIDToTypeID(stringID);
var waitForRedraw = function() {
var d;
d = new ActionDescriptor();
d.putEnumerated(s2t('state'), s2t('state'), s2t('redrawComplete'));
return executeAction(s2t('wait'), d, DialogModes.NO);
// Window stuff
while (isDone === false) { // isDone is set true in win.onClose() etc.
waitForRedraw()
The problem is as follows:
1. They both work on Mac, either CS5 and CS6
2. app.refresh() seems to work on PC + CS5, but not PC + CS6
3. waitForRedraw() fails on both PC + CS5 and PC + CS6.
Mind you: When I wrote that the workarounds fails in CS5 and/or CS6 on PC, I mean that the 'palette', idle windows are modal and not non-modal as it is on Mac (which is my main coding platform).
[EDIT] Further testing has shown that PC palettes are... halfway between modal and non-modal. For instance, you can click on menus, but not select a Tool; you can collapse or drag a panel, but not access its content. You can't absolutely click on the image - for instance I'm desperately trying to enable panning on PC palettes: no way, you can't have the Hand tool to click&drag the image. For some reason, a "soft-scrolling" is enabled (on my MacBookPro, two fingers scrolling in all directions in the trackpad - but how to mimic this behavior in a desktop PC with no trackpad I don't know). Weirdly enough, the trackpad's "soft-scrolling" works in all directions on PC + CS5 64bits only, either CS5 @32bits, CS6 @32/64bits goes up and down only, no left/right allowed - frankly, to deal with platform-dependent issues is one thing, to take into account 32/64bits too is... ehm...
So, to sum up there are big differences in the ScriptUI behavior depending on how platform and PS version are combined:
PC, 'palette' Window:
CS5 + waitForRedraw() = modal
CS5 + app.refresh() = non-modal
CS6 + (app.refresh() OR waitForRedraw()) = modal
Mac, 'palette' Window:
(CS5 OR CS6) + (app.refresh() OR waitForRedraw()) = non-modal
Is there any... "working workaround" to make on PC CS6 a 'palette' ScriptUI Window to keep a non-modal, idling behavior? (the unasked question is: why is that palettes are behaving as non-modal in CS5 and not in CS6?! )
Thanks in advance!
Davide
Message was edited by: DBarranca - added blue text, further testing comparing 32/64bit versions

In the meantime, I've published two posts either describing in detail my issues:
ScriptUI Window in Photoshop - palette vs. dialog
and testing a workaround:
ScriptUI - BridgeTalk persistent window examples
Hopefully they may be useful to others as well.
Regards
Davide

LabVIEW IDE Overhaul

1. Allow for "Tabbed Browsing" of VI's to better manage windows.2. Allow for the BD to be open independent of the FP.3. Allow dockable palettes... dock to either the edge of the screen, or to the top bar (pictured below) of LabVIEW.4. As a bonus, consider being able to open PDF's, txt's, and html's in tabs also for Help and documentation.5. Finally, allow the project tree to be docked into the IDE. Please, add your own IDE upgrade ideas in this discussion - illustrations will be especially helpful here. If it's a major enough idea, create a new idea!

In response to altenbach: 1. The problem of "hiding the titles" for 60 tabs could break down fairly easily. Let's say, when you double click a VI in the docked project it automatically jumps to the tab of the BD of that VI. If there is not a tab, it creates a tab. Now, your "window manager" becomes very clean - a hierchal view of all VI's in the project. Now, you have a list of about 20 text items you can visually scan and choose, rather than a WIN+Tab that you have to scroll through. And when you CTRL+E, it brings up the FP in a SEPARATE window (Ok, completely ditch the "FP in a tab" idea.) Would you propose a more elegant method of scanning through 30 VI's? 2. This is important to remember: Like most integrated, tabbed IDE's, you can resize the relative size of each element. Have a vertical divider that makes the tabs larger and project smaller. Have options that remove the docked palettes from the top of the window. 3. Comparing two small VI's would be easier with the tabbed method! Consider the case structure, and CTRL+Scrolling through the cases. When I want to compare two very similar cases, I CTRL+scroll Up, Down, Up, Down, comparing differences. Take two VI's in adjacent tabs: you could click a tab, then Arrow Left, Right, Left, Right, comparing differences. The overlay method of comparing (think the animated sketch artist, flipping up and down the previous frame in his or her sketchbook) is easier than side-by-side comparisons (remember the "can you find the differences between these two pictures" in your kid's coloring books? Subtle differences are not as readily evident). 4. Copy and pasting between two VI's, I normally do by dragging. In this case, you're right, two side by side windows is better. I suppose we would more heavily rely on CTRL+C and CTRL+V. I would readily accept this standardized concession. 5. The "one size fits all" container could DEFINITELY not apply to a FP (!!!), but there's no reason why it could not suit a BD! By default, all FP's have both vertical and horizontal scrollbars turned on. The size of the container is boundless... but the size of the viewing window is limited to how large you physically make the Windows window... just like today! Just make your environment window as large as your largest VI, and then the smaller VI's will have white space around them (pretty much like my original screenshot... a small BD in a larger window). 6. Although MSWord ditched MDI, Excel didnt'! Why? The nature of the documents open is dramatically different. Are you likely to be jumping around from .doc to .doc? Eh, maybe. How about .xls to .xls? Much more likely. How about from .vi to .vi? WAY more likely!! 7. Font toolbar... money. Pre-Kudos. (Just make it dockable!) 8. MDI for a LV deity? Jail. MDI for mere mortals? Productivity. MDI for NI? Sales. (A little dramatic? Arguable.) To jlokanis: 1. Windows 7 has a MUCH improved taskbar. It provides basically exactly what you are talking about - a window manager with one icon on the taskbar. I will use Windows 7, and it will suffice until LabVIEW offers a tabbed IDE.Message Edited by mechelecengr on 07-27-2009 08:58 PM

Photoshop CS5 Palettes refusing to dock

If I try and re-arrange my palettes in Photoshop, I cannot get any of them to redock. As soon as I start to drag a palette or palette group, it becomes a stand alone window (with a close icon), and refuses to redock into a new position. The only way I can get the palette back into the main collapsible dock is to reset the workspace.
This means that I can't rearrange any of my palettes within the collapsible dock, which is very frustrating. I've tried throwing away all Photoshop CS5 preferences and plist files, but the problem persists. Has anyone else encountered this problem? I'm running Photoshop 12.0.1 on Mac OS X 10.5.8.

Resolved: restarting my machine has fixed the problem. I didn't try this sooner, as I simply don't expect this sort of behaviour from Mac apps.

CS4 & CS5 Swatches Palette

Hi there, i know this is small but i wondered if we could have it fixed for CS6. CS3< were fine with this because they did not have custon UI, but CS4 was bad, and CS5 is slightly better but still wrong.
Its just the swatches window, all of the colors are offset compaired to the old version where they were laid out properly. This image shows what i mean:
http://i151.photobucket.com/albums/s133/rickyt_album/imageofswatches.jpg
If this small UI error could be fixed it would be much appreciated!! I have also noticed the Mac version of CS5 does not have this it seems.

To reinforce what Chris has said, drag the Swatches palette out of its docked position by its little tab...
-Noel

Docking palettes in CS5

Similar Messages

Maybe you are looking for