[Bobboau]

yeah, the tree is my thing, if it ever gets done it'll be via an allternate gui that I write.

[WMCoolmon]

Originally posted by Kazan
WMCoolmon: have you ever written a tree ctrl?  

PS the data isn't stored in the GUI - i _NEVER_ use GUIs for data storage, GUIs are presentation only

Yes, in fact I used the one I wrote as a model for what I said. While GUIs might not be used for data storage, you can in fact do what I said; you could also make the data portions of the tree items point to a struct containing an int with the type of data, and a union with pointers to the data itself(Assuming you didn't derive anything). That would be more complex though as you'd have to allocate and deallocate the memory for those additional structs.

And while you may have vetoed it, it just seems flat out a better way to do it from the usability side of things, and worth the extra coding time.

[Nuke]

i really dont care how the data is displayed, i just want to be able to move like data types with a simple dragdrop event. but overall i think i like the tree style interface over a tab style. tab style you can only really look at one chunk at any given time. with the tree you could look at multiple objects from multiple models without the trouble of switching between tabs.

[Bobboau]

erm sort of, you'd be able to move to a specific item a lot faster but you'd still only have one item at a time, and your scope would be a lot narrower than with the traditional tab interface (ie you'd only be able to do one thruster point not the whole thruster, this might get a bit confuseing in data types that have a lot of data in both the child items and the perent items like paths, but it would also save a lot more on space)

[Nuke]

will it have full autogen support?

[Bobboau]

yes regardless of the overall interface it will have auto-gen and all the snazzy things I made for aurora.

[Kazan]

Originally posted by Bobboau
(ie you'd only be able to do one thruster point not the whole thruster,  

and what exactly is forcing it to be that way?

nothing


-------------

i was just thinking about it and im going to reverse the idea.veto() on the tree ctrl

it would make things a lot easier when it comes to copy+paste

[Nuke]

i use autogen on everything it can be used on, just wich you could autogen everything.

[Bobboau]

yay!

[Bobboau]

there's nothing forceing it to be that way it's just the way I was planning on it workingyou don't realy need access to the parent data while you are editing the children, becase it's just a quick click to get access to the parrent data. I supose it's more of a matter of taste, I think it would be a bit cleaner if it only displayed the data of the element you were editing, not the parent data

[Taristin]

Bob! Study how to get glow and shine mapping in OGL! Damnit!

[Kazan]

bobboau: they way you stated it implied inability to select the entire object

[Bobboau]

well I was corecting a misconception that you'd be selecting multable objects at the same time.

[ShadowWolf_IH]

just wondering how this was coming along.  I am very interested in it.  Thanks guys for this, we do apreciate your eforts.  Mostly because your efforts rock

[Bobboau]

hey, I just thought of something, why don't you make this use the FEs graphics class, it'd give me a reason to work on it again, and kill two birds.

[Nuke]

death to birds!

*hands bob one of his miniguns*

[Kazan]

we could do that - but i'd have to merge PCS2 into the ferrium codebase


not like i wasn't planning on putting support into PCS2 for ferrium models anyway

[Bobboau]

/*gets nukes gun*/

dude it's like a gatling gun... of gatling guns WTF!
them fuk'c birds are dead

[FireCrack]

Wait, what about a gattling gun of gattling guns of gattling guns....


Nuke, you never happened to see the unreal gattling gun did you? it was two 3 barreled gatling guns positioned so that they interlocked as they turned, awesome-cool.

[Bobboau]

eh, actualy I made that, it's a joke Nuke has a bit of a mini-gun fedish.