forums.silverfrost.com

LitusSaxonicum · Posted: Fri Jan 20, 2023 11:28 am Post subject: Resource not found message

Why is it that sometimes a resource listed in a RESOURCES section or in a separately compiled .RC file cannot be found, and FTN95 tells you this in a "Resource not found" message? (Apart from the obvious, that FTN95 hasn't found it - but why?)

I can understand it if the path has a space in it.

The workaround that I discovered many years ago is to put the resource name in double quotes, as in:

PaulLaidler · Posted: Fri Jan 20, 2023 11:52 am Post subject:

I am not sure but for 64 bit applications the RESOURCES directive only works when using /LINK or /LGO on the command line.

LitusSaxonicum · Posted: Fri Jan 20, 2023 5:31 pm Post subject:

Hi Paul,

I'll pass it on. I generally use SRC for some applications, and RESOURCES for others. It's been a while since I saw the issue, but recognised it when someone else had it.

Eddie

wahorger · Joined: 13 Oct 2014 Posts: 1227 Location: Morrison, CO, USA

And don't forget to double the backslashes when you specify a path, even in double quotes.

wahorger · Joined: 13 Oct 2014 Posts: 1227 Location: Morrison, CO, USA

BTW: The HELP files are created with a different utility that requires different syntax. So spaces aren't really an issue. It's a hyperlink, after all.

LitusSaxonicum · Posted: Sat Jan 21, 2023 12:58 pm Post subject:

Bill,

I'm confused now. I put all my resources in the same sub-directory, so for a logo bitmap that I'll put on a drawing with IMPORT_IMAGE@, I might have:

wahorger · Joined: 13 Oct 2014 Posts: 1227 Location: Morrison, CO, USA

Here is my "standard" resource file with an error introduced in the path name of my_warning. I've only included a couple of lines before and after. The path name has spaces, so has to be in quotes. The inclusion of the quotes necessitates the syntax change.

wahorger · Joined: 13 Oct 2014 Posts: 1227 Location: Morrison, CO, USA

And, no, so far as I can tell there is no reference in the documentation to using the double backslashes for a path name that is in double quotes within a resource file.

I discovered this as I was cleaning up my main folder, putting my icons and BMP's into their own folder.

I don't happen to use hypertext (%ht) either, so I cannot comment on syntax there. However, it is very likely that the same syntax requirement would persist when using a resource file and something like:

PaulLaidler · Posted: Sat Jan 21, 2023 3:35 pm Post subject:

SRC is an adaptation of the C++ compiler SCC so the strings are C strings and the backslash is an escape character.

Code written for a Fortran compiler uses Fortran CHARACTER variables and literal constants where the backslash is like any other character.

I agree that the documentation ought to say this.

LitusSaxonicum · Posted: Mon Jan 23, 2023 11:32 pm Post subject:

I'd have never found the double slash solution! If I'd had the message about \C being unrecognised, that would have pointed to where the error was, but not how to solve the problem*. Was the other error because the file wasn't there? The error that provoked me in the first place occurred when the program was run.

Eddie

*I can often go to the root of the problem with Fortran syntax errors (but not always at first): RESOURCES are a different matter. Fortunately, there aren't that many mistakes you can make.

wahorger · Joined: 13 Oct 2014 Posts: 1227 Location: Morrison, CO, USA

Eddie,

I went back to re-read your original posting. There are at least two different questions posed, and I apologize if I took it off of the actual topic.

The one that refers to FTN95.CHM and path names has nothing to do with Resource Files that are tied to a compiled program. The HELP file is a separate entity, with it's own syntax requirements, BEFORE you run it through the program that actually builds the HELP file that you see as FTN95.CHM.

Since SRC is a C-Compiler "variant", it is quite possible that some of the syntax held over (Paul could comment on that, I'm guessing) for how file names and paths are handled syntactically.

In "C", if you specify a file name in <> brackets, it is a global (aka system) filename. One uses this for #include's for system declarations, as an example. if the file name is enclosed in double quotes, the file is assumed to be local to the current working directory or uses one of the specified paths supplied on the command line or an environment string. S

So, maybe, with only a file name present, the SRC resource compiler looks-for/compiles-for one place for the file, and if in double quotes, it looks elsewhere. Or, if the full path name is specified, it looks specifically at one place only.

And, it is possible, since you can bind resources at run-time, that all that exists in the compiled code are resources that can be found, and if not found are only references to external resources that would not likely be found on a user's system.

Not knowing exactly how a resource file is constructed, I'm only guessing, but it is logical guessing!

Bill

LitusSaxonicum · Posted: Wed Jan 25, 2023 6:16 pm Post subject:

Hi Bill,

I suspect that you have read more into the second question than I intended. I'm reading FTN95.CHM with the Mk 1 eyeball as a substitute for a printed manual, which I hanker after. I suppose that I could look at PLATO's help, but my first goto is that CHM file. I'm certainly not smart enough to parse it as a C compiler would!

The examples I've seen all look not to have paths.

Eddie