BTW: I'm using JDK 1.6u2 with NetBeans 6.0. The absolute layout
address is:
new org.netbeans.lib.awtextra.AbsoluteLayout()
Thanks for your help.
Why? *
> ..in Java.
Using absolute layouts is a bad idea in an X-plat,
X-plaf, multi-VM language.
>..I want to set the z-index of my
>component after adding them.
* What is this GUI that requires absolutely positioned,
overlapping components? Some types of GUIs might be
better suited to a CardLayout that shows any one GUI
element (usually a panel with many other panels and
widgets inside it) a JTabbedPane or a JDesktopPane.
>..How can I do so?
Why do you want to do so?
>2-How can I get the X and Y of an added component in absolut layout?
One way would be to remember where you absolutely
placed it in the first place (I would guess). But also,
you might try these methods listed in the JavaDocs
java.awt.Component.getLocation(java.awt.Point)
(as well as getX(), and getY() ).
--
Andrew Thompson
http://www.physci.org/
Message posted via http://www.javakb.com
Because no other layout can do my work. I want to design a board game:
put the places as JButton and the player as another JButton and put it
on the places. But the arrangement of places is very specific! (Take a
look at http://en.wikipedia.org/wiki/Monopoly_(game))
As I said, the component doesn't know its X and Y (So we can't use
getX and getY)
Please learn how to post in-line with trimming.
..
(Why AbsoluteLayout?)
>Because no other layout can do my work.
Rot. Whatever cannot be done in any single layout is
pretty simple to achieve with nested layouts.
>..I want to design a board game:
>put the places as JButton ..
JButtons do not make sense for the game place squares
themselves, though perhaps as a D'n'D (Drag'n'Drop, as
opposed to Dungeons and Dragons) DropTarget - probably
implemented on a (custom) BoardPlacePanel that has a
custom background, and is itself contained in a larger
layout.*
>..and the player as another JButton and put it
>on the places. But the arrangement of places is very specific!
*All* Java Layouts are very specific, and are also
very adaptive to the size and shape of the underlying
components. Lock down the size of the underlying
components, and the overall layout and size can
also be locked.
>..(Take a
>look at http://en.wikipedia.org/wiki/Monopoly_(game))
Monopoly, ..yes I'm familiar with it. Please enclose
URLs in <>, to help prevent line wrap and incorrect parsing.
.look at <http://en.wikipedia.org/wiki/Monopoly_(game)>)
* Use a GridLayout for each of the four sides, around the
borders of a BorderLayout. Drop a GridBagLayout in the
CENTER for the game cards, dice etc. D'n'D should be
able to handle the rest.
You might be able to do the entire GUI in a GBL,
here is a Periodic Table implemented in a* GBL.
<http://physci.org/jnlp/PToE.jnlp>
* Though their are some other layouts, and HTML
formatting, thrown in for good measure.
>As I said, the component doesn't know its X and Y (So we can't use
>getX and getY)
I find that hard to believe. What results when you call ? ..
System.out.println( myGamePieceJButton.getX() );