Zum Hauptinhalt gehen

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

No C:\\ in C1 v4 folder browser (and other brokeness of v4)

Kommentare

3 Kommentare

  • Permanently deleted user
    Well, you can easily open files anywhere on your computer....
    See the triangle in the directory preceeding your computer name?
    Click on it.....
    Nice, huh?
    0
  • MikeArst
    > there's no C: drive shown at all. How do I now get to the directories on the C: drive??

    Drive C: does not appear when you expand "My Computer" (or whatever name appears below "Desktop") by clicking the triangle to its left?

    > When I go to the "Exposure" pane, the Curve window goes off the bottom of the screen (I'm still at 1024x768 on a 17" monitor at present).

    Same problem here -- same resolution settings on a 19" monitor. The Curves panel problem is a "known issue," per the release notes. Why a major UI element's failure to display fully (in some circumstances) was not considered a ship-stopper, I don't know. I think they could have done something about this, some temporary fix. Sadly, they didn't.

    > Why not just design a decent (i.e, native) UI instead?

    From where I sit that's a perfectly reasonable question. And I agree with you about the preferences dialog's "thin" content. I found that kind of shocking, considering the extensive preferences settings available in other applications of this type.

    > Why is the Help file a PDF instead of a real (context-sensitve) help system?

    I can speak from experience here: in companies with an "engineering-heavy" mindset, documentation often takes a back seat. I could live with the documentation's not being context-sensitive. But -- not even a proper table-of-contents panel ("bookmarks") within the PDF file? That is not a good way to do PDF-based help. It isn't as if creating the bookmarks were mind-twistingly difficult. You set up your doc-authoring and PDF-building processes right the first time, and you're home free afterward -- each time you rebuild the online help. You're right about the lack of easily "discoverable" info on upgrading. I find that baffling. But again, it's the kind of thing that happens with documentation (and web sites) in an "engineering-heavy" work environment, especially one where there is nobody acting as a kind of end-user ombudsman. The end-user becomes a conveniently malleable hypothetical person whose satisfaction can always be predicted: whatever we give them, will satisfy them (or satisfy them enough to suit our purposes)...a closed system.

    Creating non-mediocre documentation is expensive. But when the app is complex, spending real-world money on good documentation can produce higher customer satisfaction and noticeably lower support costs. When the "ambient" mind-set is not end-user-oriented, this point nearly always falls on deaf ears. The costs typically drive the documentation project out of the company's mind. I've seen it happen often.

    Even on P.O.'s web site, finding clear information about how to upgrade is difficult. From message traffic here I take it a number of users have felt that same pain. It's an unnecessarily convoluted system and one that -- here I'm just taking a wild guess -- might be sometimes compromised by problems with P.O.'s servers or databases.

    I had only slight trouble upgrading 3.7 to 4. If it had proven more difficult I would simply have kissed the program goodbye.

    Clearly P.O. has put a lot of time and money into the raw conversions. I never liked v.3.7 but I'm impressed by v.4's conversions, including its rendering of fine image detail -- best I've seen so far. So the program can produce superb results, but sadly, the end-user "stuff" seems to have taken a seat a bit too far in back. One message thread here is entitled "How can we effect change" (in v4?) Good question. It's hard to know what attention P.O. pays to comments posted in the forum. Bare-bones 'how do I' questions are sometimes answered, but that's about it...
    0
  • photogenix
    I for one think is strange they decided on a system requirement to have a minimum vertical resolution of 800 instead of 768. That extra 32 lines on the screen really excludes a lot of people. I haven't tried the final release, but in the betas, using my laptop (1280x800, the minimum res in the C1v4 system requirements), the curve tool was still chopped off significantly, meaning that even their system requirement was not sufficient to use all the product.
    0

Post ist für Kommentare geschlossen.