Viewport Options
jazzed
Posts: 11,803
I would like to use ViewPort's debugger on a project.
ViewPort installed with my admin user path as the default, but I never use the admin login; this causes issues since almost all my development has not been done as admin user. Also I find that I have no control over the Propeller Tool library path ... this is particularly painful.
Any help?
ViewPort installed with my admin user path as the default, but I never use the admin login; this causes issues since almost all my development has not been done as admin user. Also I find that I have no control over the Propeller Tool library path ... this is particularly painful.
Any help?
Comments
ViewPort currently uses Parallax's Propellent to compile code- so objects must be either in the same directory as the object you're compiling or in the Propeller library. Yes, I too don't like that limitation and am considering switching to homespun- any thoughts?
Click on the welcome page "browse" button to browse to a new directory- it shouldn't matter where you installed ViewPort.
Hanno
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Co-author of the official Propeller Guide- available at Amazon
Developer of ViewPort, the premier visual debugger for the Propeller (read the review here, thread here),
12Blocks, the block-based programming environment (thread here)
and PropScope, the multi-function USB oscilloscope/function generator/logic analyzer
Hanno, Propellent has a library option on the command line.
The tutorials are installed in the admin directory ... extremely confusing.
John Abshier
Hanno
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Co-author of the official Propeller Guide- available at Amazon
Developer of ViewPort, the premier visual debugger for the Propeller (read the review here, thread here),
12Blocks, the block-based programming environment (thread here)
and PropScope, the multi-function USB oscilloscope/function generator/logic analyzer