[04 May 2010] CodeBench/CubicIDE

[nexus]

Note: This is an archived post that was originally sent to the Hollywood mailing list on Tue, 04 May 2010 20:15:05 +0200

I now tried for the first time CodeBench by just importing and compiling my hwbeamer project from CubicIDE and I have a weird problem:

It seems that the following line of code does not work in CodeBench, but in CubicIDE:

Code: Select all

Const #HEADCOLOR = $003388
TextOut(0,0,"[color=#HEADCOLOR]test[/color]")

The error message is then, that "constant cannot be found".

In Codebench, it only works, if I replace the constant in TextOut-Object with its definition. So the following code works also in Codebench. What's the problem here?

Code: Select all

Debugprint("color="..#HEADCOLOR)
TextOut(0,0,"[color=$003388]test[/color]")

Maybe the reason is that Codebench always compiles a binary and CubicIDE allows to start the script without compiling it?

When I'm more familiar with Codebench, I will give a report what I like and what I don't like. At the moment, there're some things which I more like in CubicIDE and hw4cubic addon, but there're also some things, which are pretty handy in Codebench.

regards, Tom

[Simon]

Note: This is an archived post that was originally sent to the Hollywood mailing list on Wed, 05 May 2010 10:10:08 +0100

It seems that the following line of code does not work in CodeBench, but in CubicIDE:

Code: Select all

Const #HEADCOLOR = $003388
TextOut(0,0,"[color=#HEADCOLOR]test[/color]")

The error message is then, that "constant cannot be found".

I can't imagine why this would be, CodeBench simply calls the Hollywood compiler with the script as an argument, so I fail to see how CodeBench can affect the compilation of the script.

Simon

[nexus]

Note: This is an archived post that was originally sent to the Hollywood mailing list on Sat, 08 May 2010 10:07:10 +0200

Andreas: Any Idea? Is this a bug with Hollywood 4.7? In a way that user defined constants can't be used with TextOut-Objects, when the project is compiled to some binary?

greetings, Tom

[airsoftsoftwair]

Note: This is an archived post that was originally sent to the Hollywood mailing list on Sat, 08 May 2010 11:50:12 +0200

Andreas: Any Idea? Is this a bug with Hollywood 4.7? In a way that user defined constants can't be used with TextOut-Objects, when the project is compiled to some binary?

No, here it's working fine. Try to grab the script that Codebench sends to Hollywood for compilation... there must be syntax error in it. Trying to compile the following script works fine here: (without Codebench)

Code: Select all

Const #HEADCOLOR = $003388
TextOut(0,0,"[color=#HEADCOLOR]test[/color]")
WaitLeftMouse
End

If it doesn't work with Codebench, then it must be a Codebench error

[PEB]

Note: This is an archived post that was originally sent to the Hollywood mailing list on Sat, 08 May 2010 14:59:31 -0000

Code: Select all

Const #HEADCOLOR = $003388
TextOut(0,0,"[color=#HEADCOLOR]test[/color]")
WaitLeftMouse
End

I just tried running that code in Hollywood (not CodeBench), and I get the following message: "General syntax error!". . . "(current line: 2 - In function: TextOut)"

So maybe the problem is in the OS4 version of Hollywood?

[airsoftsoftwair]

Note: This is an archived post that was originally sent to the Hollywood mailing list on Mon, 10 May 2010 11:10:02 +0200

I just tried running that code in Hollywood (not CodeBench), and I get the following message: "General syntax error!". . . "(current line: 2 - In function: TextOut)"

So maybe the problem is in the OS4 version of Hollywood?

It's mysterious... I just tried it on OS4 and I don't get any error. Anyone else having problems with this code?

[nexus]

Note: This is an archived post that was originally sent to the Hollywood mailing list on Mon, 31 May 2010 19:53:20 +0200

Hi Andreas,

This is definitively a bug in the Hollywood compiler, not in CodeBench. I haven't found much time recently for Hollywood but I had to compile my script for windows and I used also CubicIDE. It defenetly does not work to use self-defined constants in TextOut-Objects (at least for the [color=...]-Tag) *AND* if you compile the script to some platform.

I tried compiling Windows, AmigaOS3.1 and AmigaOS4.1-executables and it didn't work. After replacing the constant #HEADCOLOR in the hole project with its definition $003388, it worked for all platforms.

You can use self-defined constants only, if you use the Hollywood-player to start a script (i.g. hollywood myscript.hws) but as soon as you compile it, and try to run the compiled executable, it's does not work anymore.

regards, Tom

[TheMartian]

Note: This is an archived post that was originally sent to the Hollywood mailing list on Mon, 31 May 2010 18:51:28 -0000

Hi

I have to agree - there is a bug. I tested the little program provided in previous mails in the Windows 4.7 version. It will run if you click the Run button and run in 'on screen', but it fails as already described if you compile it and executes it as a separate program.

regards Jesper