pastthepixels / freepaint Goto Github PK

Device: Pixel 6
Android version: GrapheneOS, Android 13

Background:

This is something I noticed after adding FreePaint to F-Droid (aargh!). It's something I didn't notice during testing of 1.0, and since I barely changed anything in the codebase between 1.0 and 1.0.1 it might be an error introduced by Android/GrapheneOS. Still worth looking into.

I don't want to release a fix right as soon as the app got on F-Droid, but I believe this is still quite critical, especially for new users who may think the program will never work.

What's happening:

When you open the app for the first time, you can draw paths. They just won't be visible! Save your "invisible" drawing as a .svg and open it, and you'll find you have drawn paths with the regular settings. Once you start the app and open the settings menu, even if you don't change any settings, you will draw paths with the default settings again. This fix will persist across app restarts.

My best guess is that when you're opening the app for the first time, you have no settings config stored and FreePaint looks for the default settings when calls are made to load settings (argument 2 of the function to read settings, in Java). However, something is bugging out which is setting all default settings to some kind of null value. When you open the settings menu, Android (could be) updating your settings based on the default values in preferences.xml.

I'm not an F-Droid developer/maintainer so I can't say for sure if the program can't build, or even if it's a problem with FreePaint, but I'm opening this issue anyway because it very likely is.

#14 suggests that it's an issue arising from the fact that I lost my old key, decided it was for debugging anyway, and signed 1.1.0 with a new key. Apparently best practice states that you should provide a version of a previous release with the new key (or current release with the old key), but ultimately F-Droid maintainers have to do some work to allow new builds to be checked against the new key.

I've provided a version of 1.0.2 with the new key to make things easier, but I'm leaving this up because there might have been something I have forgotten that's causing the app to still not build.

I just opened svg, and that looks like that ->

My app is opening it as expected ->

• I have given my bug report a descriptive title, beginning with "[Bug]" and ending with the version code for FreePaint in brackets.
• My issue describes only one bug, and does not contain multiple bugs or feature requests.
• I have attached all assets to be able to reproduce this bug.
• (if available): This bug is reproducable on a virtual machine or device running stock Android.

Description:
When I erase a line, and then touch once, the app crashes.

Device:

• OS/version: Oxygen OS (Android 13)
• Device: OnePlus Nord CE 3

While testing the previous issue i zoomed the scene out, and after app restart i can't zoom it in even for two pixels

Describe the bug
Latest release (v1.2.0) build does not contain the necessary libraries for other architectures.

To Reproduce
Steps to reproduce the behavior:

1. Download latest release
2. Install it on a device not running on ARMv8
3. Observe failure

Expected behavior
Installation not failing. Necessary libraries are included for other architectures in the build.

Device (please complete the following information):

• OS/version: One UI 6.0
• Device: Samsung Galaxy A13
• Version: Android 14

I don't want to always save params when the app closes permanently, it would be good to add some switch of selecting that🐸

You updated the version code but the apk still has version code 3 so that it's not reproducible. Please also update it, thanks!

1. App crashes when double tapping while using paint brush and eraser.

2. When using the eraser, instead of creating a closed path to erase the entire segment, I want an option to use a normal eraser to erase specified amount of the line based on where I slide on it.

Device

• OS/version: Oxygen OS (Android 13)
• Device: OnePlus Nord CE 3

Hiho, as your app is available on F-Droid.org now for about 2 weeks, I'd usually remove it from IzzyOnDroid – but I see your Readme still links here. Does that mean I shall keep it here as well?

ref: https://gitlab.com/fdroid/fdroiddata/-/jobs/6831284308#L902

as https://github.com/pastthepixels/FreePaint/releases/tag/v1.2.0 is tagged to f2bf6a0

but APK is built from 4ed875a

but besides that (and please in the future always build from the tagged commit or at least remove vcsinfo: https://f-droid.org/docs/Reproducible_Builds/#vcs-info) diff log says you've built your APK with Java 21 (https://f-droid.org/docs/Reproducible_Builds/#mismatched-toolchains) right?

diff: freep5.log

/LE: fyi https://gitlab.com/fdroid/fdroiddata/-/commit/cf1900e6e961e31f8dd5746c42327476df36c70b

Is your feature request related to a problem? Please describe.
No.

Describe the solution you'd like
When a tool is selected, it doesn't change in the tool menu. The Paintbrush will always visually appear selected because it's hard-coded.

Additional context
I would like to make this dynamic.

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
Having multiple types of brushes

Additional context
For my study i need to work on an open source project. I found your project and would like to contribute.

When i change between paint and eraser this one happens

Is your feature request related to a problem? Please describe.
Changing color of the pen is hard.

Describe the solution you'd like
Instead of the change color of the pen from setting menu, I would like to change it in the top bar without going to the settings.

Describe alternatives you've considered
Putting color settings to top bar can be a easier and nicer for most users.

Thank you.

Is your feature request related to a problem? Please describe. I sometimes work with .wmf (Windows Metafile) files. Currently, there is no Android app able to open .wmf files directly. I'm always frustrated when I need to use multiple applications to convert these files before I can use them in your vector drawing app. I would appreciate the addition of a feature that allows for the direct opening and editing of .wmf files within the app. This would greatly streamline the process, making it more convenient to work with a variety of file formats, especially for users dealing with legacy graphics or those in specific professional fields like mine.

Describe alternatives you've considered An alternative solution could be the implementation of a conversion tool within the app that converts .wmf files to SVG format. While this is not as seamless as direct opening and editing, it would still improve the current need to use external software for conversion.Additional context Adding .wmf support would enhance the app's utility for professionals who frequently deal with a mix of modern and legacy file formats, broadening the app's appeal and user base. Thank you for considering this feature request. Your app has been incredibly useful, and this feature would make it even more valuable to users like myself.

It would be nice to be able to export the image to PNG. SVG is great to use for drawing but it's not as good for sharing with others. Being able to export to PNG would really help with that.

I love how simple it is and the UI updates you showed in another issue will make it really useful for simple drawings.

Thanks for your help!

When using the eraser, instead of creating a closed path to erase the entire segment, I want an option to use a normal eraser to erase specified amount of the line based on where I slide on it.