Author Topic: Manually inputing File Path v0.9.9.22  (Read 7216 times)

0 Members and 1 Guest are viewing this topic.

Offline tikivideo

  • Member
  • *
  • Posts: 12
    • View Profile
Manually inputing File Path v0.9.9.22
« on: December 13, 2010, 02:24:58 pm »
How can I manually type in the file path and or edit the location of the movie file without using the browse tab? With over 2200 movies on the hard drive, it is more convenient to type in the path without browsing the entire hard drive.

Thanks for such a wonderful program!

Offline rick.ca

  • Global Moderator
  • *****
  • Posts: 3241
  • "I'm willing to shoot you!"
    • View Profile
Re: Manually inputing File Path v0.9.9.22
« Reply #1 on: December 13, 2010, 09:06:32 pm »
You can type or paste data into the File path field, just like any other.

Offline tikivideo

  • Member
  • *
  • Posts: 12
    • View Profile
Re: Manually inputing File Path v0.9.9.22
« Reply #2 on: December 13, 2010, 09:34:12 pm »
When adding episodes, there is no input for the file path.  Then, when the database is edited, the file path cannot be edited, only browse is available.

Offline rick.ca

  • Global Moderator
  • *****
  • Posts: 3241
  • "I'm willing to shoot you!"
    • View Profile
Re: Manually inputing File Path v0.9.9.22
« Reply #3 on: December 13, 2010, 09:47:57 pm »
An episode record is exactly the same as a movie record. All fields are editable in edit mode.

Offline tikivideo

  • Member
  • *
  • Posts: 12
    • View Profile
Re: Manually inputing File Path v0.9.9.22
« Reply #4 on: December 13, 2010, 09:56:47 pm »
Thanks for replying, Rick,

No matter which record in the PVD I try to edit, I am not able to edit the file path field.  I left click on it but the cursor is never placed in the field to edit.  I can edit all other fields, except the file path.

Offline rick.ca

  • Global Moderator
  • *****
  • Posts: 3241
  • "I'm willing to shoot you!"
    • View Profile
Re: Manually inputing File Path v0.9.9.22
« Reply #5 on: December 13, 2010, 10:10:09 pm »
The behaviour is rather strange—apparently due to the field type used—but it is editable. It won't show the cursor location, and working with long or multiple paths that won't fit in the text box can be challenging. Nostra has indicated he will fix this in version 1.

 

anything