メインコンテンツへスキップ

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

Few cosmetic bugs in v.6

コメント

12件のコメント

  • Paul Steunebrink
    I suggest you post it in a support case. Though monitored and moderated by Phase One, this user forum does not guarantee you your experiences are logged and forwarded to R&D.
    0
  • PhilippePierre
    Thank's Paul_E, good advice, i did.
    Ph.
    0
  • Drew Altdo
    [quote="PPP" wrote:

    Filmstrip/Grid/List View pop-up icon menu partly unseen

    Post a Screenshot please.
    [quote="PPP" wrote:
    New Session -> Capture Name deleted

    Fixed in 6.0.1
    [quote="PPP" wrote:

    Copying a file name with "command+a" copies also the file extension

    This is an option in the New Batch Rename tool.
    [quote="PPP" wrote:
    After deleting files in Browser, selection gets back to first capture

    Can't say I saw that in Capture One 6.0 but it doesn't occur in 6.0.1 for sure.
    [quote="PPP" wrote:

    Window "Viewer" stays behind other applications windows, if any.

    This is an OS issue that occurs in MANY other programs. The Activites Window is a different kind and stays present on top no matter what application you browse to.
    0
  • thowi
    [quote="Drew " wrote:
    [quote="PPP" wrote:
    After deleting files in Browser, selection gets back to first capture

    Can't say I saw that in Capture One 6.0 but it doesn't occur in 6.0.1 for sure.
    Same behavior in 6.0 and 6.0.1 on my machine: after deleting files the selection goes back to the first capture in the browser... not to the last capture (the browser set to regular order, not to reversed order).
    This is after a clean uninstall of 6.0 prior to upgrading to 6.0.1. ...
    0
  • Drew Altdo
    Gotcha... it was the "Selection" (implying more than one) that I missed. Deleting one at a time does not show this error.
    0
  • thowi
    [quote="Drew " wrote:
    Gotcha... it was the "Selection" (implying more than one) that I missed. Deleting one at a time does not show this error.
    Hi Drew,

    it's a bit different. after deleting an image C1 autmatically selects the next capture... not the previous capture.

    let's say you've got 10 captures in your session folder.

    - if you delete capture #7 C1 selects the next capture afterwards, so capture #8 (i.e. "old" #8, now #7).
    - if you select and delete captures #3 - #5 (or multiple selection) C1 automatically selects the first capture afterwards.
    - if you delete capture #10 - so the last capture - C1 selects the first capture afterwards (as with multiple selection).

    So as long as you only select and delete a single image (but NOT the last one) everything is "okay".
    But if you select and delete multiple images - or the last image - ... it's not okay.

    Would you please forward this to the software team?
    0
  • Drew Altdo
    [quote="thowi" wrote:

    Would you please forward this to the software team?


    You are welcome to provide a support case so that we are sure to get it to the right department.
    0
  • thowi
    [quote="Drew " wrote:
    [quote="thowi" wrote:
    Would you please forward this to the software team?
    You are welcome to provide a support case so that we are sure to get it to the right department.
    i thought there is already a support case running... and that you guys talk to each other now and then 😄

    I'll copy a link to this post when I send my next support case... I guess I still have some support cases to file until I will finally get a 5th option in the color preferences providing rel.col with black point compensation ☹️
    0
  • PhilippePierre
    Drew wrote:
    Gotcha... it was the "Selection" (implying more than one) that I missed. Deleting one at a time does not show this error.
    thowi wrote:
    Hi Drew,
    it's a bit different. after deleting an image C1 autmatically selects the next capture... not the previous capture.[...]

    Thank you Thowi for this explanation in much complete and better english than mine. The problem you perfectly described is exactly the one i encounter.

    thowi wrote:
    i thought there is already a support case running...
    yes, one at least: case no 82612.
    It seems now that all described bugs have been reproduced and should be fixed soon i guess: C.O. v.2011 ?
    Ooops! sorry, v.6.1 ?...

    PPP wrote:
    New Session -> Capture Name deleted
    Drew wrote:
    Fixed in 6.0.1

    No sorry Drew, it has been partly fixed in the latest version 6.0.1 (did you forget to throw away your preferences file?...) 😊
    Here is what i just send to complete the previously running support case:
    When making a new session, the chosen name for the capture(s) name(s) to come (parameter: Capture Name) is now kept as the session starts. The capture name in NEXT CAPTURE NAMING is not empty anymore.
    But, if the parameter in Capture Name is modified, it won't be considered: the NEXT CAPTURE NAMING will be ALWAYS the session name.
    For example, let say we make a new session called: "WinterGoods_2010".
    By default, in the new session built-up window, the Capture Name parameter will be filled with that session name "WinterGoods_2010".
    If we change that name into "WG_SKI_HappySlide_" for example, when the session starts the NEXT CAPTURE NAMING will still be "WinterGoods_2010"!
    (i did not add the usual space that comes after by default with it, always... I know it is not a bug, but please let's get rid of it: if we want a space here, give us the choice to add it ! Thank's in advance for submitting this customer wish)


    Drew wrote:
    and that you guys talk to each other now and then
    They might talk to each other but, when you see those obvious bugs for an average user on this latest version of Capture One, you might ask too if they obviously use what ever they make ?
    And if main conversations are not just like that:
    - OK guys, ready to send the Rocket ?
    - humm, yes, not sure yet..., maybe here..., there...
    - no worries ! If monkeys disagree on distorted reflections, we'll send them free minor mirrors to enjoy captivity ! Easy, isn't it 😕
    Philippe. P. P.
    0
  • Gareth
    I've noticed a an issue that bugs me with the local adjustment layers. When you click on the plus icon for a new layer the text "Layer 1 etc" is selected as a promt to rename it. I've lost count of the number of times I press to add a new layer followed by a keyboard shortcut for brush size or the likes and the shortcut does not function and I end up with a layer called "bbbb" or "eeeee" or "[[[[[" or "]]]]]". I think you get the drift.

    Photoshop does not do this and you physically have to double click the layer name to rename it. I personally don't feel a need to always give adjustment layers specific names so I would love if C1 worked the Photoshop way.
    0
  • Drew Altdo
    Creating a new layer automatically goes into the Naming Field to identify the layer.
    Simply hit "Return" on the keyboard prior to using tool shortcuts. This is not a bug, this is by design. It is the same functionality as creating a new folder, by default the first step is naming the folder.
    0
  • Gareth
    [quote="Drew " wrote:
    Creating a new layer automatically goes into the Naming Field to identify the layer.
    Simply hit "Return" on the keyboard prior to using tool shortcuts. This is not a bug, this is by design. It is the same functionality as creating a new folder, by default the first step is naming the folder.


    Hi Drew. Yes, I know its not a bug but still annoying when most of the time I don't want to name the adjustment layer. I prefer Photoshops approach of physically clicking the name in the layer to change it rather than having to name it or always press return before hitting any keyboard shortcuts.

    Just would like a bit of continuity thats all. 😉
    0

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