Jump to content

Robert Cailliau

Members
  • Content count

    50
  • Joined

  • Last visited

Everything posted by Robert Cailliau

  1. (yes I have the latest version: 1.7.0) Create an object, say a rectangle. Set its fill to none and its stroke to pure black (rgb 0,0,0). Then try to add style from selection in the styles panel: nothing happens. Now change the stroke colour ever so slightly: e.g. rgb 0,1,0. This is so close to black as to be imperceptible, but it is NOT black. Now adding style from selection does work.
  2. JDW has a point. I've reported a number of "bugs": "a rose, by any other name, smells as sweet", so call them what you will (some bugs/features/workarounds/… usually stink.) But they do not get corrected in a new version or an update. I do not need new features: they came in avalanches in Illustrator but never the desired ones. I'm much happier with Designer than with Illustrator, and happy with Photo, except for that missing white point tool. For Designer I have reported, without reasonable response, that on a machine with two screens, a new document appears first on the second screen (where obviously I do not want it) documents do not always open in the same location and view as when they were closed the interface colours now do use my preferred highlight, but the text on the selection is not the inverse (I get white on light yellow…) the tab order in the transform panel is wrong and I just now found that adding a style from a selection does not work if the stroke colour is pure black (rgb 0,0,0) but it does work if it is even just very slightly different (e.g. rgb 0,1,0). That is a BUG. I will report those issues again on the corresponding forums and feature request lists. As to the white point request: I fully support JDW. It's not about "photoshop on the cheap". I do realise that professional users will rarely or perhaps never use this tool. However, I'm using Affinity Photo mostly for touching up scans of documents, and in those cases almost always the first thing I want to do is to get rid of the light greyish background, turning it into simple flat white (not the Australian coffee). I'll be happy with a "macro" if it does exactly that. But I get the impression from the responses that there is no easy workaround at all, and that some even find the question annoying. This is not a place for a flame-war. We are here to collaborate to find working solutions. If there is no white point tool available and there is no simple workaround, then we should simply admit that, put in a strong request in the feature requests list. Not waffle around. I'll go and do that now.
  3. And same here: this is a tool I use(d) a lot in Photoshop. It's not perfect and it's not "professional", but it is so effective and efficient: you scan a document or make a photo, the want to print it and the quickest way to get rid of the greyish parts is to use the white picker. Saves a lot of ink.
  4. Robert Cailliau

    Saving as SVG

    I use Designer exclusively for technical drawings, some of which I want to publish on the web as SVG. Here is a screenshot of a Designer drawing (it is an outline of some Lego construction): The document unit is pixels, the grid is set to whole pixel numbers and all elements are snapped to the grid and have whole pixel numbers for dimensions; they are all stroked with 1 pixel black. I expect the SVG elements to be specified in whole numbers and positioned at whole numbers in the viewbox. However… When exporting "for export" I get this in Safari: When exportine "for web" I get this: When exporting "for print" I get the same. However, the svg code is very different. For web I get: <?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> <svg width="100%" height="100%" viewBox="0 0 842 596" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" xmlns:serif="http://www.serif.com/" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:1.5;"> <g id="s-2x3" serif:id="s 2x3"> <path id="profile" d="M86.4,46.081l-15.601,0l0,4.561c1.457,1.095 2.4,2.838 2.4,4.8c0,3.311 -2.689,6 -6,6c-3.312,0 -6.001,-2.689 -6.001,-6c0,-1.962 0.943,-3.705 2.4,-4.8l0,-4.561l-15.6,0l-9.601,-7.68l57.603,0l-9.6,7.68Z" style="fill:#fff;stroke:#000;stroke-width:0.24px;"/> <circle id="r" cx="67.199" cy="55.442" r="3.84" style="fill:#fff;stroke:#000;stroke-width:0.24px;"/> <rect id="p-2x3" serif:id="p 2x3" x="38.397" y="30.72" width="57.603" height="7.68" style="fill:#fff;stroke:#000;stroke-width:0.24px;"/> </g> <rect id="p-10x2" serif:id="p 10x2" x="57.601" y="23.04" width="192.009" height="7.68" style="fill:#fff;stroke:#000;stroke-width:0.24px;"/> <rect id="p-1x2" serif:id="p 1x2" x="38.4" y="23.04" width="19.201" height="7.68" style="fill:#fff;stroke:#000;stroke-width:0.24px;"/> <g id="hand-1x2" serif:id="hand 1x2"> <rect id="p-1x21" serif:id="p 1x2" x="249.61" y="23.018" width="19.202" height="7.68" style="fill:#989595;stroke:#000;stroke-width:0.24px;"/> <path d="M281.047,30.111c-0.796,0.39 -1.69,0.609 -2.636,0.609c-2.558,0 -4.745,-1.605 -5.607,-3.862l-3.992,0l0,-3.84l3.844,0c0.735,-2.483 3.035,-4.298 5.755,-4.298c0.985,0 1.915,0.238 2.735,0.659l-0.987,1.921c-0.524,-0.268 -1.118,-0.42 -1.747,-0.42c-2.119,0 -3.84,1.721 -3.84,3.84c0,2.119 1.721,3.84 3.84,3.84c0.606,0 1.18,-0.141 1.689,-0.391l0.946,1.942Z" style="fill:#989595;stroke:#000;stroke-width:0.24px;"/> </g> </svg> which is manifestly wrong, for "export" I get: <?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> <svg width="100%" height="100%" viewBox="0 0 3508 2481" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" xmlns:serif="http://www.serif.com/" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:1.5;"> <g id="s-2x3" serif:id="s 2x3" transform="matrix(4.0002,0,0,4.0002,-3360.18,-1272.07)"> <path id="profile" d="M930,366L913.75,366L913.75,370.751C915.268,371.892 916.25,373.707 916.25,375.75C916.25,379.199 913.449,382 910,382C906.551,382 903.75,379.199 903.75,375.75C903.75,373.707 904.732,371.892 906.25,370.751L906.25,366L890,366L880,358L940,358L930,366Z" style="fill:white;stroke:black;stroke-width:0.25px;"/> <g id="r" transform="matrix(1.66866,0,0,1.33333,-512.36,-81.5833)"> <ellipse cx="852.397" cy="343" rx="2.397" ry="3" style="fill:white;stroke:black;stroke-width:0.17px;"/> </g> <g id="p-2x3" serif:id="p 2x3" transform="matrix(1,0,0,0.950075,-1.13687e-13,17.4736)"> <rect x="880" y="350" width="60" height="8.42" style="fill:white;stroke:black;stroke-width:0.26px;"/> </g> </g> <g id="p-10x2" serif:id="p 10x2" transform="matrix(32.182,0,0,2.56013,-27923.8,-757.14)"> <rect x="875.14" y="333.242" width="24.86" height="12.5" style="fill:white;stroke:black;stroke-width:0.04px;"/> </g> <g id="p-1x2" serif:id="p 1x2" transform="matrix(3.1802,0,0,2.66269,-2304.16,-844.484)"> <rect x="774.843" y="353.208" width="25.157" height="12.019" style="fill:white;stroke:black;stroke-width:0.34px;"/> </g> <g id="hand-1x2" serif:id="hand 1x2" transform="matrix(1,0,0,1,-2569.94,64.0778)"> <g id="p-1x21" serif:id="p 1x2" transform="matrix(-2.0002,1.11619e-16,2.22055e-16,4.02132,6450.26,-2670.66)"> <rect x="1380" y="672.042" width="40" height="7.958" style="fill:rgb(152,149,149);stroke:black;stroke-width:0.31px;"/> </g> <g transform="matrix(1,0,0,1,2649.99,-1164.08)"> <path d="M1090.98,1225.46C1087.66,1227.09 1083.93,1228 1080,1228C1069.34,1228 1060.22,1221.31 1056.63,1211.91L1040,1211.91L1040,1195.91L1056.02,1195.91C1059.08,1185.56 1068.66,1178 1080,1178C1084.1,1178 1087.97,1178.99 1091.39,1180.75L1087.28,1188.75C1085.09,1187.63 1082.62,1187 1080,1187C1071.17,1187 1064,1194.17 1064,1203C1064,1211.83 1071.17,1219 1080,1219C1082.53,1219 1084.91,1218.41 1087.04,1217.37L1090.98,1225.46Z" style="fill:rgb(152,149,149);stroke:black;stroke-width:1px;"/> </g> </g> </svg> which has greatly different stroke widths! And finally for "print" I get: <?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> <svg width="100%" height="100%" viewBox="0 0 3508 2481" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" xmlns:serif="http://www.serif.com/" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:1.5;"> <g id="s-2x3" serif:id="s 2x3"> <path id="profile" d="M359.998,192.005l-65.003,0l0,19.005c6.071,4.563 10,11.824 10,19.997c0,13.798 -11.202,25.001 -25.001,25.001c-13.798,0 -25.001,-11.203 -25.001,-25.001c0,-8.173 3.929,-15.434 10,-19.997l0,-19.005l-65.003,0l-40.002,-32.002l240.012,0l-40.002,32.002Z" style="fill:#fff;stroke:#000;stroke-width:1px;"/> <circle id="r" cx="279.994" cy="231.007" r="16.001" style="fill:#fff;stroke:#000;stroke-width:1px;"/> <rect id="p-2x3" serif:id="p 2x3" x="159.988" y="128.002" width="240.012" height="32.002" style="fill:#fff;stroke:#000;stroke-width:1px;"/> </g> <rect id="p-10x2" serif:id="p 10x2" x="240.004" y="96" width="800.039" height="32.002" style="fill:#fff;stroke:#000;stroke-width:1px;"/> <rect id="p-1x2" serif:id="p 1x2" x="160" y="96" width="80.004" height="32.002" style="fill:#fff;stroke:#000;stroke-width:1px;"/> <g id="hand-1x2" serif:id="hand 1x2"> <rect id="p-1x21" serif:id="p 1x2" x="1040.04" y="95.91" width="80.008" height="32" style="fill:#989595;stroke:#000;stroke-width:1px;"/> <path d="M1171.03,125.462c-3.316,1.625 -7.043,2.538 -10.981,2.538c-10.66,0 -19.771,-6.686 -23.363,-16.09l-16.633,0l0,-16l16.018,0c3.059,-10.349 12.643,-17.91 23.978,-17.91c4.104,0 7.978,0.991 11.396,2.746l-4.114,8.004c-2.184,-1.119 -4.658,-1.75 -7.278,-1.75c-8.831,0 -16,7.169 -16,16c0,8.831 7.169,16 16,16c2.525,0 4.914,-0.586 7.038,-1.63l3.939,8.092Z" style="fill:#989595;stroke:#000;stroke-width:1px;"/> </g> </svg> which has the stroke widths right, but not the positions nor the dimensions: those should all be whole numbers! What am I missing?
  5. Robert Cailliau

    Saving as SVG

    Ah! It does work satisfactorily if export for export or export for web.
  6. Robert Cailliau

    Saving as SVG

    Sorry, still cannot get it right. Must be doing something wrong. I now have Designer version 1.7.0. I create a new document (attached), with the settings as: Then I drag a rectangle from what I think is 0,0 to 100,100. The transform box too shows 100,100. When I export it as svg I get: <?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"><svg width="100%" height="100%" viewBox="0 0 240 120" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" xmlns:serif="http://www.serif.com/" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linejoin:round;stroke-miterlimit:1.41421;"><rect x="0" y="0" width="24" height="24" style="fill:#ebebeb;"/></svg> Where do the 240, 120, 24, 24 come from? At least they are round numbers now, as expected, but how does 100 get transformed to 24? Robert. PS: never mind the yellow highlights, yellow is my system highlight colour, so that is correct, but the text does not get displayed in the complementary colour which would be dark blue; I've reported that bug elsewhere. Ex1.svg.zip
  7. Just downloaded Designer 1.7. In 1.6 when I clicked a layer in the layers palette, it highlighted in the colour set in the system preferences, but in the Designer preferences a selection highlighted in blue. Now it is the inverse, but in addition the text of the selection becomes white. My highlight colour being yellow, this makes the text unreadable. See attached screenshot.
  8. Robert Cailliau

    Saving as SVG

    Hi Sean, OK. Setting to 6 decimals lets me see things better (somewhat anyway). I think I'll be able to "work around" the problems by a combination of settings and discipline. I did this (always with 6 decimals): (1) verified that the grid specifications are typed in as whole numbers. (2) created a rectangle by dragging while snapping is on. This gives the correct values in both saving "for export" and "web" svgs. (3) created a random rectangle by dragging with snapping off, then typing whole number values in the transform palette for the width and height, then switching snapping on and moving the rectangle to snap onto the grid. This gives: For Export: <?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> <svg width="100%" height="100%" viewBox="0 0 986 275" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" xmlns:serif="http://www.serif.com/" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:1.5;"> <g id="V-Main-Support" serif:id="V Main Support" transform="matrix(0.358354,0,0,0.0931325,-949.639,0)"> <rect x="2650" y="0" width="2750" height="2950" style="fill:none;"/> <g transform="matrix(2.37674,0,0,9.3998,2632.18,1030.23)"> <rect x="101.426" y="36.614" width="93.928" height="36.554" style="fill:rgb(206,199,199);stroke:black;stroke-width:3.47px;"/> </g> </g> </svg> which is complete rubbish and unusable, whereas saved for web I get: <?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"><svg width="100%" height="100%" viewBox="0 0 986 275" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" xmlns:serif="http://www.serif.com/" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:1.5;"><rect id="V-Main-Support" serif:id="V Main Support" x="0" y="0" width="985.474" height="274.741" style="fill:none;"/><rect x="80" y="128" width="80" height="32" style="fill:#cec7c7;stroke:#000;stroke-width:3px;"/></svg> which at least has the position and size correct, as well as the stroke width. So I will have to figure out how to work. Sometimes I can create elements by dragging, other times I have to type values. Thanks for your help.
  9. Robert Cailliau

    Saving as SVG

    Thanks Sean. The preferences were set to 1px. But also, my transform palette looks like this: I never see any decimals there! And, sorry, I do not quite agree: SVG does not know/should not care about dpi, which is rendering. I don't even know what "for export" might mean. It still does not explain why the values would be ever so slightly off. I type whole numbers, they should remain whole numbers. The only problem there can be is that certain of those numbers cannot be expressed in binary floating point as whole numbers after some multiplication/division that happens somewhere. Then there remains the problem that in the "for export" case the second rectangle's stroke width is completely wrong: Thanks for reporting the grid bug. While you are at it, please also report that two other "bugs" have not been addressed: (1) on multiple screens the main window opens on the screen where the palettes are, not on the screen with the main menu bar, (2) some palettes annoyingly open always in the middle of the document window, not where I left them last time, this is especially true for Photo and, for me, especially annoying for the shadow/highlights palette, but there are others. Robert.
  10. Robert Cailliau

    Saving as SVG

    Ok Sean, There were snippets in my previous post. However, to be very simple about this I've narrowed it down further. Attached an afdesign file with just the two rectangles, and three svg files called Export, Web, Print. Open them with some plain text editor (e.g. BBEdit) and you will see that they are different and contain a lot of numbers with decimals. Lastly, I wrote my own svg version, which is in Plain.svg. That has the whole numbers that I expect. And it is very simple. Using the Transform palette in Designer I also see whole numbers only. Good luck… By the way, doing this I noticed another very annoying problem: I use a grid (see attached two screenshots) with spacings that are adapted to the two Lego spacings (8mm horizontally and 9.6mm vertically). When I scroll the Designer window up and then down again, the grid has moved with respect to the drawing! The grid does not seem to be anchored to the top-left corner of the artboard. Export.svg Plain.svg Print.svg Web.svg SVGproblems.afdesign
  11. Robert Cailliau

    Saving as SVG

    Sure. Here is the whole thing. Try artboard "Main Support". Thanks a lot for the investigation and certainly for any solution. It's really irritating, because I think I'm making very simple designs with all whole numbers, and instead I get SVG with all these tons of decimals. Lego is a fairly whole-number thing… The designs are to illustrate some mathematical aspects (Pythagorean triangles) of the set 10261 But it may of course be me… CoasterTriangles.afdesign
  12. Robert Cailliau

    Geotagging in Affinity photo

    OK, found one: solmeta Does have the viewing direction included, and not just the azimuth but also the altitude angle (by how much the camera is tilted up or down). Ordered one and will let you know how its data appear in Affinity Photo.
  13. Robert Cailliau

    Geotagging in Affinity photo

    oops, this is "old" and has no replies I can spot. However, I have the same problem: my Nikon D750 has no built-in GPS. My iPhone 6s tags its photos with the location, altitude and the direction in which the photo was taken (compass bearing). The latter can be very important! The D750 GPS attachments do not give the bearing. Is there any attachment that does? Solutions that do the tagging by synchronising from a smartphone app also (as far as I know) do not give the bearing. That's not surprising since the bearing only has a meaning if the smartphone is held in the same direction as the camera. Trail recording apps record the place but not the bearing. One solution would be to fix the smartphone to the camera and make sure it records the data (position & bearing) at shutter release. Anyone?
  14. Can anyone please tell me how I get the toolbar to show in separated mode in Affinity Photo? I run: macOS Sierra 10.12.5; macbook Pro13,3, intel i7, 2.9GHz, 16GB. Two Cinema 30" displays (2560x1600 each), laptop's lid closed so its own screen is not used. I have re-installed Affinity Photo etc. but in separated mode the toolbar disappears! It drives me crazy to have to work in a single window. Separated mode works well in Designer. I suspect it may have to do with the screen coordinates at which the toolbar is drawn, i.e. it is probably off-screen somewhere, though it does not appear on the laptop's screen either if I open the lid or if I start Photo with the lid open. Help!
  15. Robert Cailliau

    Convert JPEG to JPG

    Hi, I may have reported this earlier, but I want to export as .jpeg, not .jpg. However, when I type .jpeg I get this: Why is it "forbidden" ? The "e" in jpeg stands for "expert", and the earlier Windows extensions being limited to three characters, the experts were left out… I want them back. (the answer "rename the file in the Finder" is not acceptable).
  16. Robert Cailliau

    Multiple displays

    Designer 1.5.5: I have two identical Cinema screens (2560x1600(*)) attached to my 2016 Macbook Pro (the one with USB-C sockets only). If any of the panels of Designer are placed on the second screen (e.g. Transform, Snapping, …) then opening a document or creating a new one puts the document window on the second screen. The document window should open on the screen that has the macOS menu bar. Robert. (*) I don't think the screens are relevant, but these are the old Cinema displays that have 2560x1600 pixels, NOT the more recent and smaller ones of 2560x1440 pixels)
  17. Robert Cailliau

    Multiple displays

    2018-03-28 21:22 Just downloaded the 1.6.7 version, and it's still the same: if the palettes are on the screen that does not carry the menu bar, then the new document appears on the screen with the palettes, which is NOT where I expect it and certainly not where I want it
  18. Robert Cailliau

    The file could not be opened because permission was denied.

    I have the same problem since a while. Create a new designer document, then can't save it. I have not seen this problem earlier, i.e. beginning of the year. But I don't think the number of fonts(*) is the problem: often I can save to a different folder. Sometimes I can save to the desktop but not to the folder I originally wanted. Sometimes I can save to the folder where the document sits, but doing a Save-As to a different folder does not work. It's very erratic. Robert. (*) FontBook says there are 401 fonts, but they are the ones that came with the system and most of them I have switched OFF. Some cannot be switched OFF unfortunately. The Designer font menu does not show the OFF fonts. The only font I installed in addition to the Apple ones is DejaVu.
  19. Robert Cailliau

    macros do not keep formulae

    I need to resize hundreds of photos for publishing on the web, and they come in different aspect ratios, portrait/landscape and from different cameras. I created a macro from Document→Resize Document… , checked Resample, opened the padlock, and typed the formula /2 (divide the number of pixels by 2) in both the width and height fields. That should reduce the image to a quarter of the pixels. But no: it calculates the half width and height of the current image, remembers those values and then applies them to any image it is told to work on! And therefore also the macro canot be applied twice: it does not reduce by half, it reduces to a fixed value which is the same the second time. (1) it would be excellent if the formula would be stored in the macro instead of the result on a particular image (2) is there another way to do it that I have overlooked? (obviously I could first sort the photos into all the portrait ones from a specific camera, then all the landscape ones, and so on for each camera, but then I might as well do it by hand!) (3) is there a way to see what a macro step does? It seems impossible to see what an "atomic" step such as resize document has actually recorded.
  20. Robert Cailliau

    macros do not keep formulae

    Ah, well… owenr, Now you've just provoked me into my usual rant about "computer science". The best way to know the details is to look in the code. There should be no such thing as experiments: the algorithm was written by someone and that someone has the answer. However, as with all commercial software, that is usually not openly available. The best thing would be for someone from Affinity/Serif to tell us what it is and what the purpose is. Agreed that I myself did an experiment, and also agreed that yours show circumstances under which the result is what I was "afraid" of. The next step should be to get Affinity/Serif to do something about it. At this late hour of the day (23:26) I can only think of three proposals: (1) either put a well-defined resampling algorithm into the equation transform, but that should probably NOT be done, (various good reasons) (2) provide a sensible way to reduce image sizes while keeping aspect, (3) keep the formulae specification in the macros. The ball is in their camp now.
  21. Robert Cailliau

    macros do not keep formulae

    Hmmm... There clearly is a resampling algorithm at work, just as in the case of carl123's dragging the corner handle, but we don't know what it is or how to control it. It would be good to have that settable in the preferences. The preferences have a lot that I'd like to add, e.g. a way to say how large I want the default size of a new window.
  22. Robert Cailliau

    macros do not keep formulae

    carl123: (and owenr) What goes on is that the x*2 and y*2 push the image into a quarter of the space, upper-left of the canvas, but does not change the canvas, i.e. that keeps its number of pixels. The canvas clip then removes the empty pixels. I don't yet understand why x*2 halves: I would have thought that a pixel at x,y would now go to x*2,y*2, but it is probably this way around: f(x)=x*2 means that at position x will now be displayed the pixel that was on x*2 in the original picture. Anyway, there is also resampling: obviously I immediately tried x*2 on this image with 1 pixel wide black lines inserted: and then got this: Also, since the equation macro obvioulsy does have to keep the equation, I can apply it more than once if needed. So that does what I want. But what a way to do it! Thanks for the distort tip. (btw, in computing there is a lot of bad use of the word "filter": a filter's primary purpose is to remove something, usually from a liquid or a gas. Many of the effects listed in the filters menu are actually transformations. This bad use is much more pronounced in computer programming. I'm not even going to go into the semantic abuse of definition and resolution, where resolution has replaced definition and "pixel density" has then been invented to mean resolution)
  23. Robert Cailliau

    macros do not keep formulae

    That seems to work. There must be something going on, even if not a resamplig, because the size of the file in bytes is certainly reduced, and the number of pixels too. However, I would never have thought of looking in "distort"! I'll try and report results.
  24. Robert Cailliau

    macros do not keep formulae

    Thanks Sean P. I did the right-click thing before, but nothing at all happens. (I get the choices delete/rename/edit, but edit has no effect whatever) Unless I'm mistaken, Photoshop did allow correct resizing. But CS6 no longer works on Sierra. Keeping the formula surely is not a big deal, and would be so much more powerful. I will try your batch dialog suggestion.
  25. Robert Cailliau

    Toolbar disappears in Affinity Photo separated mode

    Worked! Thanks! I confess some of my own programs showed this problem of having windows unreachable off-screen after attaching or detaching external displays. They have been changed so that at launch they move any window whose top-left corner happens not to be on a connected screen onto such a screen. OK, an easy bug to correct then. Thanks for the tip. PS: it's not easy to launch with the control key down, as that brings up a contextual menu from which one has to choose "Open".
×

Important Information

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.