Database / Plugin Manager ect.. not locking you out of the rest of the editor.

[Isaac The Red]

Description of the Feature:
Have the editor behave in a way that would allow you to keep multiple windows in the editor open, such as having the plugin editor and database both open while you are also able to edit your maps.

Why is this feature good?

• Access to information at a glance, while editing event's or mapping.
• Freely access plugins and plugin help while working in database. [opening plugin help through the context window while in the database helps, but while that help window is open you lose the ability to continue working on the project until you close the window.]
• Smoother workflow between functions of the editor.
• Quality of life/Time saving

Possible issues with this feature?
Only a few things I can think of that would be problematic~

• Only really useful for those with very large, or Multiple Monitor setups.
• Will need to handle windows differently which may be a fundamental issue in the editor.
• Might be a little sensory overload for some?

 

[SamJones]

Other possible issue: inexperienced users might experience a loss of oversight on which element they are currently working on with multiple event editor windows open

 

[Andar]

I think the main problem here is rather that you might forget which changes were already applied and which not.

Having to close one window after working there will require you to apply the changes to the project.

Having multiple windows open will allow you to switch between them without applying the last changes, and that means the user might forget to press apply before starting a testplay (and no, you can't autoapply for a lot of reasons).
That will probably result in a lot of support tickets "the editor forgets my changes" or other bug reports that aren't bugs at all.

 

[Sarah_yt]

I really like this idea.

In relation to the issue of the testplay, perhaps that button could be greyed out while editor windows are open? Or a warning comes up to say you have windows open and your changes would not have been applied.

 

[Fornoreason1000]

Voted Yes!!

But all I want is to be able to move(not particularly edit) the Editor Window or at least hide it while editing Move Routes.... my god its so infuriating trying to see more of the map and see where you player needs to do next only to have a big ugly modal window that can't be moved in the way. you have to go back (pressing Ok) then move the window...open up move route dialogue again to do a few more commands then repeat!.

After the first ten its bearable but after several hundred you want to write it out the Move Route in some script file instead!

 

[Lantiz]

I was just about to ask for this.
My biggest problem is to read a plugins' help section while configurating a map.

Example: Just like OP suggested...
I use a custom map generator that needs lots of meta tags and I can't remember all by heart, so with this feature I could leave the plugin window open while working on the map.

 

[SamJones]

Voted Yes!!

But all I want is to be able to move(not particularly edit) the Editor Window or at least hide it while editing Move Routes.... my god its so infuriating trying to see more of the map and see where you player needs to do next only to have a big ugly modal window that can't be moved in the way. you have to go back (pressing Ok) then move the window...open up move route dialogue again to do a few more commands then repeat!.

After the first ten its bearable but after several hundred you want to write it out the Move Route in some script file instead!

Maybe put a feature request in for a visual Move Route editor that allows the drawing of movement paths on an image of the map (after all, transfer event targets can already be placed visually) or shows direct feedback when you step through the movement list?

 

[Shade Aurion]

This would save me a lot of time and effort. Especially since i'm currently transcribing my VXA project