Documentation problems
Re: Documentatation problems
MUIRoyale 1.7 guide.
Area.FixHeight and Area.FixWidth says the value is number, but it seems to be boolean.
Area.FixHeight and Area.FixWidth says the value is number, but it seems to be boolean.
- airsoftsoftwair
- Posts: 5635
- Joined: Fri Feb 12, 2010 2:33 pm
- Location: Germany
- Contact:
Re: Documentatation problems
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
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"/>
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"/>
- airsoftsoftwair
- Posts: 5635
- Joined: Fri Feb 12, 2010 2:33 pm
- Location: Germany
- Contact:
Re: Documentatation problems
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
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")
xml closing tag is: </window>
instead of: </dialog>
calling function is: mui.DoMethod("dlg", "showmodal")
instead of: moai.DoMethod("dlg", "showmodal")
- airsoftsoftwair
- Posts: 5635
- Joined: Fri Feb 12, 2010 2:33 pm
- Location: Germany
- Contact:
Re: Documentatation problems
Oops, fixed
Re: Documentatation problems
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()".
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()".
Currently using: Hollywood 9 with Windows IDE and Hollywood 9 with Visual Studio Code and hw4vsc
- airsoftsoftwair
- Posts: 5635
- Joined: Fri Feb 12, 2010 2:33 pm
- Location: Germany
- Contact:
Re: Documentatation problems
Right, added that.
Re: Documentatation problems
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)
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)
Currently using: Hollywood 9 with Windows IDE and Hollywood 9 with Visual Studio Code and hw4vsc
- airsoftsoftwair
- Posts: 5635
- Joined: Fri Feb 12, 2010 2:33 pm
- Location: Germany
- Contact:
Re: Documentatation problems
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().