Jump to content

Hexcede

Newbies
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thank you for the information! Some kind of export/save a copy feature definitely does sound like a good alternative. I've struggled before with synchronous code and it's especially annoying to handle a bunch of threads with little interaction. (That's one reason why I've switched to node.js for a lot of my web design and scripting because of Promises). I'm not sure how or if you've even decided on how this would work, but at least for my case I tend to keep my pdn and png files the same name so being able to quickly save a pdn file to a png through the use of a keybind would be an awesome imp
  2. It's particularly slow on my machine then. I measured ~5 seconds mostly due to the time it takes to save the file/unflatten/flatten. I am not on a low end PC either. Here are my specs: Windows 10 64 bit 3.25 GHz (Overclocked to 3.75 GHz) AMD Ryzen 3 2200G 4.0 GB of RAM (I know it's not that much haha) Two identical SPCC SSDs (I get good write/read speeds usually and saving a small image file wouldn't take that long). An NVIDIA GeForce GT 730 (This card isn't that terrible. I am able to get FPS in the 80s and 90s in a lot of modern 3D games, for example Minecraft. I don't have p
  3. Time and time again my progress is slowed down by the way png saving works in PDN. I often work in files with many layers. When I save my layered files to png (or other) files I always get the "flatten" popup as well as the save dialogue and then I must unflatten the image which massively mucks up my workflow. I don't know why this prompt exists still but it honestly annoys the hell out of me and it takes several seconds extra to save my images when it could be much quicker. This is especially bad when I am making small tweaks to my files in quick succession. I save my files a lot and a lot of
×
×
  • Create New...