Setting defaut look and feel under Gnome generates errors.

We are migrating some of our developer machines to linux, and in the process we are testing in house applications to ensure that in program file locations are correct and that everything just works. Each of our applications set the default look and feel at startup, which hasn't been a problem until now. Errors are being generated, despite no apparent affect on the application or how the application looks. Commenting out the the line of code that sets default look and feel result in an application that looks exactly the same, but with no errors. Keeping the line commented isn't an option, since the applications look horrendous in a Windows environment w/o the Windows L&F.
My question is: Since these errors have no apparent affect on the application, do we need to worry about them? Can they be safely ignored?
UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName());will generate errors during application lifetime, a snippet of the errors:
(<unknown>:16565): Gtk-WARNING **: Attempting to add a widget with type GtkButton to a GtkComboBoxEntry (need an instance of GtkEntry or of a subclass)
(<unknown>:16565): Gtk-CRITICAL **: gtk_widget_realize: assertion `GTK_WIDGET_ANCHORED (widget) || GTK_IS_INVISIBLE (widget)' failed
(<unknown>:16565): Gtk-CRITICAL **: gtk_paint_box: assertion `style->depth == gdk_drawable_get_depth (window)' failed
(<unknown>:16565): Gtk-CRITICAL **: gtk_paint_box: assertion `style->depth == gdk_drawable_get_depth (window)' failed

It's a bug in jdk
look here http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6624717
and vote for it

Similar Messages

Having trouble setting the look and feel

hi, i've almost finished my app and am trying to improve it's appearance. I'm trying to change the look and feel but i can't seem to get any changes to take effect. i've been reading through the tutorial on L&F but obviously am not 'getting' something.
At the moment all I'm trying to do, is to add the line below. I'm not totally sure where to put it though. I've tried putting it in the main method and nothing happens. I've also tried putting i the CreateandShowGUI() method and that doesn't seem to do anything either.
Where should it go?
try {
        UIManager.setLookAndFeel("javax.swing.plaf.metal.MetalLookAndFeel");
    } catch (Exception e) {
        System.err.println("Could not initialize java.awt Metal lnf");
    }

Put it before you start assembling your GUI, ie. instantiating and adding components.
Cheers
DB

Setting the Brushed Metal look and feel for macs using Java.

Hello,
I am relatively new to Java and I am new to Mac-specific java stuff. Anyways, when I try to set the look and feel of my classes to the "apple.awt.brushMetalLook" look and feel, I am unable to. It works if I have System.setProperty("apple.awt.brushMetalLook", "true"); written before I create any swing component. This would be fine, except that means that it is impossible to extend any swing component, such as JFrame or JApplet. Is there a way around this?
Thanks!

This might answer your question:
http://lists.apple.com/archives/Java-dev/2003/Apr/msg00829.html

JDeveloper 11g Look and Feel

Does someone know how to set Oracle Look and Feel used from JDeveloper 11g. There is one L&F oracle.bali.ewt.olaf.OracleLookAndFeel but it is something other. It looks like defined synth L&F but I can't find it in Oracle libraries.

I'm not 100% sure what you are asking - are you talking about the look and feel of the IDE (under tools ->options -> environment) or the look and feel of an application that is using EWT?

Changing look and feel with radio buttons

k this is the code that i have so far, Yes i read the tutorial and stuff but it doesnt seem to make any sense and all. tell me what else i need in this code to do what i want, its the action performed part i didnt put the other code, what else do i need??? but well...you will see grips of duke dollars to whom can do it
public void actionPerformed(ActionEvent e)
String actionCommand = e.getActionCommand();
if(actionCommand.equals("Metal"))
try
UIManager.setLookAndFeel( "javax.swing.plaf.metal.MetalLookAndFeel" );
catch (Exception ex)
else if(actionCommand.equals("Windows"))
try
UIManager.setLookAndFeel( "com.sun.java.swing.plaf.windows.WindowsLookAndFeel" );
catch (Exception ex)
else if(actionCommand.equals("Motif"))
try
UIManager.setLookAndFeel( "com.sun.java.swing.plaf.motif.MotifLookAndFeel");
catch (Exception ex)
}

While not in the tutorial, I have found several other things necessary to get the look and feel change to be complete. Here is the code I'm using after I set the look and feel. It seems to do a pretty good job of sync'ing everything together.
            SwingUtilities.updateComponentTreeUI(TDba.getFrame());
            TDba.getFrame().pack();
            Dimension dim = Toolkit.getDefaultToolkit().getScreenSize();
            Integer w = new Integer((int)(dim.width * .8));
            Integer h = new Integer((int)(dim.height * .8));
            TDba.getFrame().setSize(w.intValue(), h.intValue());
[\code]

Replacing part of a Look and Feel

Hi, all,
I have designed a new UI delegate for buttons (Both command buttons and toggle buttons), ones that fit better with the color palette, gradients, fonts, spacing, icons, borders, etc, that we have been using for much of the rest of our GUI. Up to now, I've been replacing the UI delegate of each button after I create it, but I'd like to do a global replacement of this UI for all buttons that use the default UI delegate. That way, I can still use things like JOptionPane.showXXXMessage(), and those buttons will be updated as well.
The only way I can find to do this is to write a new Look and Feel, but I only have a new UI delegate for buttons, and I would like for any other JComponents to continue to use the default look and feel (that is, the system native look and feel, or which ever look and feel is set to be used in their properties, etc). Does anybody know of a way to tell the UIManager (or some other component it uses) to use my UI delegate for Buttons, and use it's defaults for everything else? Preferably without writing a new Look and Feel?
Thanks!
Adam

To make all buttons use the BasicButtonUI you set the following:
UIManager.put("ButtonUI", "javax.swing.plaf.basic.BasicButtonUI");I imagine that you can replace the class name with your own UI. Remember to do this after you set the look and feel.

Using menu to update look and feel

Hi all,
I am trying to update the look and feel of my application.
In the main method I set the look and feel to metal.However, I have created a menu with an option to change the look and feel at runtime. I want the user to be able to just select the required look, e.g. Windows,on the drop down menu and then have the application updated.
I know that the following does not work:
void jMenuItem10_actionPerformed(ActionEvent exc) {
try {
UIManager.setLookAndFeel("com.sun.java.swing.plaf.windows.WindowsLookAndFeel");
this.repaint();
catch(Exception excs) {
excs.printStackTrace();
Am I miles away from the correct solution or am I nearly there? All help gratefully received.
Regards.

After UIManager.setLookAndFeel() add this row:
SwingUtilities.updateComponentTreeUI(this);
I don't think you need this.repaint();
Hope this will help you!

Look and feel of self-service pages under Oracle Applications Manager (OAM)

Hi All,
After applying patches for upgrading the HRMS module from 12.1.3 to 12.1.5, look and feel of self-service pages under Oracle Applications Manager (OAM) changed means Buttons not appearing in proper manner. and look of pages are not in proper manner. This is happening for OAM self-service pages only.
Current HRMS patchset level : r12.hr_pf.b.delta.5
OS : RHEL 5.3 x86_64
Any idea please....
Thanks inadvance,
Regards,
900076.

You need to ask your DBA to delete the cached stylesheets in /OA_HTML/cabo/styles/cache/...
You will also need to delete your temporary internet files.
Once both and deleted, re-access the page and you will see the updated stylesheets.
(Note: individual users may need to delete their temporary internet files too else they will see an old version cached on their computer)
Explanation: In new releases Oracle may introduce new additional OAF components. Each OAF component is assigned a shortcode/id by browsers in alphabetical order and a stylesheet generated.
If a new item is introduced, the shortcode/ids will change. However if an old version of the stylesheet still exists it will apply the wrong style to the wrong component.

Problem setting look and feel

It seems like I'm not able to change the windows xp look and feel, I'm using this code to change it but nothing happens, the window comes out with windows LAF:
" public static void main(String[] args)
try {
UIManager.setLookAndFeel("javax.swing.plaf.metal.MetalLookAndFeel");
} catch (Exception e) { System.out.println(e.getMessage()); }
new Ventana();
Maybe... Am I missing some code? or a specific class needs to be downloaded?
I'd apreciate any help

That was not the problem, but thank you...
I finally noticed the problem, what I was trying to do was actually done by writting this:
JComponent.setDefaultLookAndFeelDecorated(true);
Sets the OceanTheme feel on, but I noticed that when you try to use it with a Jdialog and a JFileChooser you get some ugly colors. Orange/Brown with JDialogs and Green with JFileChoosers. Is this a bug or it's ment to do that?
Does somebody know how to fix it?
Thanks for your support

Setting Look and Feel gives error

Hi,
I get error when I use,
JFrame.setDefaultLookAndFeelDecorated(true);
cannot resolve symbol
symbol: method setDefaultLookAndFeelDecorated (boolean)
location : class javax.swing.JFrame
JFrame.setDefaultLookAndFeelDecorated(true);
^
1 error
I am running the example for JFrame in the site . PLease help!!

Hi,
that was solved!
thank u 4 ur time!
Do you know how to use aqua look and feel??
I have downloaded the files. demo.bat works fine! and I tested Aqua by editing demo.bat, but how to use it i nmy program?? what is the name to be given for setLookAndFeel(??)

How come setting look and feel not successful

class gameble{
public static void main(String argv[])throws Throwable{
try {
UIManager.setLookAndFeel(
UIManager.getCrossPlatformLookAndFeelClassName());
} catch (Exception e) { }
console cs = new console();
cs.addWindowListener(new GenericWindowListener(cs.tv));
cs.setLocation(320,0);
cs.show();
with the above codes, i want java look&feel, but it still shows me window look & feel. need your help!!

CroosPlatformLookAndFeelClassName looks almost exactly like the java default look and feel.
You can try other L&F like:
try{
UIManager.setLookAndFeel(getSystemLookAndFeelClassName());
//this will take the look and feel of the OS you are working with
catch(Exception e){
System.err.println(e.getMessage());
or
try{
UIManager.setLookAndFeel("com.sun.java.swing.plaf.motif.MotiveLookAndFeel");
//this will take the look and feel of the Unix OS
catch(Exception e){
System.err.println(e.getMessage());

How do I get a more modern look and feel for a compiled help file

I gather from reading various posts that there is no easy way
to generate a .chm file with a more modern look and feel (am I
right about this?). Are there no plug-ins available from Adobe that
will enable us to generate a help file that looks more modern?
I hesitate to move to flash help or something like that
because, of course, then the developers would have to hookup the
hundreds of dialog boxes we have in our product to the new files. I
also think that having one file is way easier to manage in terms of
getting updated help to the customers. What are online Help
developers generally delivering for apps where users are not
connected to the Internet except perhaps periodically while using
the software? I'm a writer (not a developer) so need soemthing that
is easy to implement :-)
Thanks for your help. It is much appreciated.

To add to the advice already offered, you can apply a skin to
a CHM file which allows you to customise it. However as with most
things there are issues with this approach. You can read about this
by downloading Rick Stone's excellent
tips
'n tricks file. Just look in the index under "skins". Something
else you may want to look at is the beta of Adobe's
AIR.

BSP - Look and Feel / Theme

Good Morning All,
disclaimer: I checked the blogs, I checked the discussions, I checked the examples, I checked the doco - and couldn't find the answer to my question.
Question:
I've already seen it, but can't remember where it is, does anyone know the name of the BSP Sample/Example which comes with the WAS which has the EP6 look and feel ?
I saw it a few weeks ago and I can't find it now and I want to study the code from it to make my app have a nicer look and feel.
Note: I read Thomas's blog on - 'A developer's Journal Part VI
and although that example discussed what I am interested in I couldn't see examples in the code of creating the header bar etc, maybe it's just me, but at the moment that's what I would like to achieve and to do it by example.
So to conclude if anyone knows / can remember the name of the BSP example which has an EP6 look and feel please let me know so that I can study it for inspiration.
Thanks very much,
Milan.

Hallo Milan,
I think that you are doing good. It is always the best to follow a small mix of documentation reading and practical work. So let me tell you the minimum to get a first version working. Thereafter to can continue reading!
Problem: we want to implement a simple link tag (in 15 minutes!) that works like this:
<%@page language="abap"%>
<%@extension name="htmlb" prefix="htmlb"%>
<%@extension name="bcm06" prefix="bcm06"%>
<htmlb:content design="design2003">
<htmlb:page>
 <bcm06:simpleLink href="http://www.sap.com">
 SAP Home Page!
 </bcm06:simpleLink>
</htmlb:page>
</htmlb:content>
In SE80 we defined a new BSP library bcm06. We define a new element simpleLink. Typical handler class name will be CL_BCM06_SIMPLELINK (just the convention we use). As body this tag can contain other HTML and also over BSP elements (we want to just render a link around all of body). We don't worry about the rest of the checkboxes. They will become interesting later on.
We activate the library. The workbench will detect that no handler class exists, and will generate all of the stuff we need. Now already the tag is full functional, and can be used on any BSP page. It just will not do anything.
What was generated? The class inheritance diagram is as follow: CL_BCM06_SIMPLELINK --> CLG_BCM06_SIMPLELINK --> CL_BSP_ELEMENT.
The class CL_BSP_ELEMENT is the base class, and it contains a lot of interesting functionality. None of which we worry about now. Never try to change it!
The class CLG_BCM06_SIMPLELINK (note that CLG_!) is generated new each and everytime that you touch the definition of the tag. Effectively all the defined attributes are generated onto this class, so that they are already of the correct type, and that this information is always in sync. This means that all your tag defined attributes are directly attributes on your class. In our case, the defined "href" attribute (type string) is now an attribute on the CLG class.
The last class CL_BCM06_SIMPLELINK will only be generated once if it does not exist. This is the class where you work. In this class there are two methods that are interesting to you at this moment. Later you will learn about the rest.
DO_AT_BEGINNING: This method is called effectively in response to the <lib:tag> sequence. This is the code that executes before the body. This is the place where we would like to render out "<a href=...>" sequence.
DO_AT_END: This method is called effectively at the end of the tag, when the </lib:tag> is seen. The body has now already been processed and sent onto the output stream. So we only need to render "</a>".
Note that these methods are implemented empty. You *MUST* overwrite them, and implement them in your class. See instructions from Thomas. Source code:
METHOD if_bsp_element~do_at_beginning.
DATA: html TYPE string.
CONCATENATE `<a href="` me->href `">` INTO html.
me->print_string( html ).
rc = co_element_continue.
ENDMETHOD.
METHOD if_bsp_element~do_at_end.
me->print_string( `</a>` ).
rc = co_page_continue.
ENDMETHOD.
Notice that you DO NOT need that super call. The base method will always be empty (from definition, will never change). You also have a direct PRINT_STRING method in newer SPs. The return code you must set. (To tell the truth, the constants for RC have been picked so perfectly that if you forget them, it should not hurt in 85% of the cases.)
That is it. Test page. Mine worked!
Of course, we can start looking at more exotic things, like empty tags, at tags that skip their bodies if not required, processing the body, validation, etc.
But this overview was just to give you that first success feeling, and also to give you a better framework for understanding more of the documentation as you continue to read.
Recommended: read <a href="/people/brian.mckellar/blog/2004/06/11/bsp-trouble-shooting-getting-help">Getting Help</a> to see how you can quickly navigate between BSP page and a tag's definition, from where you also quickly get to the implementation class of the tag.
bye, brian
PS: Now if this is not already the first page of your weblog done

Java Components and Look and Feel

Can anyone suggest a free look and feel that does not resemble the standard stuff that comes with the JDK?
Also, Swing seems to be missing some important components like dockable windows, and toolbars. Can anyone suggest some resource that offers interesting swing components?

Can someone suggest a good API for doing this stuff?
I would really like to consider using Java for some
e real world application, but the swing interface
makes applications look at least 15 years old.Really? My applications look like native windows applications (when run under Windows, at least). Try setting the native look and feel. Search the forum if you don't know how.

WebDynpro look and Feel

Hi,
I created a webdynpro application and deployed into portals. We are running Portals SP11. But the webdynpro is not getting custom look and feel what has been added to the portal by default, it is displaying SAP Color theme.
Any ideas please?
Thanks
Vijay

Hi
Are your J2EE instances different for WAS and EP. If they are then what is the version of your WAS. You have mentioned EP as SP11.
Note : In SP11 the below mentioned procedure slightly affects the theme. It works fine in SP10 though. See if the steps mentioned below is of any help to you.
If you want the color schemes to apply for WebDynpro then you will have to set the theme for the WebDynpro application too.
Download the Theme Editor available in SDN.
Follow these steps
Create a new theme editor project with the same name as the theme name in the portal.
Import your theme file into WebDynpro.
You will have to generate your custom theme and then right click and export your theme as a zip file.
Then extract the Zip file to a folder.Copy the extracted files into the folder
C:\usr\sap\J2E\JC00\j2ee\cluster\server0\temp\webdynpro\web\sap.com\tcwddispwda\global\SSR\themes
Then give the path in your Visual Admin --> Configuration Adapter --> WebDynpro >tcwddispwda> default.properties
Type the path as the following.
http://<machine_Name>:50000/webdynpro/resources/sap.com/tcwddispwda/global/SSR/themes/sap_chrome
and also set the property useWebDynproStyleSheet property to true and then restart your J2EE server.
Hope that helps you. Let me know if you require more inputs
regards
ravi

Setting defaut look and feel under Gnome generates errors.

Similar Messages

Maybe you are looking for