g3d viewer request: refresh button

[John.d.h]

When working on a model or animation, sometimes I like to have it open in Blender to modify it and a copy open in the g3d viewer so I can see how it actually looks in game.  I think it would be easier to focus on minor changes and updates to the file if there were a way to "refresh" the model in the viewer so it reloads the model, texture, etc., but keeps the same view.

[titi]

ctrl-r

[claymore]

A button would be nice too though.

[John.d.h]

ctrl-r

Oh, cool.  Never mind then.

A button would be nice too though.

True.  I didn't see a menu item or anything, so I didn't know it existed.

[titi]

yes thats true, even a hint that its ctrl-r to reload would be nice. Will think about it.

ctrl-r does:
- load projectile particle again ( and play it back again !)
- load unit particles again if changed
- load model again if changed

[Omega]

Wow, that WAS handy... I've been needing such a feature for a long time, and had no clue it was there...

Relatedly, the G3D viewer and the Map editor should have a help file (and I mean a little more than the three lines that the map editor has...  ) that can be opened from the menu bar.

[softcoder]

Problem with help fiels is there is no cross platform framework that I know of easy to use. Perhaps we could just launch a text file with help info?

[Omega]

Problem with help fiels is there is no cross platform framework that I know of easy to use. Perhaps we could just launch a text file with help info?

Yeah, that's probably the simplest method. I don't see much for cross platform help. Most windows programs like to use CHM, but to my knowledge, that's not so standard in Linux. Some programs (such as the GIMP and Open Office) have their own help browsers, but that may be unnecessarily complex.

Instead of a txt file, why not an HTML file? After all, they are cross platform compatible, and are able to show a lot more a lot better than a simple txt file, and makes it possible to expand in the future, with multiple pages.

[softcoder]

Yes, then the help could also go on the wiki. HTML it is

[Omega]

Well, just to point out that making the help file HTML wouldn't necessarily mean you can backtrack it to the wiki too. For example, in the wiki, it's best to use ==My Header==, but HTML would have to use <h2>My Header</h2>.

I volunteer to create you a help file though.

[softcoder]

Excellent, thanks. It will be good to get more information out there and make it easier for everyone to work with Glest.

[tomreyn]

Did you ever get around to create this help file Omega? It might be good to generate it in a generic format which can later be easily updates and exported to multiple other formats. HTML isn't ideal for this but may be good enough.

[Omega]

No, I never got any confirmation it would be used, so abandoned the idea. If I could hear at least a hint that it could be used, I'll happily make one (probably in plain text, for compatibility).

[tomreyn]

So what softcoder said did not provide enough indication that it would be used? It does to me. If I will ever start modelling I'd appreciate it if there was a help file, too.

[Omega]

Fair enough, I can make one, but first of all, how will it be viewed? Will it just be a very large dialogue box (in which case I am more limited in how much text can fit) or will it be able to directly open a txt file?