Hacker Newsnew | past | comments | ask | show | jobs | submit | yeko's commentslogin

This kind of thing always feels too slow to use. Every time I open my trace in it, it always lags and requires a few seconds to zoom in or zoom out.


Please file bugs against us at https://github.com/google/perfetto/issues! We're always very interested in seeing traces which are hitting performance issues. We take them seriously and are responsive at fixing them (or at least explaining what makes it hard to fix).

As I note in the post, we optimize for the needs of Android/Chrome developers so we may not necessarily know about whatever condition you are hitting with your trace!


The long press does not work on the Android mobile app, although it does work on the web page.


Sometimes it is not possible due to bugs in browsers.

For example, how do you know if calling a API will crash the browser?

https://bugs.chromium.org/p/chromium/issues/detail?id=118336...


In that case you use that API whenever you can so that browser gets fixed ASAP.


Yeah, and that browser update is controlled by IT and they manage the CEOs laptop and you'll be fired if the site doesn't work on their laptop.


There is unofficial open source driver for tablet from these brands.

https://github.com/OpenTabletDriver/OpenTabletDriver


Awesome. Just replaced official drivers with it, and it solved an issue I had with my Wacom on KiCad!


However, the restriction only apply to asop/pixel devices. For other devices, often there is a way to extract unique id/ imei with hidden api without any premissions.


> I was able to open a .ai file,

Actually it doesn't, Affinity open the embbded pdf in Ai file, some metadata like textframe/alignment does not exist in pdf.


Good to know, this probably explained why the notionally transparent artwork was imported with a white background. But the fact that it’s not a true .ai import I don't think this is ever going to be a concern to me because I never use SVG to typeset flowing blocks of text. The main things I'm concerned about are:

1) Path and style integrity

2) Artboard dimensional integrity

3) Export file quality

In my testing, I was able to open a file I had edited and saved in Illustrator, export it as an SVG, it was an utterly pixel-perfect drop-in replacement for a previously exported SVG. I was also able to confirm that all of the SVG files I care about can be opened directly, edited and exported with no errors. That's enough for me to confidently say goodbye to Illustrator forever. It's robust enough that I know I can deal with the occasional import glitch if it ever does happen.


There are some really annoying things about Designer, though - like how it insists on rasterizing Gaussian blurs, even though SVG supports them as a vector operation...


affinity artboard support is newish, and not great. you may want to deep dive into it to be sure their implementation is good for you


Yes, I did. My files are simple. Around 15 or so assets. One file per asset, no elaborate effects used.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: