Thread: SVG developments

I use the Skin of Pongo and the "original" icons are from Andrey, the icons in the menus (speedwarn_normal) are 60x60....... if you enlarge them, what I showed you happens.

I was the first to say that in some files the icons are 120x120:

For example in the_skin file of Pongo the images are all max 120x120, but the ico_TomTomSpeedCam.svg file is a converted image of 512x512 (like the Ambulance), very probably if there were many other images with that size iGO would crash.

But apolyps3made a 512x512 image of an Ambulance, this image will be used for the Speedcams category for both Luna and Nextgen. The images in the speedcam_mod (speedwarn_normal) files are all 60x60, don't look elsewhere to be right, this data is indisputable.

Originally Posted by BIRBANTE

The images in the speedcam_mod (speedwarn_normal) files are all 60x60, don't look elsewhere to be right, this data is indisputable.

You are wrong.
What is there to prove? Simple work with the program, if you want to enlarge the picture, you must enlarge the canvas - window.
The picture should always be in the window. For example, the window size is 78x78, and the picture will be 77x77.
You are trying to insert a larger 78x78 image into a 60x60 window. It doesn't work like that.

Originally Posted by BIRBANTE

I use the Skin of Pongo and the "original" icons are from Andrey, the icons in the menus (speedwarn_normal) are 60x60....... if you enlarge them, what I showed you happens.

In general, for a start, you need to learn how to work with the program Adobe Illustrator. We're professionals, aren't we?

On the contrary, (almost) all are amateurs here
And that's not bad at all, otherwise this wouldn't be a free forum.

There are exceptions, professionally and for free:

Spoiler: DD

[Only registered and activated users can see links. ]


[Only registered and activated users can see links. ]


[Only registered and activated users can see links. ]


[Only registered and activated users can see links. ]

Originally Posted by Andrey Form

Of course, 100 is closer to 60 for reducing and reading by the program, and if the files are close to the original sizes, then the program will spend less time resizing the image. The question is different, I suspect that the time to reduce the picture is almost negligible.

I'm a bit confused over this discussion. Isn't SVG the acronym of "Scalable Vector Graphic"? This by design has no "resolution". As the name suggests, it contains vectors not pixels and it is scalable by definition. It may have a scaling factor as a hint how big it is meant to be when rendered to the physical world. This is usually some sort of "mm" not "pixel". Coordinate points are floating-pont, not integer. It is a matter of moving the decimal point when an image is defined as 100x100 or 1x1. The graphic is essentially the same with no loss of "resolution".

How these vectors are translated into pixels is determined by the rendering software that has knowledge about the physical resolution of the output device - in case the dimensions of "mm" should be matched at all.

If rendered on a laser printer, it might turn out as 1200 DPI or more giving a lot more pixels (and sharpness) per mm dimension than the same image rendered on an old TFT screen of 640x480 pixels.

Any software rendering VECTOR graphics into a pre defined layout space should chose to fit the image coordinates within the available space, so that no coordinate falls outside = proportional. Scaling = multiplying each coordinate with a fixed value to match image "dimension" to the actual screen space on the device. Failing to fit any SVG into a defined "icon space", I would consider as software bug.

Depending on the programmer this can be done just once and then cache the pixel map suitable for the current display, or it may be rendered on the fly, if the processor is capable enough. That's the idea of creating an SVG. You do the work just once in all detail and leave it to the rendering engine to make best use of it. Low resolution devices certainly will miss details over high resolution ones, so a good design does not depend on tiny details like tiny text that might get scaled down to just unreadable mud.

What might make a difference is how many decimals are in the file for each vector coordinate as it does affect file size and load time. With four significant digits, any "icon" should render perfectly sharp on any current or future PND display in any size.

Said that, it IS possible that an SVG can contain rasterized content, like a photo, which cannot otherwise be expressed with good results by vectors, polygons and filled shapes. But this not how SVG is thought to be used.

@kilroyj
That's right, but we are talking about svg for iGO. Let's talk about window sizes (viewBox) for icons, what window sizes were chosen by the creators of the iGO program, and if you continue to fill the program, then you should adhere to the window sizes, despite the fact that svg has no size. And so, svg has no size, but the size of the visible window is important.