Jump to content


  • Content Count

  • Joined

  • Last visited

About voidsea

  • Rank

Recent Profile Visitors

676 profile views
  1. In my projects, I'm largely relying on CIELAB colors. But the LAB sliders alone are really hard to scroll along Hue. Then I found this variant of LAB: HSLuv. It would greatly save my time dealing with CIELAB colors. Details and sample implementations can be found at http://www.hsluv.org/
  2. I've encountered the same problem when working with symbols. I just have some cropped bitmap inside the symbol. And upon copying/duplicating with CTRL+Drag or ALT+Drag, the bitmaps disappear at random and the symbol bounding box is extended to artboard size. EDIT: After checking the layers, I found the missing bitmaps are all there but with a wrong mask size and location. I have to resize and edit the mask to get them back.
  3. I have about 300 slices in the list. After clicking on the Expand Arrow of a slice or clicking on the Add button under an export set, the list will jump back up, and I have to scroll down again to find the right slice. Please check the attached GIF for a demo. (You may need to click on the image then "Full Size" on the bottom-left to play the animation.)
  4. And one more thing... Showing slices as a layer enables me using slices a a bounding box guide whiling editing icons. I don't want to manage another extra grid layer for this. Currently I have to switching a lot between personas, and every switch takes time due to the mode change.
  5. But I can't set margin spaces for the auto-following slices, and the pixel alignment would be wrong on some of my drawing (because of the sub-pixel placement on the top & left most borders). To the concern of a bloated UI, personas can be predefined as tool layouts. It should not block me from accessing whatever features right at my hand via shortcuts. *AT LEAST TAKE A LOOK AT ADOBE ILLUSTRATOR* And what make a software hard to learn is hiding everything in a box. (Like hiding "export slices" in the export persona's slices panel. DOUBLE BOXING) The biggest problem with this MAN-MADE persona blockage is I will (almost always) forget which persona I'm in when focused on my work. And I will not recommend AD to my friend or buy a upgrade on the future as long as this time-wasting problem persists. Since the refund period has expired, I'll go along with whatever it is now. Though the personas workflow suits AP well.
  6. When would us be able to copy/paste slices and reorder the slices in the panel? And I would like to move slices alone with drawing objects, since I have to reorganize the canvas frequently. Move the objects and realign all those slices is a pain. Merging the three personas into one just like Adobe Fireworks will be a great help. Slices can just be placed inside a layer. And the only different between vector & pixel personas is the content of the Tools bar. It wasted lots of my time on switching those stupid personas.
  7. I was moving slices or objects after a ctrl+s save in Pixel Preview mode. Sorry I don't remember exactly what I was doing after a sleepless night. One thing worth noting is I applied outer glow affect to a whole layer which contains at least 1000 objects.
  8. Crash info: Faulting application name: Designer.exe, version:, time stamp: 0x58414e28 Faulting module name: d3d9.dll, version: 10.0.14965.1001, time stamp: 0x581d54f2 Exception code: 0xc0000005 Fault offset: 0x000000000000d93e Faulting process id: 0x1dd4 Faulting application start time: 0x01d2550f91f2378d Faulting application path: C:\Program Files\Affinity\Affinity Designer\Designer.exe Faulting module path: C:\WINDOWS\SYSTEM32\d3d9.dll Report Id: 29b3dbf6-676f-45b8-ae20-6314ac7f7e5c And I didn't find the log for the blue screen.
  9. (Surely a good method to encourage more users buying Affinity Photo)
  10. Major bug fix is also a major release. ;) My company uses 1.X mostly to encourage users to update.
  11. And JS+HTML/CSS is far more flexible to build a good cross-platform experience. PyQt is ugly, yes, simply ugly. Though the python lib is smaller to include, the performance might be the same. (No intention to start a war with zealots) Actually Node.JS(V8) performance is even better than the PyPy in my company's use cases. What I can't give up is the Python scientific libs my project depends on. But those ugly __***__ and more in the code, well, as long as it works, the end users won't care.
  12. The release policy in my company is a repeat cycle of one New Feature release and two or more (up to five as I remembered) Maintenance releases. (Since there are always more bugs to be fixed than the urge of new features ;) ) Not should if Serif uses the same strategy.
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.