1 line program error?

Karbon · Post by **Karbon** » Thu Dec 13, 2007 10:11 am

messagerequester("Hi","Hello World")

End

i make the executable and run it and a terminal window opens, the message box is displayed but you can't click "OK" on it - have to CTRL+C the terminal to end the program.

What have I missed?

IceSoft · Post by **IceSoft** » Thu Dec 13, 2007 10:34 am

Karbon wrote:
messagerequester("Hi","Hello World")

End
i make the executable and run it and a terminal window opens, the message box is displayed but you can't click "OK" on it - have to CTRL+C the terminal to end the program.
What have I missed?

Works here as expected. Ok button can be pressed.

michel51 · Post by **michel51** » Thu Dec 13, 2007 10:37 am

Karbon wrote:
messagerequester("Hi","Hello World")

End
i make the executable and run it and a terminal window opens, the message box is displayed but you can't click "OK" on it - have to CTRL+C the terminal to end the program.

What have I missed?

Works here fine too. No problems.

Dreamland Fantasy · Post by **Dreamland Fantasy** » Thu Dec 13, 2007 1:28 pm

That should work okay (I'm not in front of my Mac to test it just now).

Make sure that you are using the correct extension (.app) for the executable file name.

Kind regards,

Francis.

michel51 · Post by **michel51** » Thu Dec 13, 2007 3:02 pm

Karbon wrote:
messagerequester("Hi","Hello World")

End
i make the executable and run it and a terminal window opens, the message box is displayed but you can't click "OK" on it - have to CTRL+C the terminal to end the program.

What have I missed?

I have to read the whole posting

.
I tried again, and You are right.

Compiled as *.app is working fine, as expected.
compiled as "unix-executable" opens the terminal first and then the test-window is shown, but the OK-button cannot be pressed. That is because the terminal is in front and not the test-window.

Hm..., very interesting....

Dreamland Fantasy · Post by **Dreamland Fantasy** » Thu Dec 13, 2007 3:17 pm

Yes, it seems to be a classic pitfall for anyone not familiar with the Mac way of doing things (like myself!

).

I had a similar problem and it took me ages to figure out that i had to add '.app' to the end of the executable file name.

Kind regards,

Francis.

Karbon · Post by **Karbon** » Thu Dec 13, 2007 4:49 pm

Rename to .app and get "You can't open this application because the classic environment is no longer supported".

This is a new Mac so it's running 10.5.1

Dreamland Fantasy · Post by **Dreamland Fantasy** » Thu Dec 13, 2007 5:10 pm

Karbon wrote:Rename to .app and get "You can't open this application because the classic environment is no longer supported".

This is a new Mac so it's running 10.5.1

I'm using Mac OS X 10.5.1 as well.

I remember getting the same error as you, but I can't remember offhand how I resolved it. I'll have a look when I get home tonight and let you know.

Kind regards,

Francis.

Karbon · Post by **Karbon** » Thu Dec 13, 2007 5:45 pm

OK, so if you put ".app" when you compile it works - if you compile without it first then rename it - it doesn't.

Very strange

Post by **freak** » Thu Dec 13, 2007 5:51 pm

Karbon wrote:OK, so if you put ".app" when you compile it works - if you compile without it first then rename it - it doesn't.

Very strange

A .app is a directory (called bundle), not a single executable.
If you append the .app when compiling, the compiler generates the bundle directory,
else it only creates a single executable.

Karbon · Post by **Karbon** » Thu Dec 13, 2007 5:54 pm

Ah, well, there ya go.. I didn't realize that.

So is this a "classic" app?

Karbon · Post by **Karbon** » Thu Dec 13, 2007 6:30 pm

Additionally, "Get Info" tells me it's a PowerPC application. Since it was compiled and is running on an Intel machine I don't know if that is accurate

Dreamland Fantasy · Post by **Dreamland Fantasy** » Thu Dec 13, 2007 7:04 pm

Karbon wrote:Additionally, "Get Info" tells me it's a PowerPC application. Since it was compiled and is running on an Intel machine I don't know if that is accurate

It is accurate.

PureBasic for the Mac at present does not support the Intel processors and can only produce PowerPC executables. MacOS X interprets the PowerPC code into Intel code in order to be able to run it.

Glad you got your problem sorted!

Kind regards,

Francis.

Post by **freak** » Thu Dec 13, 2007 7:39 pm

Karbon wrote:Ah, well, there ya go.. I didn't realize that.

So is this a "classic" app?

You mean classic as in pre-OSX app ?
Nope, its a real OSX application. no classic support needed.

Karbon · Post by **Karbon** » Thu Dec 13, 2007 7:59 pm

Gotcha. The PowerPC thing is what threw me.. I got all confused with the Mac terminology - Cocoa, Carbon, Classic, .app, Unix application.. What they need is something else to call "a program"

PureBasic Forums - English

1 line program error?

1 line program error?

Re: 1 line program error?

Re: 1 line program error?

Re: 1 line program error?