Jump to content

Nickkk

Members
  • Content count

    45
  • Joined

  • Last visited


Reputation Activity

  1. Like
    Nickkk got a reaction from Alfred in Dismissing popover first clears shadow and then closes popover   
    I will appeal to the "it does not work correctly" part.
    Generally, I would rather call a bug something that does not work as expected (also see Wikipedia). By your definition, if the toolbar rearranged all its buttons randomly every time you clicked one of them, that would not be a bug, but I think most people would agree it is.
    A shadow that disappears 1 frame earlier that its object might sound like a tiny thing, but for those who are sensitive to these kind of things it is distracting.
    Now let's assume we have the reversed situation, i.e. the shadow stayed on screen 1 frame longer than its object. You probably wouldn't call this a bug either. But then, if the shadow stayed visible for a whole minute after the object disappeared, you probably should, because the user couldn't tell if the shadow is on the canvas or not. Since I think we can agree that we cannot define the number of frames until which the shadow not disappearing is considered a bug or not, the original case should also be considered a bug.
  2. Thanks
    Nickkk reacted to Alfred in Dismissing popover first clears shadow and then closes popover   
    Déjà vu all over again!! 
     
  3. Like
    Nickkk got a reaction from Alfred in [By Design] Undoing first stroke in pixel persona should remove automatically added layer   
    I would love to hear why someone would want to keep that automatically created layer when undoing the first stroke. It would help me understand why you think this is a feature rather than a bug.
  4. Like
    Nickkk got a reaction from Alfred in [By Design] Undoing first stroke in pixel persona should remove automatically added layer   
    Thanks for supporting me. I also find that there are several inconsistencies which seem to be dismissed because they are by design, without thinking through how a user perceives this design. As a user, I would expect that undoing a stroke would restore the previous state, which does not include that automatically created layer. Those two history items should be merged into one.
  5. Like
    Nickkk got a reaction from Alfred in [By Design] Undoing first stroke in pixel persona should remove automatically added layer   
    I would appreciate feedback on my thoughts from the moderators. It seems that at least 2 people think this behaviour is confusing.
  6. Like
    Nickkk got a reaction from Alfred in [By Design] Undoing first stroke in pixel persona should remove automatically added layer   
    Thanks for supporting me. I also find that there are several inconsistencies which seem to be dismissed because they are by design, without thinking through how a user perceives this design. As a user, I would expect that undoing a stroke would restore the previous state, which does not include that automatically created layer. Those two history items should be merged into one.
  7. Like
    Nickkk got a reaction from Aammppaa in [By Design] Undoing first stroke in pixel persona should remove automatically added layer   
    If one starts with a vector graphic and then adds some strokes in the pixel persona, undoing those strokes leaves an empty layer behind that was automatically created with the first pixel stroke. An additional undo removes this layer, but it should be automatically removed when undoing the first stroke. Each undo should correspond to one user action.
  8. Like
    Nickkk got a reaction from Alfred in [By Design] Undoing first stroke in pixel persona should remove automatically added layer   
    Thanks for supporting me. I also find that there are several inconsistencies which seem to be dismissed because they are by design, without thinking through how a user perceives this design. As a user, I would expect that undoing a stroke would restore the previous state, which does not include that automatically created layer. Those two history items should be merged into one.
  9. Like
    Nickkk got a reaction from Alfred in Dashes line type is selectable with custom width   
    When a stroke has a custom width controlled by pressure points, the dashed type has no effect. If this is intended, then it should not be possible to select the dashed type in this circumstance or a warning should be displayed, otherwise one keeps wondering why nothing changes.
    IMG_0025.TRIM.MOV
×

Important Information

These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.