GZDoom Builder 2.3

[Reisal]

Hey MaxED, can you post changelogs with each new revision on the in-dev versions? I'm curious on what Feb 20th's changes are from February 19th's.

If you already do, where are they (besides browsing the SVN/GIT)?

[GooberMan]

Reporting back with numpad enter things. It mostly happens whenever I have a drop down box open, then type in a number manually. Pressing enter there will make the value not commit.

--

On another note. I just had a catastrophic GZDB fail - alternting between 600MB used and six times that amount, causing my system to crawl. Had to end process to get my computer back to being usable. Lost half an hour of work as a result. Which then made me wonder - where's the autosave feature? Save to a temporary file every <x> seconds. Keep a track of which file it is in the .dbs data. And on load, if the last time the file was saved is before the autosave ask the user if they wish to recover.

I don't know how often things like this are needed, but it would certainly save me a bit of time if it existed.

[Gez]

This might help you:

http://www.doomworld.com/vb/doom-editin ... work-back/

[GooberMan]

Bah. Yeah, I should have realised considering it uses temp files whenever you test the map. Already redid my work though.

Alright, so how about rolling that in to a GUI driven feature?

[MaxED]

Hey MaxED, can you post changelogs with each new revision on the in-dev versions?

SourceForge has a nice Code Log feature. There's even a link to that in the first post and at the GZDB page at DRD Team...

[MaxED]

About autosaving: me from the times long gone will explain everything

[TammySilverwolf]

Just dropping in to say that GZDoom Builder has been a -real- easy program to get into and it's been very intuitive. Thanks so much for the time you put into it, this is so awesome.

[VGA]

About autosaving: me from the times long gone will explain everything

On the opposite side of the spectrum, could you please add a little advanced option to disable .bak file auto-backups?

http://forum.zdoom.org/viewtopic.php?f= ... start=7245

[MaxED]

Sorry, but I'm with Gez and edward850 on this one. Suffer me.

[NeuralStunner]

I literally do not understand how anyone can work/play for hours without saving progress that they do want to keep. (Then of course be angry at the program/game when it crashes and takes those hours with it.) Is it really that difficult to save your progress once in a while? The solution to the problem is a few keypresses away, at all times.

Re: Autosave clutter. The only time this bothers me is if the project is in a stable state and I won't be doing anything else with it for a while. It's not a big deal to manually remove the files at these times just to clear up space.

[GooberMan]

It's really a conceptual problem, and it's double felt when there is creativity involved. If I get out a pen and paper, I can work for hours and I won't lose anything. Computer program's haven't gotten the hang of that yet for the most part - Google Docs is one major example where you don't have to think to have your changes saved.

You can be as clever as you like, but everyone gets in to a rhythm at times and doesn't let other things interfere.

[SyntherAugustus]

Some feature ideas.

Second screen:
Can the side and bottom panel be separated into a different window so I can put them on a different screen?
Is it possible to make 3d Visual mode be in a separate screen so that both it and the normal view can be seen at the same time?

Toggles/Filters:
Is it possible to toggle seeing the grid? Also toggle whether or not to see the 64 lines?
Is it possible to have a view filter where you can only see things of certain classes. (Example, if I only want to see the things filtered for Easy only).

[MaxED]

Can the side and bottom panel be separated into a different window so I can put them on a different screen?

No

Is it possible to make 3d Visual mode be in a separate screen so that both it and the normal view can be seen at the same time?

No

Is it possible to toggle seeing the grid? Also toggle whether or not to see the 64 lines?

No

Is it possible to have a view filter where you can only see things of certain classes. (Example, if I only want to see the things filtered for Easy only).

Yes . Use thing filters.

[SyntherAugustus]

Oh, the feature does exist! I didn't see it at first but now I do.

[Xtyfe]

I just updated from my very ancient GZDB version to the latest SVN and it crashes when try to enter 3d mode now.

Here is the crash report

---

Could not bind BaseVisualMode.RotateThingsCW to action "buildermodes_rotatethingscw", that action does not exist! Refer to, or edit Actions.cfg for all available application actions.
at CodeImp.DoomBuilder.Actions.ActionManager.BindMethods(Object obj, Type type)
at CodeImp.DoomBuilder.Editing.EditMode.OnEngage()
at CodeImp.DoomBuilder.VisualModes.VisualMode.OnEngage()
at CodeImp.DoomBuilder.GZDoomEditing.BaseVisualMode.OnEngage()
at CodeImp.DoomBuilder.Editing.EditingManager.ChangeMode(EditMode nextmode)
at CodeImp.DoomBuilder.Editing.EditModeInfo.UserSwitchToMode()
at CodeImp.DoomBuilder.Actions.Action.Begin()
at CodeImp.DoomBuilder.Actions.ActionManager.InvokeAction(String actionname)
at CodeImp.DoomBuilder.Windows.MainForm.EditModeButtonHandler(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)