It seems like you are trying to use a Java library for 3D programming. If that is the case, then there would most definitely be a class called FastMath in a package called math somewhere. You can use the FastMath.round(...) method within that class to convert the float values to an int without much overhead. This will enable you to then pass those values to the Vector3D class. Hope this helps. I would have been of further help if I only knew what libraries you were using.

The beginning of knowledge is the fear of God

You would need to look into the java.awt.Robot class to capture the screen. Just search for this class and you will get several tutorials explaining how to use it. But remember, this class just captures images of your desktop. You would then have to send those images over the network to other computers using an implementation of either Datagram (UDP-based) or TCP-based Sockets or RMI. Plus, also look into Serialization. These are the only pointers I can give you. People do not write tutorials about such stuff. I hope this helps you find a suitable direction to move forward in.

The beginning of knowledge is the fear of God

As far as I know, you are only allowed to kill a process directly from within Java if it was started from the currently running Java code. However, if a certain process was not started from within your Java code, you would need to use a native third-party tool to do the job for you. Thankfully, if you have Windows OS versions greater than Server 2003 or Vista, you can use the TASKKILL.EXE command-line application present in the ~\WINDIR\system32 folder to kill a certain task. Or perhaps, you can use the following code to do this explicitly from within your Java code:

Runtime runtime = Runtime.getRuntime();
String[] killArgs = {"TASKKILL", "/IM", "WINWORD.EXE"};
try
{
Process processToKill = runtime.exec(killArgs);
processToKill.waitFor();
System.out.println(
new StringBuffer()
.append("Process exit code: ")
.append(processToKill.exitValue())
.toString());
System.exit(0);
}
catch(java.io.IOException ex)
{
ex.printStackTrace();
System.exit(1);
}
catch(InterruptedException ex)
{
ex.printStackTrace();
System.exit(1);
}

Tell me if this works for you. I certainly hope this is what you were looking for.

The beginning of knowledge is the fear of God

Firefox isn't my browser either but development in the Open Source world is damn slow. Nevertheless, I am still reluctant to go back to Microsoft Internet Explorer especially after I came to know that there's a vulnerability in the browser that lets scammers to launch a phishing attack on your PC. Some even include a fake SSL signature padlock certificate to fool you and that too over the updated version of Windows, Service Pack 2.:wtf: Read it yourself. And, I thought Service Pack 2 was the most secure thing there is on this planet! We always are wrong about certain things that happen around us. The Open Source community around Firefox might have been dragging their development speeds, but who knows what might happen next? I still won't go back to Internet Explorer even if version 7.0 ends up with tabbed browsing and a promise of 50% more secure browsing.

The beginning of knowledge is the fear of God

Mike Connor's speculations made quite a stir in the Open Source Community a few days back but all is not dead for Open Source. Firefox did in a few months what SeaMonkey (Mozilla Application Suite) could not do in years. Just yesterday the Mozilla Foundation declared it official that the SeaMonkey (Mozilla Application Suite) 1.7 is the last version up the Development tree. They are literally abandoning SeaMonkey. Read more about the slow death of Mozilla. Asa Dotzler, in reply to concerns cleared the issue saying [Read more here]:

We're focused on shipping our premier applications, Firefox and Thunderbird, and any efforts we're spending on Seamonkey right now are devoted to maintaining the 1.7 branch with security and stability updates. Seamonkey is a fine testbed for Gecko improvements that will be a part of any application releases that come from the 1.8 branch.

So what is the Mozilla foundation left to deal with? What else! They have their finest products up in the Development tree. In fact Mozilla Firefox 1.1 is due June 01, 2005. Don't lose your trust in Open Source now. Who knows what you might see coming your way when the goods of Mozilla gets mixed with the better of Firefox. I certainly have not given up hope there... yet.

The beginning of knowledge is the fear of God

The coordinate system As we all know, drawing systems in .Net are based upon pixels that are arranged on a two-dimensional coordinate system. The origin, that is, the points (0, 0) lie on the far top-left of the screen. Each consecutive pixel towards the right of the origin forms the x-axis, and each consecutive pixels towards the bottom of the screen forms the y-axis. If you note carefully, the co-ordinate system for onscreen graphics is an inverted copy of the Cartesian Co-ordinate System used in Mathematical Geometry. Now, when we give the call to the system to draw a rectangle, we provide it with four arguments. The x-coordinate, the y-coordinate, width and the height of the rectangle. We will traverse through each step that the system undergoes to create a rectangle. Step 1: First, the point (x, y) or the pixel present on the point (x, y) is plotted or marked on the coordinate system as shown below. Step 2: Then, it adds the width provided as argument to the next consecutive x-coordinate. For instance, if the x-coordinate is 0 and the width is 10, then the resultant point on the x-axis (fx) will be:

Because x-coordinate specified was 0,
So the next x-coordinate will be 1

Final Point = next x-coordinate + width
Final Point = 1 + 10
Final Point = 11;

Same goes for the y-coordinate and the height to calculate the resultant point on the y-axis (fy). Step 3: System marks all the pixels from (0, 0) to the point (fx, 0) on the x-axis and also marks all the pixels from (0, 0) to (0, fy). This gives two straight lines joined at (0, 0) at an angle of 90 degrees. The points (fx, 0) and (0, fy) are then interconnected at the point (fx, fy). Thus giving the illusion of a perfect rectangle. What happens with GDI+ drawing routines If you keep the x-coordinate and the y-coordinate as (0, 0), then it is seen that: Resultant Point fx = width + 1 and Resultant Point fy = height + 1 So, if we specify the below mentioned statements in GDI+:

g.DrawRectangle(new SolidBrush(Color.Blue), 0, 0, this.Width, this.Height);
g.DrawRectangle(new SolidBrush(Color.Blue),
new Rectangle(0, 0, this.Width, this.Height));

From these statements, it is clear that the resultant point to which the rectangle will be stretched is (this.Width+1, this.Height+1) which unfortunately exceeds the visible region of the Component or Custom Control. Did not understand a single word? Ask for a detailed and illustrated