Tools Tied to Workspaces??
Posted: Thu May 12, 2005 12:05 pm
Hello,
A couple of questions about tools:
1. Is it possible to have a tool buttons appear in the Navigation bar?
2. Is it possible to add buttons or redefine buttons on the Toolbar?
3. Is it possible to bind tools to a particular workspace only?
Here is my situation, I want to use the editor across numerous platforms and projects. Some C code will be for microcontrollers and will use the Compiler specific to that controller. Some C code will be for microprocessors and will use either the Borland or Microsoft compiler. Finally, Verilog and perhaps VHDL will be used for programmable logic.
If the tools are bound to the workspace, then the programmable logic tools are invisible in a C code workspace and vice-versa. Also, there would be no chance of attempting to build C code for a micrcontroller using the Borland compiler for example.
Finally, even within a particular type of project, some tools are unique to the workspace. For example, I often need to copy files from the build machine across the network to the target test machine. The file names and directories used vary project by project. By having a local tool binding to do this, I could not inadvertantly change files on the target test machine just by clicking on the wrong tool.
Thanks.
---- Steve
A couple of questions about tools:
1. Is it possible to have a tool buttons appear in the Navigation bar?
2. Is it possible to add buttons or redefine buttons on the Toolbar?
3. Is it possible to bind tools to a particular workspace only?
Here is my situation, I want to use the editor across numerous platforms and projects. Some C code will be for microcontrollers and will use the Compiler specific to that controller. Some C code will be for microprocessors and will use either the Borland or Microsoft compiler. Finally, Verilog and perhaps VHDL will be used for programmable logic.
If the tools are bound to the workspace, then the programmable logic tools are invisible in a C code workspace and vice-versa. Also, there would be no chance of attempting to build C code for a micrcontroller using the Borland compiler for example.
Finally, even within a particular type of project, some tools are unique to the workspace. For example, I often need to copy files from the build machine across the network to the target test machine. The file names and directories used vary project by project. By having a local tool binding to do this, I could not inadvertantly change files on the target test machine just by clicking on the wrong tool.
Thanks.
---- Steve
