Documentatation problems

Report any Hollywood bugs here
User avatar
lazi
Posts: 295
Joined: Fri Feb 25, 2011 12:08 am

Re: Documentatation problems

Post by lazi » Mon Jul 30, 2018 3:04 pm

MUIRoyale 1.7 guide.

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

User avatar
airsoftsoftwair
Posts: 2618
Joined: Fri Feb 12, 2010 3:33 pm
Location: Germany
Contact:

Re: Documentatation problems

Post by airsoftsoftwair » Tue Jul 31, 2018 10:58 pm

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 :)

User avatar
lazi
Posts: 295
Joined: Fri Feb 25, 2011 12:08 am

Re: Documentatation problems

Post by lazi » Sat Aug 04, 2018 10:30 pm

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"/>

User avatar
airsoftsoftwair
Posts: 2618
Joined: Fri Feb 12, 2010 3:33 pm
Location: Germany
Contact:

Re: Documentatation problems

Post by airsoftsoftwair » Mon Aug 06, 2018 10:54 pm

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.

User avatar
Lerio69
Posts: 13
Joined: Sat Sep 24, 2016 11:47 pm
Location: Italy

Re: Documentatation problems

Post by Lerio69 » Tue Sep 04, 2018 11:26 am

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")
;)

User avatar
airsoftsoftwair
Posts: 2618
Joined: Fri Feb 12, 2010 3:33 pm
Location: Germany
Contact:

Re: Documentatation problems

Post by airsoftsoftwair » Wed Sep 05, 2018 10:22 pm

Oops, fixed :)

User avatar
Clyde
Posts: 102
Joined: Sun Feb 14, 2010 1:38 pm
Location: Dresden / Germany

Re: Documentatation problems

Post by Clyde » Tue Nov 06, 2018 11:40 pm

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()".
Currently using: Hollywood 7.1 with Windows IDE

User avatar
airsoftsoftwair
Posts: 2618
Joined: Fri Feb 12, 2010 3:33 pm
Location: Germany
Contact:

Re: Documentatation problems

Post by airsoftsoftwair » Wed Nov 07, 2018 6:45 pm

Right, added that.

User avatar
Clyde
Posts: 102
Joined: Sun Feb 14, 2010 1:38 pm
Location: Dresden / Germany

Re: Documentatation problems

Post by Clyde » Wed Nov 07, 2018 10:56 pm

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)
Currently using: Hollywood 7.1 with Windows IDE

User avatar
airsoftsoftwair
Posts: 2618
Joined: Fri Feb 12, 2010 3:33 pm
Location: Germany
Contact:

Re: Documentatation problems

Post by airsoftsoftwair » Sun Nov 11, 2018 1:07 pm

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().

Post Reply