Using EWB 2.02B1 which was upgraded from 2.01.

I want to change the TDialog background for a specific application so I
copied the supplied TDialog.wbi interface file into my project directory
and altered/saved it via the Interface Editor.

I rebuilt the library but the IDE form designer doesn't show the changes
to the TDialog background. It continues to display the supplied
interface. If I run the application then my changes do show correctly
(including the ShowMessage dialog, etc.) so compilation is using the wbi
file from the project directory.

If I click the open control interface tool bar button then the supplied
TDialog.wbi file is opened rather than the one saved in the project
directory.

It appears then that the IDE form designer is using the supplied wbi
file whereas the compiler is using the wbi file from the project directory.

Is this the correct process? I only want the TDialog interface changes
to be available to this one specific application. Is there something I
need to do in the IDE to force it to use the wbi file located in the
project directory?

--
Rick

In EWB, in Environment Options from the menu, you need to add the path to your modified interfaces in the Component Library search path.

Rick wrote:

Using EWB 2.02B1 which was upgraded from 2.01.

I want to change the TDialog background for a specific application so I
copied the supplied TDialog.wbi interface file into my project directory
and altered/saved it via the Interface Editor.

I rebuilt the library but the IDE form designer doesn't show the changes
to the TDialog background. It continues to display the supplied
interface. If I run the application then my changes do show correctly
(including the ShowMessage dialog, etc.) so compilation is using the wbi
file from the project directory.

If I click the open control interface tool bar button then the supplied
TDialog.wbi file is opened rather than the one saved in the project
directory.

It appears then that the IDE form designer is using the supplied wbi
file whereas the compiler is using the wbi file from the project directory.

Is this the correct process? I only want the TDialog interface changes
to be available to this one specific application. Is there something I
need to do in the IDE to force it to use the wbi file located in the
project directory?

--
Rick

On 16/10/15 11:02, Alan Questell wrote:
> In EWB, in Environment Options from the menu, you need to add the path to your modified interfaces in the Component Library search path.
>

Yeah, but doesn't Environment Options affect all projects? I only want
the interface change for a specific project and no others (they continue
to use the default).

According to the help manual, interfaces can be loaded from the project
compilation source path. This is true but it doesn't seem to show the
changes in the IDE form designer.

--
Rick

The component library would have to be rebuilt to see changes in the IDE.


Rick wrote:

On 16/10/15 11:02, Alan Questell wrote:
> In EWB, in Environment Options from the menu, you need to add the path to your modified interfaces in the Component Library search path.
>

Yeah, but doesn't Environment Options affect all projects? I only want
the interface change for a specific project and no others (they continue
to use the default).

According to the help manual, interfaces can be loaded from the project
compilation source path. This is true but it doesn't seem to show the
changes in the IDE form designer.

--
Rick

On 16/10/15 13:26, Alan Questell wrote:
> The component library would have to be rebuilt to see changes in the IDE.
>

Yep, I did this as indicated in the OP.

It's OK if the modified wbi file is in the Environment Options component
library search paths but not if it is in the project directory.

--
Rick

Rick,

<< Is this the correct process? I only want the TDialog interface changes to be available to this one specific application. Is there something I need to do in the IDE to force it to use the wbi file located in the project directory? >>

You can't really do what you're wanting to do.   Currently, you have to modify the Library Search Paths in the Environment/Options dialog in order to affect what (source units/interfaces) is used with the component library at design-time.

Tim Young
Elevate Software
www.elevatesoft.com

On 17/10/15 02:57, Tim Young [Elevate Software] wrote:
> You can't really do what you're wanting to do.   Currently, you have to modify the Library Search Paths in the Environment/Options dialog in order to affect what (source units/interfaces) is used with the component library at design-time.
>

OK, thanks for the clarification Tim. I've created an "interfaces"
directory in the project directory and added it to Environment Options.
It contains modified supplied interfaces that are used by that one
specific project. I just move it up and down the list as necessary.

Is this something you will be addressing in the future? Maybe something
like a "Solution Manager" capability in the IDE would be useful where
multiple projects can be opened at the same time along with specific
project oriented interfaces and controls. I'm finding that I have
related projects along with controls and interfaces that belong only to
them.

--
Rick

Rick,

<< Is this something you will be addressing in the future? >>

Yes.  I just looked into this recently, and it is definitely possible to dynamically replace the interfaces at design-time as products are loaded/unloaded.  I just need to work out the search path logic, and then it's all ready to go.

Tim Young
Elevate Software
www.elevatesoft.com

On 20/10/15 07:17, Tim Young [Elevate Software] wrote:
> << Is this something you will be addressing in the future? >>
>
> Yes.  I just looked into this recently, and it is definitely possible to dynamically replace the interfaces at design-time as products are loaded/unloaded.  I just need to work out the search path logic, and then it's all ready to go.
>

Good news, thanks Tim.

--
Rick

On 20/10/15 07:17, Tim Young [Elevate Software] wrote:
> << Is this something you will be addressing in the future? >>
>
> Yes.  I just looked into this recently, and it is definitely possible to dynamically replace the interfaces at design-time as products are loaded/unloaded.  I just need to work out the search path logic, and then it's all ready to go.
>

Just tried out loading a project specific interface using EWB 2.03 ...
works perfectly. Thanks Tim!

--
Rick