Shop OBEX P1 Docs P2 Docs Learn Events
Propeller Tool - How to un-hide project files? — Parallax Forums

Propeller Tool - How to un-hide project files?

Hey guys,
I am wanting to set up some source control for these propeller project files. I noticed that for some unknown reason, the propeller tool keeps the files hidden from the file explorer? Is there a way to disable this "feature"? I want to set up a working directory, and its not going to work if the files are hidden like this.

How do you guys have your projects set up, and do you develop the firmware in propeller tool or something else?

Comments

  • rosco_pcrosco_pc Posts: 464
    edited 2016-03-23 19:44
    Which project files? Have an example?

    In propeller tool you have all your spin/pasm files in 1 folder
  • Cluso99Cluso99 Posts: 18,069
    Objects (Spin/pasm) files can also be in a library directory which can be setup in the preferences setting.
    There are no project files as such, but when you compile there is a xxxx.txt file created in the source directory with the same prefix filename as the main spin sourcefile name. This is just a text picture of the files/objects used in the compile.
  • I am just referring to any spin file. So if I create a folder inside the "Projects" folder, and create a spin file in there... this file is hidden from explorer, and only spin tool can access this file.
    I have a source control server setup, and I need to be able to make changes to these files outside of the propeller tool program...e.g. explorer.
  • Cluso99Cluso99 Posts: 18,069
    If it is the extension .spin (and probably others or all), you need to change preferences in windows explorer. The default often hides the extensions - I turn them on immediately I install a new Windows version.
  • MahonroyMahonroy Posts: 175
    edited 2016-03-24 01:54
    No, you are not getting it.....

    Ok... when I am in the prop tool program, notice how I have a folder called "Projects" highlited in blue:
    prop_hidden2.jpg

    Now when I navigate to this folder in windows explorer, the folder is not there...:
    prop_hidden1.jpg

    My windows is configured to always show hidden files by the way. This is like a virtual directory or something, doesn't make any sense.
    959 x 643 - 211K
    934 x 801 - 125K
  • I'm using Windows XP and my explorer shows subfolder "projects", its subfolder "test", and "test1.spin". There is nothing virtual about the files (I can copy/move them in explorer to another folder, or open test1.spin with notepad).

    From your screen shot above, I realize that you are using a later version of windows. There must be something in the explorer options that is causing it not to show the projects subfolder?

    tom
  • SapphireSapphire Posts: 496
    edited 2016-03-24 03:33
    The problem is you installed the Propeller Tool in the Program Files (x86) directory. Windows does not allow applications to write files in any of these subdirectories, and instead creates a VirtualStore which has them under your user name. The application can access them, but Explorer has to be pointed to them, which makes finding things difficult.

    The path to your files is probably something like this:

    C:\Users\USERNAME\AppData\Local\VirtualStore\Program Files (x86)\Parallax Inc\Propeller Tool v1.3.2\Library

    where USERNAME is your Windows logon user name.

    What I would recommend is uninstall Propeller Tool, and reinstall it in its own subdirectory, so that the files you create can be seen by Explorer where they really are and not in the VirtualStore.
  • Been there, done that, it's a nuisance. I had to re-install as well as edit the path info in the registry.
    Erlend
  • Thanks for the tips guys, that makes sense. I'll definitely give this a shot.

  • 'Another gotcha to be aware of: if the app stores and updates a .ini file in the Program Files app directory, the new version goes in the virtual store. If you uninstall, then reinstall the app, The updated .ini file stays behind and takes effect when the new install is run. This drove me crazy for weeks before I figured out what was going on.

    -Phil
Sign In or Register to comment.