FineLineIDE

[mackrackit]

The INCLUDE command is part of PBP, the text editor used to write the code does not have anything to do with it.

[Normnet]

The INCLUDE command is part of PBP, the text editor used to write the code does not have anything to do with it.

Correct; for compiling PBP finds the include files.

Gusse may be opening the include files with a click in the explorer window.
The next version of FL will also do an explorer open if the full path is provided in the include.

I'm not sure how to code for a partial path as it could be anywhere on the hard drive and doing a search could take several minutes in some cases unless their is a way to limit it.


Norm

[Gusse]

I'm not sure how to code for a partial path as it could be anywhere on the hard drive and doing a search could take several minutes in some cases unless their is a way to limit it.

Relative path should be always linked to main pbp-file folder (at least this is how it is done in MicroCode Studio), so that should fix the location in HD.

-Gusse-

[Normnet]

Relative path should be always linked to main pbp-file folder (at least this is how it is done in MicroCode Studio), so that should fix the location in HD.

-Gusse-

You are saying if the include isn't in the main pbp folder it is within one of it's sub folders?


Norm

[Gusse]

You are saying if the include isn't in the main pbp folder it is within one of it's sub folders?

It doesn't have to be a sub folder in main pbp-file folder. It can be any folder and path is point to it (same like in command prompt, i.e: "cd .." goes 1 level up for current folder).

Example:
If main pbp-file is located

c:\pic\pbp\prog\

and include files

c:\pic\pbp\incl\

In MCS I can do

include "..\incl\[filename_to_be_included].pbp"

so starting folder is "c:\pic\pbp\prog" and then it goes one level up "c:\pic\pbp" and then to "incl"-folder, which is parallel to prog.

-Gusse-

[Normnet]

It doesn't have to be a sub folder in main pbp-file folder. It can be any folder and path is point to it (same like in command prompt, i.e: "cd .." goes 1 level up for current folder).

so starting folder is "c:\pic\pbp\prog" and then it goes one level up "c:\pic\pbp" and then to "incl"-folder, which is parallel to prog.

-Gusse-

So FL should look in main pbp file folder and all of its sub folders and all up clicks to root(C:\)?


Norm

[mackrackit]

I think PBP only looks in the directory the code is in and the directory PBP is in. Any other location needs to have the path to the include in the code. So look in the two default locations and parse the INCLUDE line for the other possible locations???

[Normnet]

It doesn't have to be a sub folder in main pbp-file folder. It can be any folder and path is point to it (same like in command prompt, i.e: "cd .." goes 1 level up for current folder).
so starting folder is "c:\pic\pbp\prog" and then it goes one level up "c:\pic\pbp" and then to "incl"-folder, which is parallel to prog.

-Gusse-

Gusse

Problem: Opening an include in FL explorer which is located in a parallel directory.
I have written a include open routine which does what you have requested in FineLineIDE.

In tests with MCS however I am unable to duplicate opening an .inc in: M:\PBP3\ABC INCLUDE
with the .pbp program in: M:\PBP3\ABC PROGRAM
when called out as: Include "...\ABC INCLUDE\TEST1.INC"

I am using Microcode Studio 5.0.0.0 and compiler PBPX 3.0.1.4
What versions are you using?

I can email you a test version of FL with the new include routine if you PM me your email address.

Norm

[Gusse]

Hi Horm,

There are still couple of issues that I noticed in brief trial with v2.0.0.1 BETA.
------------------------------------------------------------------------------
If you re-open FL, then it cannot compile file. (require that file has been once openned with FL earlier). Same issue that I noticed also earlier.
"Invalid Include Path: "..\incl\PIC18F4520_config.pbp" Aborting Compile"

If you open same file again (with Ctrl+O or with button) then it will compile the file.
------------------------------------------------------------------------------
Include files are accessible, but when you try to close them then FL says (pop-up):
"FL THREAD ERROR 0" and there is OK button. Once pressed OK, another pop-up will come up with same error again. And again and again... Only by pressing "Close Tab" button again error message will disappear.

At least I can repeat this issue when I open all include files and close FL, then re-open FL and try to close include tabs.
------------------------------------------------------------------------------

Used test file: http://www.mediafire.com/?yty070ruqh4ycyh

BR,
-Gusse-