5 - How does one add such bitmap textures to be seen and used within Inkscape so they are accessible upon start-up of Inkscape? How does one place then into a specific category? Can additional category names or sub-groups be created or named?
What is the proper path in which to access them within the Inkscape folder system (structure)?
6 - Any suggested limitations or pitfalls to avoid in creating such bitmaps or patterns? Any shortcuts for efficiency?
Including "file bloat" or huge size increase when exporting files (such as PNGs) from created Inkscape work?
I know these questions cover some diverse ground here. But I think the answers to these questions would help users better understand and utilize this capability within Inkscape.
Thank you for adding your specifics and directions and insights.
Hi, Tyler. I dove in snd tried some things out myself.
I am not focusing on filters just using bitmaos.
I have found that one can import bitmaps, grayscale or color. Any size, no color limits. They can be created outside of Inkscape or within the program and still used easily and quickly to form patterns.
Other than saving them within the document itself, is there a way to save these patterns in Inkscape folder structure so that they are accessible when Inkscape is re-started?
Can they be placed in Category names that I create and be accessed from the menu when using the fill with Patterns? If so, how?
Hi. I am using the 1.3 Alpha version on Windows 10.
Regarding the use and creation of Patterns in this version:
I assume a user can create their own patterns ... specifically from bitmaps ... as seen in a few patterns under the Texture category.
1 - Do the source bitmap used for such patterns have to be grayscale only, or can they include colors?
Are there any color limits such as 256 colors?
2 - for such bitmaps, what is the recommended filetype? PNG, BMP, JPG, other?
3 - recommended dimensions used on such bitmaps ... width and height?
4 - recommended dpi settings? 300? 600? 150? Other?
5 - How does one add such bitmap textures to be seen and used within Inkscape so they are accessible upon start-up of Inkscape? How does one place then into a specific category? Can additional category names or sub-groups be created or named?
What is the proper path in which to access them within the Inkscape folder system (structure)?
6 - Any suggested limitations or pitfalls to avoid in creating such bitmaps or patterns? Any shortcuts for efficiency?
Including "file bloat" or huge size increase when exporting files (such as PNGs) from created Inkscape work?
I know these questions cover some diverse ground here. But I think the answers to these questions would help users better understand and utilize this capability within Inkscape.
Thank you for adding your specifics and directions and insights.
Have a great day.
It's not clear to me if the question concerns creating textures in the Filter Editor, or creating custom patterns in the paint servers.
Hi, Tyler. I dove in snd tried some things out myself.
I am not focusing on filters just using bitmaos.
I have found that one can import bitmaps, grayscale or color. Any size, no color limits. They can be created outside of Inkscape or within the program and still used easily and quickly to form patterns.
Other than saving them within the document itself, is there a way to save these patterns in Inkscape folder structure so that they are accessible when Inkscape is re-started?
Can they be placed in Category names that I create and be accessed from the menu when using the fill with Patterns? If so, how?
Thank you for your help.
1. Colors are acceptable.
2. Any filetype should be ok, I prefer png.
3. & 4. I would base size on the use-case... big enough to look ok if scaled.
5. I would make the patterns in collections, each collection in a single SVG. Sub-categories, I don't know.
5a. Preferences>System can open the user paint-server directory where the pattern file can be placed for persistent use across documents.
6. I'd only make pattern images as big as they need to be.
Thank you, Tyler, for these ideas.