Code View Wrong Color

After I posted the message about changing the default font
for the application I applied the results and the default font
changed.
Then my code font was fine except it mostly turned BLUE. How
can I make it BLACK again?
Roger
[email protected]

Roger,
First, make sure the syntax (i.e. code) coloring is turned on
here:
View > Code View Options > Syntax Coloring
If that's on, then you have a syntax error on your page at
the place
where the coloring changes from "fine" to "BLUE". The
coloring is for
more than just making you page look pretty!
Hope this helps,
Randy
> Then my code font was fine except it mostly turned BLUE.
How can I make it
> BLACK again?

Similar Messages

Code View not coloring HTML

I don't know what I did, but DW8 is not coloring the HTML of
any of my
sites.
Help!
SC

Did you double-check your preferences?
SC wrote:
> I thought that might be it. However, when I open other,
older
> "Sites", I get the same black on white HTML...
>
> Also... there are no line numbers on the left in "code
view"...
>
> Argh!
>
> Sam

DW code view custom highlight color from design view (split view)

I would like to change the "Code view" highlight color from it's default to something more contrasty ... so while using "Split view" - when I select an element in "Design View" the corresponding code in "Code view" would be easier to find ...
Anyone knows how to customize this setting wit DW CS5??
Thanks!

I would like to change the "Code view" highlight color from it's default to something more contrasty ... so while using "Split view" - when I select an element in "Design View" the corresponding code in "Code view" would be easier to find ...
Anyone knows how to customize this setting wit DW CS5??
DW Code View uses the Selection colors defined for your Operating System.
If you don't know how to change that, which OS and version are you using?
HTH,
Randy

Can you disable the color picker in code view?

One of the things that slows me down in Dreamweaver is the color picker in code view. it pops up when I'm trying to type a quick colour - like #fff, and causes a pause in my system for 5 seconds (effectively locking up my system) while it thinks about selecting a color. is there a way I can just stop the color picker from popping up at all? I never use it to pick colors.

There is no way to disable the colour picker in Code view. However, you can successfully prevent it from popping up by changing the delay in Preferences:
Setting the delay affects all code hints, but they pop up as soon as you start typing. However, I found that a delay of about 1 second was sufficient to suppress the colour picker.

In dreamweaver cs6 12.0, build 5842, there is no syntax coloring on main code view?

In my dreamweaver CS6, why is there no syntax coloring showing on the main code view window on php or any files? It works in window>code inspector, but this does not have all the same functionality. ther is no preferences icon anywhere that I can see to turn this feature on or off? This used to work until just recently. Nothing on google, but the main basics. I tried checking preferences under syntax coloring and all is okay and shows color. I also reinstalled and restarted PC. I am on a macbook with retina display. on mountain lion with latest updates. CS6 is different than cs5 in menus. Please help soon!

Thanks for the help. I didn't think the retina did, I just wanted to help clarify what I was working with. I tried changing the external editor also and that got the split design view working again, but still no code coloring gosh darnit.

Is it possible to change color on the line strip/code view in CS6?

Hello -
I did some research on this and cant seem to see if this can be done - I was hoping to change the color of the blue line menu on the code view screen.
Eric

I take it you're referring to that vertical line in the left hand side of Code View? I don't think it's possible to change the color. If you disable line numbers (#), it's a bit less noticeable.
Nancy O.

Syntax coloring in code view not working in CS6

I just got CS6 installed for Windows XP, first time using it, and the HTML syntax is no longer color coded like I was used to in CS5 and earlier.. I assume you would turn this on/off through View > Code View Options > Syntax Coloring, but when I try to select this, nothing happens and the option remains unchecked in the menu.
It seems to be the only thing in the Code View Options menu that I cannot turn on/off, but it's not grayed out or turning up any error messages or anything...
Any idea what's going on?

I didn't have a previous version of Creative Suite before this, so nothing to clean off. It's a work PC that just got set up with CS6 for the first time - I wasn't able to find that cache file (the instructions are for CS5 and earlier), but since this started happening straight out of the box, I'm not sure the cache would be the problem?
And no, the "Syntax Coloring" option is not greyed out - it's actually black, so looks like it SHOULD be selectable, but I click it and nothing happens, and it remains unchecked. That's the confusing thing.. no obvious hurdles to toggling that option...

No colored code view

I have the problem that my dreamweaver 8 don't displays
colored codes in the code view
can somebody help me?
plz

A.Translator wrote:
> Edit > Preferences > Code Coloring
That allows you to change the default colours. If Code view
isn't
displaying the default colours, go to View > Code view
options, and
select Syntax coloring. This option is toggled on and off by
selecting
it. If there is a check mark next to Syntax coloring, it's
on. If
there's no check mark, it's off.
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of
ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

Viewer is displaying wrong colors in Develop when not zoomed 1:1

I'm experiencing some strange behaviors in Lightroom under the DEVELOP module when looking a non 1:1 zoomed image (let's say when you're in FIT mode or FILL...).
The colors of the photo are different. At first, I thought it was a viewer resampling problem but it's not since the colors are fine under the LIBRARY module (when set to FIT or to FILL).
So, for me, the only way to work with accurate colors under the DEVELOP module is to set the viewer to 1:1 which is not always convenient.
Note that this only apply to .cr2 files (raw files) coming from my Rebel XSI...
If I export a .cr2 file to .tif 16 bit uncompressed and bring it back in Lightroom the colors (the good ones) stay the same for every zoom factor.
So, if I look at the same photo (viewer zoomed to FIT) under LIBRARY (loupe view) and DEVELOP (loupe view), the colors are NOT the same.
If I look at the same photo (viewer zoomed to 1:1) under LIBRARY (loupe view) and DEVELOP (loupe view), the colors are the same.
I attached 2 screenshots, one for the LIBRARY module and one for the DEVELOP module with the viewer set to FIT.
Judge by yourself...
Thanks!
Danny

Oh Sorry, these screenshots were paste in Photoshop in ProPhoto RGB, here are the sRGB screenshots :
After reading some other related posts, I found out that the issue is related to the Develop module (as Jao vdl pointed out) for not applying Detail filters to the viewer when smaller than 1:1....
I hope that Adobe are aware of that and will at least put an option for that in a near future...
I really would like to have answers from someone at Adobe regarding that behavior.
Thanks in advance!
Danny

ImageIO: scaling and then saving to JPEG yields wrong colors

Hi,
when saving a scaled image to JPEG the colors are wrong (not just inverted) when viewing the file in an external viewer (e.g. Windows Image Viewer or The GIMP). Here's the example code:
public class Main {
     public static void main(String[] args) {
          if (args.length < 2) {
               System.out.println("Usage: app [input] [output]");
               return;
          try {
               BufferedImage image = ImageIO.read (new File(args[0]));
               AffineTransform xform = new AffineTransform();
               xform.scale(0.5, 0.5);
               AffineTransformOp op = new AffineTransformOp (xform, AffineTransformOp.TYPE_BILINEAR);
               BufferedImage out = op.filter(image,null);
               ImageIO.write(out, "jpg", new File(args[1]));
/* The following ImageViewer is a JComponent displaying
the buffered image - commented out for simplicity */
               ImageViewer imageViewer = new ImageViewer();
               imageViewer.setImage (ImageIO.read (new File(args[1])));
               imageViewer.setVisible (true);
          catch (Exception ex) {
               ex.printStackTrace();
Observations:
* viewing this JPEG in an external viewer displays the colors wrong, blue becomes reddish, skin color becomes brown, blue becomes greenish etc.
* when I skip the transformation and simply write the input 'image' instead the colors look perfect in an external viewer!
BufferedImage image = ImageIO.read (new File(args[0]));
ImageIO.write (image, "jpg", new File(args[1]));
* when I do the scale transformation but store as PNG instead the image looks perfect in external viewers!
BufferedImage out = op.filter(image,null);
ImageIO.write(out, "png", new File(args[1]));
* viewing the scaled JPEG image with The GIMP produces "more intense" (but still wrong) colors than when viewing with the Windows Image Viewer - I suspect that the JPEG doesn't produce plain RGB values when decompressed (another color space used then sRGB? double instead of int values?)
* Loading the saved image and display it in a JComponent shows the image fine:
class ViewComponent extends JComponent
     private Image image;
     protected void paintComponent( Graphics g )
          if ( image != null )
// image looks okay!
               g.drawImage( image, 0, 0, this );
     public void setImage( BufferedImage newImage )
          image = newImage;
          if ( image != null )
               repaint();
* Note that I've tried several input image formats (PNG, JPEG) and made sure that they were stored as RGB (not CMYK or the like).
* Someone else already mentioned that the RGB values as read from an JPG image are wrong, but no answer in this thread - might be connected with this problem: http://forum.java.sun.com/thread.jspa?forumID=20&threadID=612542
* I tried the jdk1.5.0_01 and jdk1.5.0_04 on Windows XP.
Any suggestions? Is this a bug in the ImageIO jpeg plugin? What am I doing wrong? Better try something like JAI or JIMI? I'd rather not...
Thanks a lot! Oliver
p.s. also posted to comp.lang.java.programmers today...

Try using TYPE_NEAREST_NEIGHBOR
rather than
TYPE_BILINEARI was a bit quick with saying that this doesn't work - I had extended my example code which made it fail (see later), but here's a working version first (note: I use the identity transform only for simplicity and to show that it really doesn't matter whether I scale, rotate or shear)):
// works, but only for TYPE_NEAREST_NEIGHBOR interpolation
Image image = ImageIO.read (new File(args[0]));
AffineTransform xform = new AffineTransform();
AffineTransformOp op = new AffineTransformOp (xform, AffineTransformOp.TYPE_NEAREST_NEIGHBOR);
BufferedImage out = op.filter(image, null);
ImageIO.write(out, "jpg", new File(args[1]));The problem: we restrict ourselves to nearest neighbor interpolation, which is especially visible when scaling up (or rotate, shear).
Now when I change the following, it doesn't work anymore, the stored image has type=0 instead of 5 then (which obviously doens't work with external viewers):
// doesn't work, since an extra alpha value is introduced, even
// for TYPE_NEAREST_NEIGHBOR
BufferedImage out = op.filter(image, op.createCompatibleDestImage(image, ColorModel.getRGBdefault()));Intuitively I would say that's exactly what I want, and RGB image with data type int (according to JavaDocs). That it has an alpha channel is a plus - or is it?
I think this extra alpha value is the root of all evil: JPEG doesn't support alpha, but I guess ImageIO still mixes this alpha value somehow into the JPEG data stream - for ImageIO that's not a problem, the JPEG data is decompressed correctly (even though the alpha values have become meaningless then, haven't checked that), but other JPEG viewers can't manage this ARGB format.
This also explains why writing to PNG worked, since PNG supports alpha channels.
And obviously an AffineTransformOp silently changes the image format from RGB to ARGB, but only for TYPE_BILINEAR and TYPE_CUBIC, not for TYPE_NEAREST_NEIGHBOR! Even though I can imagine why this is done like this (it's more efficient to calculate with 32 bit ints than with 24 bit packed values, hence the extra alpha byte...) I would at least expect the JPEG writer to ignore this extra alpha value - at least with the default settings and unless otherwise told with extra parameters! Now my code gets unnecessary complicated.
So how do I scale an image using bilinear (or even bicubic) interpolation, so that it get's displayed properly with external viewers? I found the following code working:
// works, but I need an extra buffer and draw operation - UGLY
// and UNNECESSARILY COMPLICATED (in my view)
BufferedImage image = ImageIO.read (new File(args[0]));
AffineTransform xform = new AffineTransform();
AffineTransformOp op = new AffineTransformOp (xform, AffineTransformOp.TYPE_BILINEAR);
BufferedImage out = op.filter(image, null);
// create yet another buffer with the proper RGB pixel structure
// (no alpha), draw transformed image 'out' into this buffer 'out2'
BufferedImage out2 = new BufferedImage (out.getWidth(), out.getHeight(),
                                                         BufferedImage.TYPE_INT_RGB);
Graphics2D g = out2.createGraphics();
g.drawRenderedImage(out, null);
ImageIO.write(out2, "jpg", args[1]);This is already way more complicated than the initial code - left alone that I need to create an extra image buffer, just to get rid of the alpha channel and do an extra drawing.
I've also tried to supply a BufferedImage as 2nd argument to the filter op to avoid the above:
ICC_ColorSpace (iccColorSpace = new ICC_ColorSpace (ICC_Profile.getInstance(ColorSpace.CS_sRGB)
BufferedImage out = op.filter(image, op.createCompatibleDestImage(image, new DirectColorModel (iccColorSpace), 24, 0xff0000, 0x00ff00, 0x0000ff, 0x000000, false, DataBuffer.TYPE_INT))); But then the filter operation failed ("Unable to transform src image") and I was beaten by the sheer possibilities of color spaces, ICC profiles, so I quickly gave up... and hey, I "just" want to load, scale and save to JPG!
The last option was getting a JPEG writer and its ImageWriteParam, trying to set the output image type:
iwparam.setDestinationType(ImageTypeSpecifier.createFromBufferedImageType(BufferedImage.TYPE_INT_RGB));But again I failed, the resulting image type was still type=0 (and not 5). So I gave up, realising that the Java API is still overly complex and "too design-patterned" for simple tasks :(
If anyone has still a good idea how to get rid of the alpha channel when writing to JPEG in a simple way (apart from creating an extra buffer as above, which works for me now...)... you're very welcome to enlighten me ;)
Cheers, Oliver
p.s. Jim, I will assign you the "DukeDollars", since your hint was somewhat correct :)

DW acting strange - does not go to code view

My Dreamweaver CS3 has started acting strangely since I
upgraded to a new version of CS3 studio.
I have been working with CS3 for a while now without needing
too much of an adjustment from DW8.
However, I just bought a new computer so I had to reinstall
all my software.
On the new box, DW is acting mighty strange:
1) When I am in Layout view and click on an element to go to
the corresponding line of code for the element it no longer goes to
the line. However, it does when I r-click on it. It is a bit
annoying since it also opens the contextual menu at the same time.
2) When I am in code view (which is 99% of the time) and I
click on an element, it no longer shows me the corresponding CSS
rule in the CSS pane. Again, if I r-click sometiomes it works, but
this one is not reliable either way. Sometimes it works if I double
click, but most of the time it doesn't.
3) The comment icon on the code toolbar is often grayed out.
No reason I can see and just as often it wil work on the same line
of code where it didn't work a minute before.
I combed the preferences line by line without success.
On my old computer I never had any issues like this. I find
it very strange and it is crimping my workflow considerably. Is
anyone familiar with theis behavior or how to fix it?

The times I have seen others post things like this, it's been
due to a bad
installation - reinstalling fixes it.
> What is the best way to transfer preferences, snippets,
etc. from one
> computer
> to another?
PREFERENCES? No way that I know of.
SNIPPETS? Copy the Configuration/Snippets folder from the
USER-specific
application folder and paste to a similar location on the new
computer.
XP-
C:\Documents and Settings\<user>\Application
Data\Adobe\Dreamweaver
9\Configuration\Snippets
(these folders are normally hidden - you may have to use
Explorer > Tools >
Folder Options to unhide them)
VISTA-
E:\Users\<user>\AppData\Roaming\Adobe\Dreamweaver
9\Configuration\Snippets
or on Mac -
Library/Application Support/Macromedia/Dreamweaver
9/Configuration/Snippets
SITE DEFINITIONS? Export from DW on one computer to portable
media, and
Import to the other.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"corradoconti" <[email protected]> wrote in
message
news:[email protected]...
>I also wanted to give an update on the exact behavior I
am experiencing:
>
> 1) I click on an element on the layout view and nothing
happens - I
> r-click
> and it works as intended (but the contextual menu also
pops up)
> 2) I select code in the code view and instead of
highlighting the
> corresponding element in design view, nothing happens.
> 3) When I r-click in design view on an element both the
code and the CSS
> rule
> hightlights but when I select an element in code view
the CSS pane does
> not
> respond at all. Other times it does show a rule but it
always the last
> rule in
> my css, not the one I am selecting in code view.
> 4) I click on a CSS rule in the CSS pane and I cannot go
to the
> corresponding
> line of code in the CSS file about 70% of the time. When
it does work half
> the
> time it takes me to the wrong place in the css file.
> 5) In the code toolbar if I select a line of code all
the "Comment" and
> other
> icons on the left may or may not be greyed out.
Switching from one file to
> another (any file) and then come back to the original
file sometimes makes
> those same icons active once again.
> 6) On some files I cannot activate the "Visual Aids"
toolbar icon. It
> stays
> grayed out for that page until I switrch to another page
and come back.
>
> My guess is there are scores of other features not
working properly. I
> just
> haven't got to them yet.
>
> What is the best way to transfer preferences, snippets,
etc. from one
> computer
> to another? I want to try to capture my old preferences
(code coloring,
> file
> extensions, etc.) and see if that makes a difference. At
least, if I have
> to
> reinstall DW it would allow me to quickly set the new
copy up with the
> preferences that worked just fine on my other computer.
>

ASP / Code View Issues

Good morning to all of you.
I have used Dreamweaver at work for many years to manage our extensive classic ASP applications. I like the interface but I have found that programming with a darker background is much easier on my eyes. I found some dark code view background profiles that covered HTML/PHP/CFM files and loved how they looked on those type of projects but they were lacking ASP support. I took the time to create the profile for ASP Vbscript and then copied it to ASP Javascript so no matter what language I'm in they will be the same. It looks great but I have to fake out Dreamweaver to force it to view the code in the right file type. It seems Dreamweaver is pretty inconsistent with determining the ASP file/language type.
If I use:
<% @Language="vbscript" %>
It will load the correct profile and things seem well. If I don't do that, I not only don't get the correct coding but the commenting doesn't look right either. I have to end every line with that has a comment a single apostrophe as well to keep it from getting the code view appearance looking wrong.
This hackish attempt above works but it bad style. You can't define this more than once in a document and would be problmenatic if you use include files (who doesn't really?)...
I almost exclusively code ASP-VB. How can I make Dreamweaver read ALL ASP files in this the ASP-VB format by default? As it sits right now, it's totally wrong.
Thanks in advance,
Joe Jenkins

It's not so much doing with the actual language. It's the fact that Dreamweaver doesn't recognize that the .asp file is indeed ASP so it applied the wrong code view coloring, rules for comments and no suggestive code. If I am drop the language in the top of the file, this corrects THAT file but if you have multiple include files and you push it to your server like this (wish this language definition in each of those files) you will get an error from the server for multiple definitions.
Exmaple:
Top of main file:
<%@Language="vbscript" %>



Top of an included file:
<%@Language="vbscript" %>
<%
dim StartTime : StartTime = Timer()
Session.Timeout = 120
If you tried to fake out the code view by doing that to MAKE it view the file as an ASP-VB file, it's not only bad practice, it's redundant and the server will cough at it giving you an error that simply tells you that the declaration has to be on the first line. This is true, in the main file, but the included file would then put it inline on whatever line it happens to be as part of the compiled page which is invalid.
The main problem is that I have to fake out the code view by defining the language on every page I edit to get text-coloring right and other features. The question is can I make it always default to maybe ASP-VB unless explicitely defined something else like @Language="Javascript" ?
Joe Jenkins

DW CS5 displays image wrong color

I have an image created in Photoshop CS5 which I am using as a header image in DW CS5. I have made sure the hex code for the clolor matches in both programs but DW shows the wrong color but when I view the page in Firefox or Safari the color displays correctly. I really can't understand why DW does not display the correct color since the color codes are the same as what is shown in Photoshop and displays correctly in Photoshop.
Any help is appreciated.

I guess its OK to reply to my own question! The problem is the jpg file. There is no problem when the image is saved as png file. All the browsers and DW display the color correctly now. I still would appreciate any comments that might shed some light on the differences between jpg and png that might cause something like this.
Thanks

Eyedropper in PS CS6 picking wrong color

My eyedropper started picking the wrong color! I ahve reset and reinstalled PS - and still have this problem. No matter what color I click the eyedropper on, it picks a shade darker than what I want. Anyone have any ideas? Like I said, I am running PS CS6 on OS Mountain Lion.

hanci wrote:
I also have problems with the eyedropper in RGB mode. I have a blue background color and when selecting it with the eyedropper I get #244f69 when I'm in RGB mode. And if I use that color in CSS on a website, the color gets darger than the original color in Photoshop. But if I change to CMYK mode and use the eyedropper again, then i get this code on the same background #00516a. And with that code I get the color I want on the website.
Adobe Photoshop Version: 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00) x64
Am I doing something wrong?
Apart from your Photoshop needing updated to at least 13.0.1, the problem may be that your RGB document, which you're sampling in Photoshop, does not have sRGB profile and/or your Web browser is not colour managed and/or your computer is not using a correctly calibrated monitor profile and/or something else.

Editing tags in code view

im relatively new to dw 8 and have a problem. in split vied
or code view I cant edit change or remove tags. ie if i want to
remove a <font> tag. i can highlight it in the code view
window but if i try to cut nothing happens. Im sure i just have a
setting wrong but what?

Is the code in question black or gray?? If ou are using a DW
teomplate,
some of our code areas will be "locked" (gray) and uneditible
unless you
edit the template itself. Make sense?
Alex

Code View Wrong Color

Similar Messages

Maybe you are looking for