within the main display loop you can simply change the projection to orthographic. A tidy way is to input a class that has the code neccessary code to generate the 2D projection matrix and neccessary screen co-ordinates. you can then write the commands to draw the objects in this class. In the main loop you then just call this function (it should only take a few lines in the main display keeping it tidy).
The projection can swap from a 2D to 3D projection mode without any noticable artifacts or problems. This works well for interfaces, buttons, heads up displays etc.
you dont lose your 3D by changing projection type just make sure you do it before the frame switchs (it just goes next to your 3D code). You can also just texture or draw flat in 3D as other people have said. I personally just prefer to change to 2D to help keep everything seperate and prevent errors or problems when drawing multiple 3D objects and avoiding potential issues such as hidden surface removal. Realistically i don't think these problems arise much so just so which one you feel most comfortable with to start with and once happy try the other method.
Hi, as I was told that my code doesn’t scale well at all, I thought perhaps I’d try to get a better understanding of interfaces/abstract classes and classes and the relationship between them.
I don’t want at this stage work on a big separate project as I've already got plenty ...
I am writing a java program that needs to execute shell commands, so I wrote a function that would take the command to execute as a string (ie: "mkdir ~/Folder1") and execute that command with the shell. Here is the function:
Runtime run = Runtime.getRuntime();
Process pr = ...
Hi. I have a form with list box : lst_product, datagridview : grd_order and button: btn_addline. lst_product has a list of product ids selected from database (MS Acess 2013) , grd_order is by default empty except for 2 headers and btn_addline adds rows to grd_order.