Recent

Author Topic: Message Dialog  (Read 23443 times)

Leledumbo

  • Hero Member
  • *****
  • Posts: 8114
  • Programming + Glam Metal + Tae Kwon Do = Me
Re: Message Dialog
« Reply #15 on: September 30, 2011, 08:35:17 am »
Quote
Is that a typo when you copied the error message or is that the actual error message?  Because I thought it should be MessageDlg not Messagedlg.
Should be no different, Pascal is case insensitive remember?

sfeinst

  • Full Member
  • ***
  • Posts: 186
Re: Message Dialog
« Reply #16 on: September 30, 2011, 04:17:54 pm »
Quote
Is that a typo when you copied the error message or is that the actual error message?  Because I thought it should be MessageDlg not Messagedlg.
Should be no different, Pascal is case insensitive remember?

See what happens when you are in the middle of a Java project.  All reasonable thought leaves your head.   %)

Epigear

  • New member
  • *
  • Posts: 7
    • Epigear.com
Re: Message Dialog
« Reply #17 on: October 01, 2011, 01:56:47 am »
Quote
I'm porting from Delphi 7. Could it be that it is looking at the Delphi 'Dialogs', I'm now realising.
Shouldn't matter, as the project won't search Delphi one (normally). Do you have LCL as dependency? What if you ctrl+click that 'dialogs' in uses clause? Does it open LCL dialogs unit?

When I CTRL click the dialogs in the uses clause it opens the Free Pascal dialogs unit, which does not have a Messagedlg function. So it seems to be a path problem.
What do you mean by "Do you have LCL as dependency?"?

Cheers,

Jan

Epigear

  • New member
  • *
  • Posts: 7
    • Epigear.com
Re: Message Dialog
« Reply #18 on: October 01, 2011, 04:19:02 am »
Quote
I'm porting from Delphi 7. Could it be that it is looking at the Delphi 'Dialogs', I'm now realising.
Shouldn't matter, as the project won't search Delphi one (normally). Do you have LCL as dependency? What if you ctrl+click that 'dialogs' in uses clause? Does it open LCL dialogs unit?

When I CTRL click the dialogs in the uses clause it opens the Free Pascal dialogs unit, which does not have a Messagedlg function. So it seems to be a path problem.
What do you mean by "Do you have LCL as dependency?"?

Cheers,

Jan

OK, I have set in the Project options paths to lcl, lcl\include, lcl\units. Now my project compiles until the final end, where I get a stream of error messages saying "JanBxl.dpr(57,1) Error: Undefined symbol: WSRegisterCustomImageList" and so on with a whole lot of other similar messages. So I tried to make the compiler look in the lcl\widgetset directory, but that doesn't work. Now what?
I'm clearly a newbie, but it doesn't seem to make a lot of sense to me that you have to set all these search paths at the project level. Am I missing something?

Cheers,

Jan

Leledumbo

  • Hero Member
  • *****
  • Posts: 8114
  • Programming + Glam Metal + Tae Kwon Do = Me
Re: Message Dialog
« Reply #19 on: October 01, 2011, 08:22:29 am »
Quote
When I CTRL click the dialogs in the uses clause it opens the Free Pascal dialogs unit, which does not have a Messagedlg function
You open dialogs unit of Free Vision package (Turbo Pascal's Turbo Vision compatible package). If you have LCL as dependency, this should not happen (it'll open LCL dialogs unit instead).
Quote
OK, I have set in the Project options paths to lcl, lcl\include, lcl\units
NOOOO..!!! NEVER EVER DO THAT! It's in the FAQ AFAIK, please read it.
Quote
What do you mean by "Do you have LCL as dependency?"?
Open project inspector, open dependencies tab, look for LCL in the drop down and add (unless it's already there).
Quote
JanBxl.dpr(57,1) Error: Undefined symbol: WSRegisterCustomImageList
Add Interfaces to the uses clause in .lpr file.

Epigear

  • New member
  • *
  • Posts: 7
    • Epigear.com
Re: Message Dialog
« Reply #20 on: October 01, 2011, 09:40:35 am »
Quote
When I CTRL click the dialogs in the uses clause it opens the Free Pascal dialogs unit, which does not have a Messagedlg function
You open dialogs unit of Free Vision package (Turbo Pascal's Turbo Vision compatible package). If you have LCL as dependency, this should not happen (it'll open LCL dialogs unit instead).
Quote
OK, I have set in the Project options paths to lcl, lcl\include, lcl\units
NOOOO..!!! NEVER EVER DO THAT! It's in the FAQ AFAIK, please read it.
Quote
What do you mean by "Do you have LCL as dependency?"?
Open project inspector, open dependencies tab, look for LCL in the drop down and add (unless it's already there).
Quote
JanBxl.dpr(57,1) Error: Undefined symbol: WSRegisterCustomImageList
Add Interfaces to the uses clause in .lpr file.

Since I posted I've been reading up on the Help, and saw that setting those paths wasn't supposed to be OK. So I removed them, but now I'm back to square 1: the dialogs unit is the Free Pascal (or Free Vision) one, and things don't compile.

When I open Project Inspector, I don't see a Dependencies tab, and no drop down list. I have attached what I get to see.

Cheers,

Jan

Leledumbo

  • Hero Member
  • *****
  • Posts: 8114
  • Programming + Glam Metal + Tae Kwon Do = Me
Re: Message Dialog
« Reply #21 on: October 01, 2011, 02:58:28 pm »
OK, looks like I should be very clear here. From your image, it's clear that it doesn't have LCL dependency. On the page, dependencies are listed below "Required packages" node. Now, to add one, press "+" button and move on to "New Requirement" tab, the drop down is named "Package Name". Look for "LCL" and click "OK", done. Now you should see it's listed below "Required packages" and try recompiling. Hope it works now.

Epigear

  • New member
  • *
  • Posts: 7
    • Epigear.com
Re: Message Dialog
« Reply #22 on: October 02, 2011, 12:01:10 am »
Thanks a million: now it compiles. The only thing I have to work out now is why Excel crashes on this version whille it works fine with the Delphi 7 version  :(

Leledumbo

  • Hero Member
  • *****
  • Posts: 8114
  • Programming + Glam Metal + Tae Kwon Do = Me
Re: Message Dialog
« Reply #23 on: October 02, 2011, 05:07:36 am »
Quote
The only thing I have to work out now is why Excel crashes on this version whille it works fine with the Delphi 7 version
Happy debugging :D
If you think it's a bug, feel free to trim down the project to a very minimal version and report it to the bugtracker.