when we have these two boxes (one highlighted and second not) (highlighted cuts a hole into not highlited)
so after doing csg on top face of that not highlighted box we end with a hole, then we do another csg but somehow reversed:
we perform csg with (original not cutted not highlighted) box on that highlighted one with the thing i call (inverse subtract) becasue we leave only things that is inside that non highlited one (then we also want to change face normals of that (not all)
anyway thats what it should do i dont knwo if its csg or my own implekemntation of cutting things.
my prevorious post can be matched to this conclusion: why to write all components on the form with winapi when you can use compoents from borland that you place them eaisly on a from, and don't care about api crap. mostly true but still you have the ability to change the code managed by borland
mine uses string class and bitmap/jpeg loading provided by Borland. rest is reinvented wheel.
My personal thought is that unity is for children like when you buy a child 'little/small chemist kit' does that mean hes a proffesional explosive maker ?
lets wait till 2040 when all you gonna do ist to connect blocks like in lego and 'the game will be made', thus he will call himself a programmer.
And another thought: when lot of crap is not made by the developer (i think mainly because they are too lazy and lack of knowledge) the final product seems 'shallow', unfinished, just crappy. I had truly awful pleasure playing few games made in unity and all i can say that when i see "Powered by unity" i will throw my phone out of the window in the same time shooting it with a nuclear bomb'
So to clarify everything i was using std::vector to load binary file and it was slow thats because i dont want to load it.
Topic is about loading text files and everybody was asking why i dont want to use std::vector then i got -rep for that i was replying why not, and magically everyone now thinks i am trying to load 3d model text/binary file, which is not true.
Scan it for newline characters, converting each into a null terminator as you find it.
as far as i remember that was something like std::string mystring;
mystring[ \n index ] = NULL; right? i remember that worked for symbian c++ however gave me sometimes non null terminated strings anyway \n consist of two chars so do i have to NULL both or i dont know null first and do not copy the char after it to the main output?