Propellent misfeatures
kuisma
Posts: 134
Setting up a new tool chain using propellent v1.3, I found the following misfeatures.
- Propellent uses its own installation directory as default path for the file to compile, not current working directory.
- The propeller download page (http://www.parallax.com/tabid/442/default.aspx) links to the old v1.2 Propellent.
- Using command line, "propellent.exe /gui off" produces no output unless redirected. E.g. "propellent.exe /gui off | more" works, but not without piping it to more.
- Referring the same object from multiple spin files, Propellent will compile this object multiple times.
- Propellent more than happily loads the PropScope if it happens to be connected.
- Propellent uses its own installation directory as default path for the file to compile, not current working directory.
- The propeller download page (http://www.parallax.com/tabid/442/default.aspx) links to the old v1.2 Propellent.
- Using command line, "propellent.exe /gui off" produces no output unless redirected. E.g. "propellent.exe /gui off | more" works, but not without piping it to more.
- Referring the same object from multiple spin files, Propellent will compile this object multiple times.
- Propellent more than happily loads the PropScope if it happens to be connected.