Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14
  1. #11
    Join Date
    Oct 2007
    Location
    Madison, WI
    Posts
    11,623

    Default

    Thanks. I'll make a note to review that for our documentation.

    It is hard to determine what settings or combination of settings in BC3 or outside were locking your files. They could have been marked as read-only or detected as Read-only by BC3 at the time of the attempted editing. This could have been a bug or accurate. If you can reproduce it, please let us know.
    Aaron P Scooter Software

  2. #12
    Join Date
    Apr 2008
    Posts
    2,154

    Default

    > It is hard to determine what settings or combination of settings
    > in BC3 or outside were locking your files.

    Yup, that's what you get from undefined behaviour.

    > They could have been marked as read-only

    As I said twice already, they were writable.

    > If you can reproduce it, please let us know.

    When you can define the behaviour, please let me know.

  3. #13
    Join Date
    Oct 2007
    Location
    Madison, WI
    Posts
    2,507

    Default

    Quote Originally Posted by chrisjj View Post
    When you can define the behaviour, please let me know.
    A file can be marked as "Editing Disabled" for any of the following reasons:
    • It's one of the input files in a 3-way merge
    • The comparison was cancelled
    • The comparison encountered an error (corrupt file, invalid character encoding, out of memory, gamma rays, etc)
    • The file format's conversion settings don't support converting back to the original format
    • The file is on a read-only "filesystem" (7zip/RAR/CHM archives, CD/DVD-ROMs)
    • A file or parent folder had editing explicitly disabled by the user in the session settings or using the /ro command line switches
    • The viewer itself doesn't support editing (eg, Hex Compare)


    Our documentation will always lag the program, and we need to balance ease of use with coverage, so there will always be things that we don't think warrant explicit coverage in the help file. The fact that something isn't in the help file does not mean it's "undefined".
    ZoŽ P Scooter Software

  4. #14
    Join Date
    Apr 2008
    Posts
    2,154

    Default

    Thanks.

    >[*]The comparison encountered an error (corrupt file, invalid
    > character encoding, out of memory, gamma rays, etc)

    That's the only one that could apply.

    But since BC DID NOT REPORT ANY ERROR I'm really disappointed that it instead messes me about by secretly going into Editing Disabled mode.

    > Our documentation will always lag the program

    That really disappointing to hear.

    > and we need to balance ease of use with coverage

    I think you've failed dismally. Your docs' usability is severely degraded by ther poor coverage. And getting documentation instead out of this forum is like getting blood out of a stone.

    Not least because some your support people here don't know thae answers becasue, I guess, they too are deprived of full documentation.

    > The fact that something isn't in the help file does not mean it's
    > "undefined".

    Then please just publish the definition. Keep the cut-down help for those users who you think would be overwhemed by the complete docs (and I very much doubt there are many), and publish the full docs for those of us whose time is being wasted as a result of your current policy.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •