EMHmark7

Thanks for reply. But Win says access denied to that folder and I cannot rename it.

I updated my Designer to last version 1.8.5 and setup failed with this message: The installer has insufficient priviledges to access this directory: C (maybe location is more specific than C, but I cannot see more, maybe because of Affinity dialog box size) I am with main user login. Any idea why and how to fix it? Thanks.

But it would be multiplatform (if done in Webassembly) (maybe now they are programming in 2 or 3). And maybe it would even be more reliable because memory management, although I do not know memory usage limitations in a browser.

Hi, as in my old Macromedia Fireworks, is there a tool in Afinity to set the best smallest file without loosing quality? Right now, I have a 1200x1600 picture with trees and leaves details. I want to maintain the quality of the image but reduce its size (pixels and kB). So far, I did it with several tests export and look at. But the file is still big, even if I change the size, and it is difficult to maintain quality. IS there a way to optimize it or to immediately see changes before export? Thanks Marc

My most powerful CPU is on windows 8. My fear is that someday, I will need to upgrade my OS to followUp with Affinity. I am afraid about MS business model about private data. I feel it's a big open backdoor. We do not know anymore what we get when we Get Win or Ggle OS.

But, why not program Affinity in a multi-platform low level compiled language such as Web Assembly (Rust for FireFox) or other new languages that we begin to hear about (I do not remember the names) that will be reliable because they will take care of memory allocation, etc?

My intention was not to shout, but put emphasis on the point. (I was forgetting how it can be interpreted in a chat). Sorry. If I may add to the thread: I read somewhere that even if we disable data collection, it reenable itself after a while or after updates. Bottom of the line, MS allows itself to collect data, so maybe it means it can reenable this feature at will. Also, another reason to go away from Win, is its business model, especialy for updates and upgrades in the mid-long term ($), and putting pressure on making good computers not fit anymore for usage. In long run, Cost of ownership is expensive just for maintaining the OS running. When we spend $ on OS upgrade, we normally do not have new useful features for the money.

As a matter of fact, quoting EMH mark2 : "Please state the nature of the (medical) emergency." Now we are at a step where we are looking for or start to build solutions, not just ask. That is maybe why some people in the OpenSource are feeding Photoshop like projects, and others are thying to figure out how to make money programming OpenSource. But when there is an available software that is evolving rapidly and costs not much, the solution is there. I am asking: If a proprietary model serves well, how could we welcome it and feed it, so programmers can concentrate on other problems to solve? Such as dump the nonsense and welcome the making sense.

As matter of fact, I do not have a cell phone. But it is not normal an OS can record all what is entering your mic or keyboard, including passwords. I know, even Sky pe and Face bK are problems, but the solution is that some people are beginning to look for alternate means. They give up, they are feed up, they say no more, and look for changes.

I think, not only businesses but also endusers are ready to pay whatever fair price, especially low, for a software that they appreciate and use. Not necessarily yearly xxx$, but definitly xx$ yearly. Another strong decision maker is that we are fedup of MS open door for spying our data and expensive updates. WE WANT TO BREAK FREE FROM THAT NONSENSE ASAP, ASAP.

Here are examples of perspective corrections (more important that the actual Affinity tutorial on perspective correction) http://www.dxo.com/us/photography/photo-software/dxo-viewpoint/features

1) 16 bit color depth driver for color printers (such as the Canon iPf8400 print plugin for Photoshop) Qimage Ultimate (software) seems to have such feature. You could maybe incorporate their technology. Such feature is the only feature that gives me a remain of interest in Photoshop. 2) Qimage software says also it can crunch big files and feed the printer with smaller chunks so we do not care about the printer memory limit, allowing long prints and can get deep high resolution (closer to native printer resolution of 1200dpi) 3) Unclog feature: By the way, I purchased Qimage because its unclog feature that prints daily patterns (I choose the frequency) so my printheads never do deep cleanup wasting a lot of ink. (It prints automatically, paper is already in the printer) I wish I could have an automated email when everything got ok, so I know if there was a power outage or other problem that needs intervention for keeping the printer being used a bit daily. 4) Perspective correction (such as from DXO ViewPoint software) Integration with Focus Stacking software such as Zerene Stacker 5) (whatever the stacking software), it would be good tho have a workflow easing the way we can manage many images to build the single image, and no need to work directly with file folders that show let's say 100 images of the same shut, 200 of another, etc. but just one image of each sequence (and get a behind the scene link to the image set in a specific folder if we wish to regenerate the composite image, or be able to delete such folder behind the scene and keep only the resulting image. But anyway, some photo editing should be performed on the whole set, while other editings would be done on the composite image. A best practice workflow should be defined (what should be done on the whole set, and what should be done on the composite image) 6) Lense correction: it would be interesting to be able to take standardized shuts of a white frame with horizontal and vertical black lines, with the actual lense, tube extenders and distance of the object (macro photo, short distance), so, may have a version for macro photo and one for normal shuts. These shuts would show the actual lense distorsion we want to remove and the software would compute a correction filter that we could apply on other photos. 7) Image stitching from several parts (not necessarily from a panorama shut) 8) Large Image tiling on whatever size, such as letter size.