Jump to content

Cor'e =)

Members
  • Content Count

    91
  • Joined

  • Last visited

Posts posted by Cor'e =)

  1. I guess the thread got long and i'm tired, but... =)

    ...

    Our desired scenario is to take instant (but not by prolonged layer manipulations meaning "extra work") screenshots without the checkerboard. And what we wanted as a transparency BG would NEVER EVER be (that would be extremely forbidden) put in the work or file itself, so it's best to be in the application itself, if only the PDN WE use.

    Stubborn, heh... ;)
  2. Your missing the point, the checkerboard is just the way someone decided to graphically display transparency in PDN, however, we want to graphically display it another way, meaning we want to customize that checkerboard in the PDN source code or plug-in, not remove it by adding a layer. Software should remove repetitive work cycles, i'm not saying for you to do this, we could, or someone else could. But, first i wanted to ask if it was already available, since it seemed plausible to us that it was an option.

    Our desired scenario is to take instant (but not by prolonged layer manipulations meaning "extra work") screenshots without the checkerboard. And what we wanted as a transparency BG would NEVER EVER be (that would be extremely forbidden) put in the work or file itself, so it's best to be in the application itself, if only the PDN WE use.

  3. Another layer is not what we want, we do not want it part of the file and we do not want to load it as a layer every time and move it to the bottom of some 100 layers, it might get saved in the file and sent out. Plus, since we have many sizes of multi-layer images, we'd have to fiddle with canvas resize and centering etc., or perfectly pick the BG we want, that's a problem that software should solve, not humans. That's too much extra work to do, and to keep adding a layer and taking it out every time we show the image. If it was something we could select or turn on/off etc. then we'd have what we want. A checkerboard is just arbitrary anyhow and whatever design considerations it historically comes from is not written on a stone tablet, for us it'd be useful to be able to mod that BG.

  4. All points considered. We always have the Grid=On, as we manipulate the pixels mostly, each layer needs to perfectly match up, like a multi-layer jig-saw puzzle. We work with images that have about 100+ layers per image/file (we see crashes past 100 in the old version, wish we could go to ~150-200 layers).

    I'll try and test v352 on a 100+ layer mock file, i'll take some time for that. Grateful you guys care about our issues, best regards, thxs for all.

  5. A keyboard short cut, we'd like to find a way to easily increment/decrement the Wand Tool Tolerance % with either the arrow left/right or up/down, or ???, while in the Wand Tool mode and have the result immediately grow/shrink our selection region.

    Currently, it's time consuming by hand to keep mouse clicking the Tolerance and re-clicking the Wand Tool (we go to Pan to see selection) and then re-clicking our reference pixel, so it would be quite an improvement to our work flow if it existed.

  6. That's feasible, we can change from Wand(S) to Pan(h), to toggle and see both the selection and the true values, now all we need is a way to do the macros. ;)

    Update: We tried putting this back in the cycle, but we're back to square one, we cannot easily see the outline. Turns out that we've been doing this for quite some time (going between Pan etc. and Wand) in our editing & work flow, but in the older version the animated outline was very visible easy to see, now it is not. Hopefully there'll be a fix for this outline issue in the future, we'll roll-back to the previous working version until fixed.

  7. Thanks for the fix idea Sarkut, i've looked at this more as it is come to be so much of an issue here, it appears we can see the selected areas as shaded, and once it is shaded we cannot determine the original pixel values. Which is confusing us because what we want to see is the differentiation of the areas selected and not selected.

    Somehow we thought this was more intuitive in the last version, we're going to setup a test system with the older version and roll back to it if we feel it meets our needs better than this version. That'd be okay since we have not found anything v3.5 does better than the past version yet. Mostly we were hoping that v3.5 would show better memory management so it'd support more layers, functionally we see little difference, and with Rick holding back from releasing the PDN sources anytime soon we'll just stick with what can work for us.

  8. There's little need to say monitors are not calibrated, we both see the same thin faint white&blue outline pixels. But i agree with my lab users, they and I cannot easily determine what parts have been selected during the new static magic wand selection outline and it was easier for us in the previous animated version for some reason, perhaps the area bounded/highlighted was also shaded more as well, i do not recall. Differentiation between areas selected & non-selected are very hard to see/determine now. It'd be nice to be able to adjust the selection shading and coloring to suit our needs.

  9. Okay, this is sooo needed, after a large amount of layers PDN starts to glitch and choke and die... so this wonderful separate file rescues me. So thank you!

    Side notes:

    I do not see each file's thumbnail when i saved layers to the .PDN file type, therefore i feel i need to open each file to check the contents (someone mentioned layers not checked visible as not saving).

    Another quirk is that Layer Saver GUI does not close when done, and its progress bar remains full, though the Save Cancel buttons ungray themselves (So is it really done?).

    I tried drag&drop on to the program icon and it does not seem to work, but it's nice that it remembers last used directory, could it also remember its last set of configs? Is there a .ini file i can make that it can use to speed up large project chores?

    And last, since layers are so tedious moving up & down in PDN, and importing files into layers always puts it at the top of the stack rather than where one wants them, have you thought much about a tool that could create PDN files from layers?

    Or maybe a program that would sort the PDN layers by name, etc. in a large PDN file offline? That would be something i'd use.

    Thank you very much for this program! =)

×
×
  • Create New...