NEW Powerfull Message Box

Description of the Feature:
Redesign Message Box, and Add basic feature from Rmmv

• 
  * Resize Face path preview and add picture selection.
  *ADD Custom face/picture position
  *ALLOW Elementary feature, the Hexa color code..... \c[#myHexacode]
  *Allow Select Engine Render [Bitmap, PIXI] .. (PIXI.Text allow a lot of power feature)
  *Allow Custom Background image
  *Allow Custom Message Box Position By value or by Variable
  *Set The message Speed Text
  *Allow change font for the message box.
  *Allow Move Event feature { No, After MSG, Yes }
  *Allow Move Player feature { No, After Message, Yes }
  * Select Fade Type for box {Default, Scale X, Scale Y, Opacity, ScaleXY, From Bottom, From top...... }
  * Show pixel rule to help text design + Button (scale text pixel in box) is best way to resize dynamic box
  *More large box text (because we most work on PC and not with a phone !!) (maybe see if we can have dynamic size ?
  * PIXI Editor if use the render, Default can be set in the core, or use specific proprety for the msg box
  * PREVIEW with basic code render (Color, player name , Size .... )
  *Word Check

Mockups:
note:I kept as much as possible the design from rmmv programmer software.
For easy to integrate changes.

It is a sketch, but ideally, here a message box much more operational.
And that uses features already included in the rmmv core
Full screen (right click and open in a new window)



Ideally, offer a memory assist button for the default codes and also somes custom codes make by the user.
The custom code could be added directly to the core. (Simply for memory aid)



Why is this feature good?
The message box are very cheap ... and not professional.



Possible issues with this feature?
Issues that might arise from this feature:
Keep the old version values for maximum compatibility.
Provide default choices without checkbox
--------------------------------------------------
EDIT:
ADD WORD CHECKING @mogwai , when mouse hover a bad word , show suggests correction ...
with Google API ? ..



note:
This is a very approximate example if you have a better idea or want to share another design.

The psd is here, and thanks to share your design.
https://mega.nz/#!dQ4ShTYb!U4940ciD65RhWexrwe3igLa_E2LeLnHlj0Cstpdcpns

 

Piggybacking spellchecking into the list, I agree with all of this wholeheartedly.

 

Piggybacking ?? lol sorry am not fully english
piggy = litle pig pink ?
backing = front money ..
Piggybacking = little pink pig need money ?

 

My suggestion is a spellcheck feature for the message editor too. It's basically climbing on the back of your thread, because this isn't my thread.

 

ho ok, i understand , ya +++++ for this

i add a feature to suggest , is a very good idea
Mouse hover incorrect word = suggest bubble;
same lie Microsoft word

 

Indeed, to avoid compatibility issues, keeping the old message box would be great too. Something you could change in the options. But, this would require a major overhaul of the editor, I am not sure this could be done.

And concerning the spellchecker, you can use other softwares for this. Implementing one new would be more of a pain. Hence, I'm voting No for this one (with no ill intent, only comparatively with the issues and work it would require).

 

Yes, would be so awesome!

 

You voted no on the base that it will give other people more work? That's odd logic. On that basis everything would be no.

 

@Soulnet : I voted on a the base that it would give too much work for a relatively low use. As of now, many plugins already deal with enhancements of the message box. Your suggestion would require too many changes of the UI and cause a lot of issues for existing projects.

 

My suggestion? I didn't put up the suggestion!

Again though, given it's not you who would have to do the work, let the Devs decide if it's too much work or too hard to implement! They might take 1% of the suggestion.

 

@Soulnet : Sorry about that, I assumed it was yours, I just woke up ^^'

 

Strongly agree.

I don't know if I am the only one but I usually do data entry late into the night. And sometimes its the next day before I notice I've punched in a TYPO and I need to fix it. A spell checker would be handy and the current system for the messages boxes is far from satisfactory for me. I feel they
are too small and having to check them constantly to see if there is overflow is a pain.

 

I like some of the suggestions for increasing the usability of the message box, but the overly custom features like changing the rendering program used are things that would be overwhelming to me.
So I think that some improvements would be nice (like changing font or changing message speed as built-in features) but I don't want to say yes to everything.

 

I understand, but know that the PIXI v4 engine is already integrated in rpgmaker.
This one being much more powerful, it would offer enormously of possibility.

And is work with the GPU&CPU, so mor performance in game.

The idea remains to keep the engine by default, or to switch with the pixi engine.
This will keep the compatibility of the games already Build, and will allow those who wish to pass their games with the engine Pixi.Text

 

Okay, so I'm not sure I understand the logic of this. If I look at your mockup, it looks like you have to set some positions EVERYTIME you make a message. For me, it would become a huge hassle (even if you use variables, you'd have to select those everytime). I think making one plugin to handle most of these things just once would be much better.

 

How did I miss this, this is something that could be extremely useful to both us and the Japanese market!

 

What? No text-align, aka text positioning? I see window position, but not text position. Would say yes if I saw that added. Other than that, looks great.

 

yes, it possible with pixi style with align left center right.

 

So, what happens when the player activates another event while the message box hasn't been dismissed yet?

 

hi friend.
You must understand the tread from. Editor Suggestions and Improvement
We here of proposing scenarios, ideas, inspiration to the developers, in order to direct them towards possible improvement ways for the software.

Source codes and problems will be evaluated by software developer, as stated above, the idea is to inspire and allow the customer to explain their need.

When you buy a product, it makes sense to propose improvements according to your needs, which will then be evaluated and applied as internally feasible by the softwares developers.

What is offered at the top is simply a sketch to inspire possible improvement.