4 ms·

I really wanted to like penpot, but when I tried a few months ago, simply navigating between pages (even on the example documents) was causing parts of the docu

I really wanted to like penpot, but when I tried a few months ago, simply navigating between pages (even on the example documents) was causing parts of the document to change in bizarre ways. I didn't want that level of risk with documents I actually cared about, so continued to use figma. I guess it's time to give it another shot. EDIT: still broken 8 months later :(

cirelli94 11mo ago
I think you should post a issue at this point D:
- supermatt 11mo ago
  I raised the issue in the forums at the time, with video captures demonstrating the issue(s).
  - ogrisel 11mo ago
    I think it would help to open an issue on github making explicit the following three points explicit in the report: - steps to reproduce from scratch; - what you expected to happen; - what you actually observed (include the screenshot or video capture in addition to a textual description). Otherwise, you might risk your report being ignored due to a silent misunderstanding about the mismatch between your expectations and the actual results.
    - supermatt 11mo ago
      At the time i wasn't sure if it was PEBCAK, which is why i started a discussion in the forums. As there were no replies, i received no notifications, and so I forgot all about it. If anyone is interested in opening a bug report you can see the issue here: https://imgur.com/a/hZ1ja9o https://imgur.com/a/hZ1ja9o
      - ogrisel 11mo ago
        Personally, I do not understand why you think there is a bug from this screen capture alone. Maybe because I am that familiar with penpot and figma, but still, I do not find it obvious. This is why it's important to describe explicitly the three points in text: - steps to reproduce; - what you expected to happen; - what actual result you observe instead. Something that might be obvious to you but isn't for others will just be silently ignored most of the time. EDIT: I now see the problem after reading your other reply above: https://news.ycombinator.com/item?id=46064757#46069546 https://news.ycombinator.com/item?id=46064757#46069546 This is why it's important to describe explicitly the difference between what you expected and what you observed. I swear I did not see the change in button width before reading the linked comment.
        supermatt 11mo ago
        > This is why it's important to describe explicitly That is a fair point. I will take it on board when giving people screenshots and videos of bugs in future. > I did not see the change in button width There's actually a lot more visual changes than that just the button, but I will leave that to the reader as an exercise in spot-the-difference ;)
        pixelatedindex 11mo ago
        > There's actually a lot more visual changes than that just the button, but I will leave that to the reader as an exercise in spot-the-difference ;) This is fair. But issues like this will never get my attention in general because I don’t have time to do this exercise - I would much rather have it all spelled out. Even if there are a bunch of related issues they won’t get fixed in a single PR, it likely will be multiple. I guess my point is that if you really want OSS projects to improve, the issue submitter can’t just ask the maintainer “figure it out”. It totally works this way in the corporate world though (IME). Edit: I’m sorry to have jumped to conclusions. Leaving my comment up for accountability.
        deleted 11mo ago
        [deleted]
    - IshKebab 11mo ago
      I hate how every time someone even talks about an issue with an open source project, some smart alec replies "well did you raise an issue?" - or worse - "did you send a PR to fix it?". We are all very aware how bug reporting works. And user criticism of bugs isn't somehow invalidated just because the users didn't go to the sometimes very large effort to report bugs. I wouldn't have reported this bug either. If the example documents are getting corrupted just by navigating them that indicates that it's just a really buggy project (corroborated by other comments here) that I'm not even going to use, so why would I spend my time working on it?
      - theultdev 11mo ago
        I can see both sides of the dilemma and I don't necessarily like when a maintainer defaults to "open a PR" but asking for a reproducible issue wherever requested is not too much to ask. With a PR I understand not wanting to put the effort in as it may not be merged. But offering up a reproducible example on the correct forum is the least you could do. If you want the problem fixed that's the best way forward.
        supermatt 11mo ago
        > offering up a reproducible example on the correct forum is the least you could do I suggested someone do that 8 hrs ago: https://news.ycombinator.com/item?id=46069471 https://news.ycombinator.com/item?id=46069471 So far no takers. Just people saying what they would do instead of actually doing it :)
        antonok 11mo ago
        I've done it: https://github.com/penpot/penpot/issues/7850 https://github.com/penpot/penpot/issues/7850 Thanks for sharing all the details about the issue, and shame on all the armchair critics :D
        supermatt 11mo ago
        Thank you :)
yuters 11mo ago
I've loaded an example document and do not see what you mean when navigating between pages. A problem like that should be extremely jarring and it is very hard to believe it would be ignored.
- deleted 11mo ago
  [deleted]
- supermatt 11mo ago
  > A problem like that should be extremely jarring Agreed - I don't see how its not glaringly obvious to anyone who uses the app: https://imgur.com/a/hZ1ja9o https://imgur.com/a/hZ1ja9o
  - dallen33 11mo ago
    Genuinely asking - what's the issue? I don't see it.
    - supermatt 11mo ago
      I click to navigate to the "Examples" page (I am gesturing with my mouse to circle around a bit I want you to look at). Then i navigate to "Main components", and back to "Examples" and the content in that area has changed. For example, the button has changed to half the original width.
      - morcus 11mo ago
        It's that very bottom button you're referring to, right?
        supermatt 11mo ago
        Thats the one I specifically mention, sure, but there are many more changes to the page overall if you compare the before and after.
  - 11mo ago
VerifiedReports 11mo ago
Same, but the lack of Sketch import was a deal-breaker. It shouldn't have launched without that. Has that been fixed?
Epskampie 11mo ago
Same experience here. I tried it a few months ago and even on simple use I quickly ran into so many bugs & issues I quickly gave up. I'm willing to learn a new UI, but the tool must be reliable, and it simple was not. Hopefully they've improved a lot recently?

cirelli94 11mo ago

I think you should post a issue at this point D:

supermatt 11mo ago
I raised the issue in the forums at the time, with video captures demonstrating the issue(s).
- ogrisel 11mo ago
  I think it would help to open an issue on github making explicit the following three points explicit in the report: - steps to reproduce from scratch; - what you expected to happen; - what you actually observed (include the screenshot or video capture in addition to a textual description). Otherwise, you might risk your report being ignored due to a silent misunderstanding about the mismatch between your expectations and the actual results.
  - supermatt 11mo ago
    At the time i wasn't sure if it was PEBCAK, which is why i started a discussion in the forums. As there were no replies, i received no notifications, and so I forgot all about it. If anyone is interested in opening a bug report you can see the issue here: https://imgur.com/a/hZ1ja9o https://imgur.com/a/hZ1ja9o
    - ogrisel 11mo ago
      Personally, I do not understand why you think there is a bug from this screen capture alone. Maybe because I am that familiar with penpot and figma, but still, I do not find it obvious. This is why it's important to describe explicitly the three points in text: - steps to reproduce; - what you expected to happen; - what actual result you observe instead. Something that might be obvious to you but isn't for others will just be silently ignored most of the time. EDIT: I now see the problem after reading your other reply above: https://news.ycombinator.com/item?id=46064757#46069546 https://news.ycombinator.com/item?id=46064757#46069546 This is why it's important to describe explicitly the difference between what you expected and what you observed. I swear I did not see the change in button width before reading the linked comment.
      - supermatt 11mo ago
        > This is why it's important to describe explicitly That is a fair point. I will take it on board when giving people screenshots and videos of bugs in future. > I did not see the change in button width There's actually a lot more visual changes than that just the button, but I will leave that to the reader as an exercise in spot-the-difference ;)
        pixelatedindex 11mo ago
        > There's actually a lot more visual changes than that just the button, but I will leave that to the reader as an exercise in spot-the-difference ;) This is fair. But issues like this will never get my attention in general because I don’t have time to do this exercise - I would much rather have it all spelled out. Even if there are a bunch of related issues they won’t get fixed in a single PR, it likely will be multiple. I guess my point is that if you really want OSS projects to improve, the issue submitter can’t just ask the maintainer “figure it out”. It totally works this way in the corporate world though (IME). Edit: I’m sorry to have jumped to conclusions. Leaving my comment up for accountability.
        deleted 11mo ago
        [deleted]
  - IshKebab 11mo ago
    I hate how every time someone even talks about an issue with an open source project, some smart alec replies "well did you raise an issue?" - or worse - "did you send a PR to fix it?". We are all very aware how bug reporting works. And user criticism of bugs isn't somehow invalidated just because the users didn't go to the sometimes very large effort to report bugs. I wouldn't have reported this bug either. If the example documents are getting corrupted just by navigating them that indicates that it's just a really buggy project (corroborated by other comments here) that I'm not even going to use, so why would I spend my time working on it?
    - theultdev 11mo ago
      I can see both sides of the dilemma and I don't necessarily like when a maintainer defaults to "open a PR" but asking for a reproducible issue wherever requested is not too much to ask. With a PR I understand not wanting to put the effort in as it may not be merged. But offering up a reproducible example on the correct forum is the least you could do. If you want the problem fixed that's the best way forward.
      - supermatt 11mo ago
        > offering up a reproducible example on the correct forum is the least you could do I suggested someone do that 8 hrs ago: https://news.ycombinator.com/item?id=46069471 https://news.ycombinator.com/item?id=46069471 So far no takers. Just people saying what they would do instead of actually doing it :)
        antonok 11mo ago
        I've done it: https://github.com/penpot/penpot/issues/7850 https://github.com/penpot/penpot/issues/7850 Thanks for sharing all the details about the issue, and shame on all the armchair critics :D
        supermatt 11mo ago
        Thank you :)

yuters 11mo ago

I've loaded an example document and do not see what you mean when navigating between pages. A problem like that should be extremely jarring and it is very hard to believe it would be ignored.

deleted 11mo ago
[deleted]
supermatt 11mo ago
> A problem like that should be extremely jarring Agreed - I don't see how its not glaringly obvious to anyone who uses the app: https://imgur.com/a/hZ1ja9o https://imgur.com/a/hZ1ja9o
- dallen33 11mo ago
  Genuinely asking - what's the issue? I don't see it.
  - supermatt 11mo ago
    I click to navigate to the "Examples" page (I am gesturing with my mouse to circle around a bit I want you to look at). Then i navigate to "Main components", and back to "Examples" and the content in that area has changed. For example, the button has changed to half the original width.
    - morcus 11mo ago
      It's that very bottom button you're referring to, right?
      - supermatt 11mo ago
        Thats the one I specifically mention, sure, but there are many more changes to the page overall if you compare the before and after.
- 11mo ago

VerifiedReports 11mo ago

Same, but the lack of Sketch import was a deal-breaker. It shouldn't have launched without that. Has that been fixed?

Epskampie 11mo ago

Same experience here. I tried it a few months ago and even on simple use I quickly ran into so many bugs & issues I quickly gave up. I'm willing to learn a new UI, but the tool must be reliable, and it simple was not. Hopefully they've improved a lot recently?