[Bobboau]

I updated my code right after that build I posted, I've been sort of busy with stuff, I hope to know exactly what I want to do by the time I get to work on this again, (I should have time tomorrow). Ill commit when I have something that can be used (when I get the tree's basic functionality done, which should not be too huge a task). this is why I asked for discusion on how exactly everyone wanted the tree to work. and I'm thinking as of right now that selecting an item in the tree will mearly load it's chunk editor and bring the item to focus, which is also a lot easier to code than the other method.

[Kazan]

I'm thinking as of right now that selecting an item in the tree will mearly load it's chunk editor and bring the item to focus, which is also a lot easier to code than the other method.

that's what i had in mind when i originally coded the tree

[Nuke]

it woulf be cool if you could follow every branch down to the individual data types, which could then me edited by clicking on them in the tree.

[Bobboau]

yeah, and the way I have it coded it wouldn't be obsenely hard to do, but the more I think about it the more I realse that as cool as that might be I don't think it would be very useful, how oftine do you need to edit just the radius of a thruster, usualy it's best to have all the information at hand. I think makeing it so that selecting a data element places the curser into the relivent control will have the same effect without hideing useful information from you, and the most important thing about the tree will be the drag and drop ability to move nodes around at will, and copy data of the same type.

[Nuke]

that seems like it might work. editing data directly in the tree may prove more difficult than just punching the data into the right box.

[Vasudan Admiral]

About the chunk editor, would a MS word style table format be possible?

Almost like how modview does it:


Except that you could edit values directly into the table there and use the arrow keys or tab to move between cells. Something like that strikes me as the fastest way to edit most pof data, since you could do it pretty much entirely with the keyboard.

[Bobboau]

new build
basic tree functionality is implemented, I will probably be committing soon if no major bugs are found.

next item on the list for the tree is drag and drop functionality, but I might work on integrating the 3d display a bit more first.

[Topgun]

is there any way we can tell the exact size of a model?

[Bobboau]

well in the header editor it will give you the max radius and bounding box for the model.

[Topgun]

the reason I am asking is because I am making a tie fighter for swtc fate of the galaxy and I want it to be perfectly scaled to cannon size.

[Bobboau]

bounding box will probably be more useful to you then.

[Bobboau]

while you all bug hunt, I'm going to wite the omnipoint code, it won't stop me from commiting because it won't be used untill after I commit. this will be the main method by which things will be edited in the 3d controls. it's basicly a 2d vector of points with a radius and normal that the editor makes and gives to the GL canvas, the GL canvas makes changes to it and sends it back to the editor, which applys these changes to it's copy of the data. flags tell the GL canvas how the data is to be used and displayed (if the normal and radius are to be used for instance). and three colors are provided for unselected items, items that are in the selected list and the selected item.

this is mostly a heads up for kazan, so he has some idea how I'm planning on going along with this sence he's probly going to have to write the low level code for this.

[Kazan]

that makes no sense - data should never be written to the GL canvas.. the GL canvas is not in any way part of the data storage - it's just displaying - consider all actions in relation to it const - i'm not sure what you're trying to describe or do there

any flags/bits of data you need to store for it should be stored as runtime-only variables inside the PCS file class, just like the variables that are already there.

[Vasudan Admiral]

I'm getting a crashes during load on a lot of models with this build that didn't happen before. A lot still work, but a lot will lock it up.

Some examples of retail models that freeze it:
- awacs2t-01
- BeamSaber
- bomber2t-01
- bomber2t-03
- bomber2v-02
- bomber04 up to bomber10

to name a few.

Also, clicking on the turrets item in the tree on a model that doesn't have any causes an instant CTD.

The tree itself looks great so far though.

[Scooby_Doo]

I just noticed something, maybe you already know it.  When load a model, it'll view very nicely, but if you maximize the window, it disappears.

[Bobboau]

@VA: I still have a bit of buffer protection to implement, it's probly trying to read or write to something that doesn't exsist, which will crash it like that. if it crashes after the progress bar on the bottom fills all the way, then it's probly my fault.

@SD: the renderer doesn't seem to handle changeing aspect ratio's properly, try moveing the editor or tree panes to make the render window bigger (or smaller), that might help for the moment.

[Vasudan Admiral]

As far as I can tell, it's crashing before the loading bar fills. It's a bit tricky to tell though, since it's so fast at loading.

The "Loading Model" text down the bottom right appears, and it hangs there for a second or so with no apparent movement on the bar before the menu bar and tree view white out. After that point it just stays that way - there's no eror message of any kind.

[Bobboau]

actualy looking at it, it seems to be crashing in SignalModelChange before hitting any of my code, around the multi-threaded stuff, so that's probly not my bug, see if the most recent build Kaz released does it.

[Vasudan Admiral]

Oh....
Yeah it does happen in Kaz' latest build.

I guess I just didn't notice when testing that version, though I wonder how I could have missed something like that. :\

[Scooby_Doo]

I see the problem...

Load a model, it'll appear in the view,
now resize the toolbar (either one) and it'll get messed up. (the model gets distorted)

It looks like your trying to maintain the aspect ratio, when you should be maintaining model size.