Page 2 of 4

Re: Documentatation problems

Posted: Mon Jul 30, 2018 3:04 pm
by lazi
MUIRoyale 1.7 guide.

Area.FixHeight and Area.FixWidth says the value is number, but it seems to be boolean.

Re: Documentatation problems

Posted: Tue Jul 31, 2018 10:58 pm
by airsoftsoftwair
Well, in RapaGUI they are booleans but in MUI Royale they are numbers because that is what they are in MUI so I don't see any documentation mistake here. It's just a different implementation between MUI Royale and RapaGUI :)

Re: Documentatation problems

Posted: Sat Aug 04, 2018 10:30 pm
by lazi
Ahh, yes you are right. I wanted to fix a Hollywood class by MUI, but @DISPLAY {height=320, width=320, hidden=True} do the job.

Anyway it seems that it has no effect on the Hollywood class.
The following made no change on the class size. It displays the full display size.
<hollywood id="sselector" display="1" fixwidth="200" fixheight="200"/>

Re: Documentatation problems

Posted: Mon Aug 06, 2018 10:54 pm
by airsoftsoftwair
Yes, Hollywood class doesn't really respect FixWidth and FixHeight. It's a known issue but not too high on the priority list because normally you just want to have the display determine the dimensions of the class object anyway.

Re: Documentatation problems

Posted: Tue Sep 04, 2018 11:26 am
by Lerio69
There are this errors in RapaGui moai.CreateDialog Example:

xml closing tag is: </window>
instead of: </dialog>

calling function is: mui.DoMethod("dlg", "showmodal")
instead of: moai.DoMethod("dlg", "showmodal")
;)

Re: Documentatation problems

Posted: Wed Sep 05, 2018 10:22 pm
by airsoftsoftwair
Oops, fixed :)

Re: Documentatation problems

Posted: Tue Nov 06, 2018 10:40 pm
by Clyde
No error, just an addition for quicker referene:

In "8.6 Nil":

You should mention that since Hollywood 6.0 it is possible (and probably the preferable way) to use the function "isNil()".

Re: Documentatation problems

Posted: Wed Nov 07, 2018 5:45 pm
by airsoftsoftwair
Right, added that.

Re: Documentatation problems

Posted: Wed Nov 07, 2018 9:56 pm
by Clyde
Thanks!

Again, no error, but for quicker reference:

Documentation of "DisplayTextObjectFX" should mention its return value better (even if it is just when async is true). So "Synopsis" should be something like "[handle] = DisplayTextObjectFX(id, x, y[, table])".

And add new "Results" section (handle - optional: returns a handle to an asynchronous draw object when "Async" is True)

Re: Documentatation problems

Posted: Sun Nov 11, 2018 12:07 pm
by airsoftsoftwair
Right, this information actually had to be added for the following commands as well: PlayAnim(), DisplayBGPicPartFX(), DisplayBrushFX(), DisplayTransitionFX(), ClearScreen(), MoveBrush(), ShowLayerFX(), HideLayerFX(), RemoveLayerFX(), Undo(), UndoFX().