Crispy on 25/6/2005 at 04:22
I've been playing around with a handy Windows API program called Spy++ (it comes with Visual C++), and have determined that all of T3Ed is made up of standard Windows controls. It's therefore quite easy to modify the interface in any way we want. It may also be relatively easy to insert additional functionality, perhaps even without modifying t3ed.exe; I'm still looking into that.
Note that I'm not proposing to modify the .exe; at least not yet. There's a lot that can be done with the Windows API.
So is there anything that people would like changed about T3Ed? Don't restrict yourself to interface issues; wish away. Not all of your wishes may be possible, but that's fine; mention them anyway!
I have a few items on my wishlist already:
- Make the default button for Viktoria errors "Continue" instead of "Save".
- Make it possible to automatically "Continue" on user-selected Viktoria errors. My copy keeps complaining at me about a certain script "attempting to be added twice"; it'd be nice to be able to permanently ignore trivial errors like these instead of clicking "Continue" every time I open the script editor.
- Rename the "Send to Xbox" menu item with something more sensible, like "Play level with sound" or "Play level, no debug" or whatever.
- Stop the texture editor from appearing on startup all the time.
Jadon on 25/6/2005 at 04:35
A bigger viewport for the static meshbrowser.
Gestalt on 25/6/2005 at 04:37
Seconding that.
ascottk on 25/6/2005 at 04:40
I. Tab (or hide) the minimized windows like the actor, trigger script, etc. so I can easily access what those things are covering.
II. Get rid of the Obsolete stuff (find those "obsolete" things & find out if they actually are obsolete - the texture properties. I haven't totally explored which functions work & which do not).
III. More properties for the textures. If we can override the materials by right-clicking a texture then we really wouldn't need the *.mlb files.
IV. More comments in the actor browser or a reference to the wiki when it grows. T3Ed could have a database that can updatted from the wiki.
V. Right click functionality on the toolbars.
Jadon on 25/6/2005 at 05:01
which toolbars do you mean? the ones above each viewport? if so its there you just have to know where to click. the best bets are between the "realtime preview" button and "hide actors during pan button" or between the ion button and everything after that. or do you mean somthing else like a larger area or somthing?
ascottk on 25/6/2005 at 05:03
The very top toolbar. The New, Open, Save, etc. I like to customize my toolbars.
Jadon on 25/6/2005 at 07:06
ah so you want to be able to move it around like in word or photoshop.
Crispy on 25/6/2005 at 08:16
Resizing the static mesh viewport is probably possible. I'll have to play around with it to see if it updates intelligently when I do so, though.
Quote Posted by ascottk
I. Tab (or hide) the minimized windows like the actor, trigger script, etc. so I can easily access what those things are covering.
When you say tab, do you mean add them to the taskbar? Sounds like a good idea, and doing so is quite easy.
Quote:
II. Get rid of the Obsolete stuff (find those "obsolete" things & find out if they actually are obsolete - the texture properties. I haven't totally explored which functions work & which do not).
Aye. Before I can do it I need to know what to remove, obviously.
Quote:
III. More properties for the textures. If we can override the materials by right-clicking a texture then we really wouldn't need the *.mlb files.
Not quite sure exactly what you want here...
Quote:
IV. More comments in the actor browser or a reference to the wiki when it grows. T3Ed could have a database that can updatted from the wiki.
I like this idea a lot! Being able to set our own comments for each property (and links to more detailed explanations) would be excellent. No more hunting around for documentation.
In fact, the script editor could use this kind of thing too; descriptions and help added to each condition and action. There's already a rudimentary scripting reference on the wiki; making T3Ed pull info from it would encourage people to update it. :cool:
Quote:
V. Right click functionality on the toolbars.
Would be useful. Not trivial to do (i.e. it's not a 2-minute fix), but certainly possible.
I'd also like to modify the sidebar. Ideally it would be possible to drag each button group off, and make it (A) a separate window, or (B) on the right-hand side. There are just too many buttons to show at once otherwise.
Well, it looks like there's interest, so I'll start on this right away. Please do keep adding requests. :)
Ziemanskye on 25/6/2005 at 11:09
Unfortunately, what I really want is either flagged obsolete or entirely missing, but I miss my Turn to Static Mesh button!
Proper (object) selection without having to rebuild first. StaticMeshes that actually rightclick first attempt (I often have to deselect, reselect, re-rightclick to get the list up), and which always delete when I press the Delete key, rather than just when they feel like it (and no, rebuilding doesn't always help that one, for me at least)
Making the Remove Existing Particles button on the tools menu (I think) actually remove all of the particles from the level, Flesh and Unreal renderer, and without having to manually select the particle emitters first. Note I don't mean kill the emitters, but if you've had the realtime preview on to test them the collision areas for most of them get really annoying, even if you can't currently see the particles you end up clicking on them. Grrr.
Menu Buttons on the top (like the texture browser et al) for the Conversation and Schema (and maybe Skeleton) Browsers.
A one click maximise viewport button (I know UT2k4 has one, but here I'd actually use it since I make maps for printing/doodling all over from the top viewport)
And while someone mentioned the buttons on the left - the submenus can be rolled up anyway, and it's not like you need (well, to be more accurate, it's not like I use) most of them.
OrbWeaver on 25/6/2005 at 11:19
It is unlikely to be possible to change inner workings or add functionality to the editor just using a Resource Editor. Altering menus, buttons, viewport sizes etc is usually possible, but changing behaviour would require access to the source code.
