max1josef
-
Posts
80 -
Joined
-
Last visited
Everything posted by max1josef
-
I don't see a limitation to 32767 pixels, when I look at the official specs: https://www.w3.org/TR/2003/REC-PNG-20031110/#11IHDR If I'm not mistaken, the permissible image dimensions are 4 294 967 296 x 4 294 967 296 pixels (2^32 for a four-byte unsigned integer). Even with four-byte signed integers, it would be far more than 32767, namely 2 147 483 647 x 2 147 483 647 pixels (2^31-1). So, where is my mistake in thinking?
-
And what's more, the warning contains a false claim! PNG files are not limited to 32767 pixels.
-
If there is such a limitation in Windows... ... why does it not apply to TIFF... ... and why does it not apply to other programs like Adobe Photoshop or GIMP? I did indeed overlook the warning. It really should be more conspicuous.
-
Please remove the image size limitation (32767 pixels) for png files! I have a 48138 px x 72518 px tiff file that I wanted to export to a png file of exactly half the size (that would be 24269 px x 36259 px). But Photo only saves a 21750 px x 32767 px file without any warning! I can't see any plausible reason for this behavior, especially because saving to a 24269 px x 36259 px TIFF works fine.
-
You have omitted a word in your statement: Most likely Inkscape's programmers decided to implement good code which Affinity programmers decided to not write. Seriously: I am not accusing affinity of deliberately writing bad code, but rather of lack of time and prioritizing other tasks. This is just a suggestion to the Affinity team to improve the "deleting nodes" issue. Nothing more and nothing less.
-
As I wrote As far as I observed, designers "fit to curve"-functionality doesn't handle sharp edges at all. ", don't you think I haven't already tried that? The problem with this is, that not only the nodes to be deleted have to be smooth, but also the neighbouring nodes, which influences the shape of the path outside the affected section (turning straight lines into curves). @Old Bruce I don't know what you're trying to say. Inkscape proves that it is possible.
-
I often have to deal with polygonal pathes, which represents curves*). Look at this comparison between Designer and Inkscape**) (there is a red copy of the line to visualise before and after): As far as I observed, designers "fit to curve"-functionality doesn't handle sharp edges at all. Am I right with this observation? Are there plans to change this? This would turn Designer from an almost perfect to a perfect map drawing tool! *) the pathes are derived from openstreetmap which has no real curves. So all curves are approximated by small straight lines which results in a large number of nodes, which I'd like to reduce. **) In case of Inkscape make sure that "Deleting nodes preserve shape" is selected in the preferences.
- 8 replies
-
- 2
-
-
- affinity designer
- node tool
- (and 3 more)
-
I didn't know about the meaning of the path field... The user interface of the export persona could take some improvements anyway: easy copy/paste of settings between slices or duplicating of slices easy inclusion/exclusion of layers per slice fix the following: if one exports only certain layers the background will always be transparent, independently of the setting in the document menu a variable for dpi (which takes the value of the Export-dpi field or the source-dpi x scale factor) fix the following: scale factor takes only "." as decimal point (no localisation to "," under German speaking environment as anywhere else) and last but not least user variables should be global to all slices. I have managed most of the above issues with templates, but any improvement to the export persona would be appreciated.
-
There is a path field in the slice properties of photo's export persona. When I enter an absolute path there, like E:\secondary_project\exports it is converted to E\secondary_project\exports i.e. th colon is omitted. When I export this slice, I am prompted for a path. If I chose e.g. E:\primary_projects\export (just confirming the prompted path) the exported file is stored at: E:\primary_projects\export\E\secondary_projects\export Saving the path without drive letter doesn't help, becaus in this case the leading backslah is omitted. "\secondary_projects\exports" becomes "secondary_projects\exports". As a workaround I save relative paths and chose root directory on export.
-
I was about to ask a similar question (I needed blend mode "darken"), but like many other questions it has already been answered by @walt.farrell. 😉
-
I would also welcome this feature. Since I use export persona a lot, it would be nice to include this feature there as well. For now, Loukash's suggestion to use Lanczos 3 (non-separable) as a resample algorithm is very helpful.
-
Wow this works really great and flawlessly! What a savings of tedious editing and time! Thank you so much, you made my day! What do I say, you have made my week, month and year! 😀👍🏆 Some years ago (didn't have Affinity at this time) I tried the same with PTGui panoram stitcher. But PTgui cannot handle images without lens information properly and produced weird distortions. Since than I didn't even think of using a panorama stitcher for this purpose.
- 9 replies
-
- 1
-
-
- rotation
- fine rotation
- (and 2 more)
-
Some here don't understand or don't want to understand my concern, instead they take the attitude, "What is useless to me must be useless to everyone else." Not a good style of discussion in my opinion.
-
See this example with only two layers. The most annoying part in designer is the scrolling through dozens of objects in te layers tree. By the way, in a real world document I would know the meaning of my layers and name them accordingely... Designer: Affinity-Forum Move-to-layer-2.mov Inkscape: Affinity-Forum Move-to-layer-3.mov
-
I just added this topic in Suggestions. So this thread can be closed.
-
I suggest an easy way to move objects from one layer to another via contxt menu: Right-Click on object Select "Move to layer" in the context menu Choose layer from list This has already been discussed here (and I myself started a thread here, which can be closed now). It could look like in Inkscape: Video.mov
- 1 reply
-
- 2
-
-
-
This thread can be closed. I posted a new thread in Suggestions. Has this topic been solved? It's about a simple way of moving an object to another layer, without having to drag it through a long list of objects in the layer's panel. Like so: Right-Click on object Select "Move to layer" in the context menu Choose layer from list See this example from Inkscape: Video.mov
-
I'm already using my workflow with success. It may sound over-accurate, but when combining images it's worth the effort. The only improvment I'm looking for is the way how to enter the rotation values. @carl123 Thanks for the suggestion, I have not thought of macros at all!
-
First of all: I mentioned the wrong program in the initial post, it's actually Photo. My workflow: I regularly scan fotos or drawings which are to small for my A4-Scanner. So I scan 2 ore more subpictures with overlap. I load the subpicture into Photo, put one into the background make the other one semi-transparent and position it correctly with regard to the background image using a distinct detail in the picture. Then I rotate the half-transparent picture in fine rotation steps. Having the background and the half-transparent image in view at the same time you can be very, very precise here. For the time being, I rotate in steps of 0,1 until I'm almost there, then add/substract manually 0,01 degree steps and after one to three retrys I'm there. Not a big deal, but would be more comfortable to be able to rotate in 0,01 degrees in the first place. PS: Auto-Rotate of scan programs does not work precisely enough, especially when there are no suitable reference lines in both subparts.
-
It is possible to increase/decrease the rotation angle of an object using the scroll wheel of your mouse when hovering over the belonging input field (in steps of 1 degree). With 'Ctrl' pressed, the increment/decrement is 0.1 degree, which is already very helpful. Question: Is there a way to get an even finer increment/decrement of 0.01 degrees? (I often have to align scanned images, where finer rotation steps would prove useful)
-
I sometimes have superscript numbers in headings, which appear as ordinary numbers in the table of contents. There is a workaround described in this this post, namely using superscript glyphs provided by the font in use. Unfortunately, most fonts have only glyphs for digits "1", "2" and "3". I suggest an option in (character) text style like "preserve this style in TOC". This would also allow, for example, partially italicised headings to appear as such in the table of contents. This is not an urgent necessity, but a nice to have option for the future.
-
I too have recurring crashes of Photo 2.1. The program all of a sudden just disappears with all not saved changes lost. Sometimes a simple click on a menu item is enough to crash the program. For instance: I often work with placed (linked) images with approx 6000x5000 Pixels, I'm adding adding a mask and a level adjustment. I save and close the file and then when I try to create a new file for the next project somewhere in the process the program crashes. My workaround is to close Photo and restart it for a new project and save frequently. I think (but I'm not sure) that the problem started after updating Photo from 2.0 to 2.1. I changed nothing else on my PC OS: Windows 10 Hardware acceleration is disabled Renderer is set to Nvidia GeForce GTX 970
-
I have "Force Pixel alignment" enabled. When I drag-and-drop a picture file (png or jpg) from explorer into a photo ducument, the file is not aligned to whole pixels. I have to release the mouse button, grab the file again and move it a little to force pixel alignment. I have "Move by whole Pixels" and "Snapping" disabled. If I had "Move by whole Pixels" enabled, the above workaround would not work, since "Move by whole Pixels" has higher priority then "Force Pixel alignment", thus moving the misaligned image by whole pixels to a new misaligned position (e.g. from 1498.2 px to 1500.2 px). There is a similar bug report on Designer 1, which seems not to be solved either: Regards Max1Josef
-
You are right! I have assigned autokey macros to replace "ää" with "ä" and so on. The macros start with backspace ... I have long forgotten about these macros in times of unicode. Sorry for the confusion 😳
-
I tried it with pixel layers and layer masks. For the time being I use "A" for increase and "<" for decrease. These shortcuts are not assigned to anything else by default and easy to type. Nevertheless it would be fine, if Serif looked over this issues. At least the non-working "["/"]"-Keys are reported by several users, namely Gonzo64, you and me (and the poster you remembered from a while ago).
