Hollywood forums

MoveLayer() is your friend and a good workaround for the problem

Bugala wrote:So what is the use for that automatic ID receiving, if i cant really use it anywhere?

You can use it anywhere except with layers

No, but it shouldn't take that long...

Yup, it's a bug and it's still present in Hollywood 6.0. Fixed now. Thanks for the report.

Layers don't support this. They don't use the standard object allocator but are numbered from 1...N. Alternatively, they can also use names but they will still be numbered from 1..N. A layer's ID always reflects its position in the stack of layers, i.e. 1 is the bottom-most layer.

Yes, this is right. When using the automatic ID selector Hollywood will return an identifier that uses the special data type #LIGHTUSERDATA. This has the advantage that there can never be any conflict with numeric IDs.

This is because of some major changes in Hollywood 6.0's display handler. It needs to be fixed in MUI Royale, not in Hollywood. In the next update of MUI Royale this will work correctly again.

Ok, then it could be related to a recently discovered bug in SelectAlphaChannel(). Try to replace all calls to SelectAlphaChannel() with this function which works around the bug: Function p_FixedSelectAlphaChannel(id, type, frame) If IsNil(__tmpbrush) Then __tmpbrush = CreateBrush(Nil, 1, 1) ; calib...

I'm also interested in this topic (UTF8 Text). What does BOM mean in this context ? Most UTF8-capable text editors will write the BOM at the beginning of the text file to indicate that the text file uses UTF-8 encoding. This BOM consists of the following three bytes: $EF $BB $BF. In ISO8859-1 these...

Are you using SelectAlphaChannel() in your code?