Just great! not what i need right now!

Robert Whetton

• 2008年02月12日 00:05

so i upgrade to V4.01 because you've fixed a load of bugs.. well you forgot to fix the bug where i can no longer edit my 20D RAW files!!! i've tried re-installing 4.01, i've deleted the cache...

i've tried rolling back to v4.0, and deleting the cache.. but oh no nothing, my files just sit there, i can see the thumbs, they all have an eye icon in the bottom right, and i can do nothing to edit my files!

my system

E6750 Core 2 Duo, 8GB RAM, XP64

i have a deadline that i'm now unable to make because of this stupid upgrade broke!

0

• 

  SteveCa

  • 2008年02月12日 03:30

  On my computer those files with the eye in the corner are jpeg or tiff files. Can't process those with 4.0. I figure you already knew that. 😉
  
  Are your files on a remote drive?

  0
• 

  MikeArst

  • 2008年02月12日 08:02

  [quote="SteveCa" wrote:
  On my computer those files with the eye in the corner are jpeg or tiff files.

  
  I saw that eye-icon last night and was completely perplexed by it -- the files were *raw* files, not TIFF or JPEG. And, I couldn't edit them.
  
  Then I realized they were read-only -- and I remembered having read something here about read-only files being un-process-able in C1v4. What a bizarre thing. The program doesn't write any sort of metadata into raw files, right? I suppose it cares if the files are read-only because for all it "knows," you might be planning to move them via the "move-to" control. Ok, I get that bit. But then why not *warn* the user in some way other than a near-microscopic icon that looks like an eye (and what the **** does an *eye* convey about a file being read-only?). Why *no* response from the program when the user double-clicks the read-only raw file's thumbnail-image in the browser?
  
  Why not allow the files to have adjustments added -- the metadata files containing the adjustments-data aren't read-only! -- but then warn the user that the files can't be moved via the C1 UI?
  
  Just another rather bizarre user-interface "thing" in this program. Sigh...

  0
• 

  SteveCa

  • 2008年02月12日 15:22

  (and what the **** does an *eye* convey about a file being read-only?).

  
  
  You can only *look* at the file. ?

  0
• 

  MikeArst

  • 2008年02月13日 04:47

  [quote="SteveCa" wrote:
  

  (and what the **** does an *eye* convey about a file being read-only?).

  
  You can only *look* at the file. ?

  
  Ok . . . that makes sense in theory. But this business of using tiny maybe-recognizeable/maybe-not-recognizeable icons as notifications, without tool tips or the like, is not good UI design. "Everybody" does that sort of thing, and it's wrong every time they do it. Icons with non-obvious meanings...no, not good UI design.
  
  It makes perfect sense that the program would block a "move-to" operation if the original raw file is read-only. But prevent any editing at all, without even a real-world error message?

  0

投稿コメントは受け付けていません。