@feeef @Jose-Moreno @gordielachance

I have a little free time recently, maybe it a good timing to talk about 0.6 release. There are three main issues that i will focus on:

1. sound layer
2. movie exporting
3. translation

I am also going to fix the issues marked as milestone 0.6 https://github.com/pencil2d/pencil/milestones/0.6 (please tell me if I missed any urgent issues)

I plan to release 0.6.0 as soon as possible, maybe in 2~3 weeks after I solve all the major problems, and start to solve other bugs in the following small patches 0.6.x

I have already started my working yesterday, I will continuously update my progress.

Hi guys, I had to disable pencil2d.org again as my host said me the server charges were too high. I'm not sure if they say that every X month to try to make me upgrade my plan (which I can't afford) or if there is a real issue. Anyway, maybe we should buy another host for Pencil2D if you guys would agree that we buy one together. My current host is about 70 € per year. OR we shut down the website and use only Github, but that can be a problem for simple visitors who aren't used to it.

:/ :/ :/

As per discussion in #582. This script will allow automatic nightly builds to be uploaded to GDrive via CI. It requires Python 3 and the google-api-python-client Python package. (I originally tried to do it with simpler means and no additional dependencies but the amount of complexity in Google’s authorization API is honestly quite ridiculous, so I gave up.)

Obtaining the right API credentials and setting everything up is a pretty tricky too, but I’ll make a detailed guide on that tomorrow.

Ubuntu 16.04 Любая ночная сборка. При работе со слоем камеры. Если использовать одновременно сдвиг и масштаб то сохранения работают некорректно. Any night build. When working with the camera layer. If you use both the shift and the scale, then the save does not work correctly.

Hi

Looking at issue #550 made me think that instead of fixing the icons, it would be better to give the toolbar a makeover. There are lots of decisions to be made when designing icons, so instead of me just bashing pixels without any consideration in what the rest of the pencil community thinks, I've decided to share my thoughts and progress.

I've made a bunch of sketches already, mainly to figure out the placement and how the icons should be illustrated. Nothing is finalized though, so try not to think too much about the style, color or shading.

Rules i've come up with so far:

• Style should be consistent across all icons, if possible
• icons should be designed in size 24x24.
• Icons should be designed in a vector program or be convertible from raster to vector.

Iterations:

These represent the look as you would see them in the program ie. in pixels

100% scale:

I prefer the top right icon, as it is displayed in a way similar to the old icon but with more emphasis on tip.

Mockup:

I'll keep updating the thread, showing more icons as I get them done. If no one disagree or comment, then I'll just go with the design I've mentioned already (the top right).

@chchwy @gordielachance Lately I've been noticing that people are too prone to download the same old 0.5.4b version from the website, which has a plethora of bugs that have already been fixed, and some continue to report the same bugs over and over.

I wanted to propose to you that we push the latest Nightly Build as an interstitial version download, so people can at least report bugs based on the newest code base, and not the old one which is not really that stable anymore and causes multiple issues on newer systems.

This could be something like version 0.5.5 for the moment, which we know is well in it's way to version 0.6, but not quite there. This is just to avoid duplicate bug and grief reports that continue to happen due to this older version we have on display.

To "Gordie": We could change the hyperlinks on the landing page and the download page to buttons in order to differentiate "Nightly Builds" from "recommended build"

Let me know what you think, but hopefully we can do this soon.

Pencil has a issue with a lag when you use a wacom Intuos tablet pen and mac OS El Capitan.. It is the similar problem that Manga Studio ex and Artrage had. Artrage has released a new version with the tablet pen lag. When you draw with the mouse it is fine but drawing with the tablet there is a unusable lag

I have just discovered pencil and am very excited to use it, but with the pen lag it is not useable at the current time.. Hopefully some can fix it soon ... thanks Taz

This adds a bunch of additional information to the status bar in preparation for #1151 – in particular the current tool, whether the current file has been modified, the current layer and a zoom control inspired by Krita’s. Originally this work also contained a timecode, but I removed that part since it has been submitted separately in #1423 in the meantime. I can take care of the conflicts once either PR gets merged.

In addition to the status widgets I also added some basic tool help, inspired by GIMP and Blender. I hope this will help answer some of the basic questions people ask, such as “How do I rotate the view?” or “How do I move my selection?” or “How do I finish a polyline?”. Further suggestions for improvement are welcome!

(This screenshot still shows the timecode, but as I said that is not part of this PR)

Hello everyone,

I don't know if anyone noticed but the Pencil2D.org website is down. I dont know what has happened as according to google it was working today until 7 PM GMT-5

With fear of all of your effort going to waste, I decided to create a temporary free webpage, plus a forum in case we can't have our old community back. Either way i'll be maintaining that one if one day someone decides to pull the plug once and for all.

For now I'll share the forum since it's easier. I'm still creating the site to make it usable, so for now the forum will do. Give me until Nov 30th so I can share the rest, and also so I can be more active towards looking how we can improve this app and how we can find more devs.

http://pencil2d.forumotion.net/

@Jose-Moreno @scribblemaniac @CandyFace @davidlamhauge @J5lx Finally I got some time that I can work on v0.6.5 release. It's nearly a year ago that we released v0.6.4.

Just had a look at 0.6.5 milestone, there is only one issue there so I supposed Pencil2D is in a good shape to release.

I will start a quick QA session to check if anything is broken. And please let me know if anything is missing.

The release checklist:

Source code

• [x] Bump version number (common.pri)
• [x] Prepare release notes for CHANGELOG
• [x] Make sure all unit tests are working and are OK
• [x] Test all features known to work and make sure they behave the same
• [x] Update contributor list
• [x] Update meta info Meta info
• [x] Make sure 0 issues in milestone
• [x] Add release tag to the correct commit
• [x] Push to release branch

Deployment

• [x] Build and upload manually compiled versions:
  • [x] 32-bit Linux AppImage
  • [x] Legacy macOS (10.7-10.11)
  • [x] Legacy Windows (Windows XP/Vista)
• [x] Add downloads to the Bitbucket mirror
• [x] Update download links:
  • [x] Pencil2d.org
  • [x] Github README
• [x] Update packages
  • [x] Arch Linux @City-busz
  • [x] Homebrew Cask (macOS) @scribblemaniac
  • [x] Apt (Debian/Ubuntu) @mapreri
  • [x] Flatpak (Linux) @eszlari
  • [x] RPM (Fedora) @blackfile
  • [x] FreeBSD @yurivict
  • [x] KCP (KaOS) @scribblemaniac

Social media

Make an announcement with release notes (or a link to the release notes) on the following platforms:

• [x] Pencil2d.org News
• [x] Facebook
• [x] Discord
• [x] Tumblr
• [x] Transifex
• [x] Youtube?

Fixes #851. This works for me on Ubuntu 14.04.

Technical Details

The connection from the FPS spin-box is set up here:

connect(mFpsBox, spinBoxValueChanged, this, &TimeControls::fpsClick);

The Application Output tab showed a warning that the connection was not valid. I added a breakpoint to "fpsClick" and changed the FPS value, but "fpsClick" was never called.

I tried a couple of other things (from https://stackoverflow.com/questions/16794695/connecting-overloaded-signals-and-slots-in-qt-5/16795664) but couldn't get the valueChanged signal to work.

So finally I changed it so that if the "spinBoxValueChanged" connection is invalid, we use the "editingFinished" signal instead.

The bug got reported through the forum: https://discuss.pencil2d.org/t/some-new-bugs-as-of-the-nov-8-nightly-build/6777/2

How to reproduce:

1. paint a stroke on 4 frames, with the frames being 1, 2, 3, 5
2. set the scrubber on frame 4
3. Set "skin previous frames" to one

Notice that frame 2 is not painted

This had been removed unintentionally during the rework of the selection manager.

Additionally dragging along an axis should be easier without accidentally moving the selection a few pixels in the wrong direction.

And unrelated, fixed icons for some of the selection types had gone missing because of wrong path.

For this PR the goal has been to create stronger coupling between the camera tool and the painter that handled the interactive parts. This has been done by introducing a BaseTool::paint(...) method which allows us to perform calculations that can both be used by the tool and its painter without addition branching in Scribbearea. One example where we benefit from this is when calculating the centered control point instead of having to explicitly set it at various times. Another example is when calculating the distance between the rotation anchor, its line and the camera frame, as this has to be done two places, locally in the tool and in the world coordinate space.

Fixes

• Rotation anchor would not keep a fixed distance from the camera frame How to reproduce:

1. Load a project, select the camera tool and the camera layer
2. Zoom in and out, notice the distance of the rotation anchor being slightly off
3. Now increase the size of the camera frame and repeat the steps Result: The rotation anchor has been positioned further away from the frame or if decreased, position closer to the frame.

• Sometimes dragging the last control handle would drag the previous instead...

• Reworked recovery logic for splitting and merging control points

Changes

• Camera tool painter logic has been moved to camera tool
• PathCPM has been removed as its not necessary anymore

Based on my findings from when I profiled the performance issue in #1724, I changed the timeline to redraw its contents only in response to a paint event rather than every single time in updateContent() (which is triggered by all sorts of operations throughout the program) and also made the existing caching mechanism a bit more aggressive while I was at it.

Additional changes:

• Fixed an issue where the current frame border was not updated while playing
• Fixed an issue where the current frame border did not take the length of sound frames into account
• Fixed an issue that allowed frames to become selected after dragging the timeline via MMB
• Moved the timeline and related classes from core_lib to app because that’s where all the other dock widgets live
• Delayed showing the dock widgets until they have been docked to prevent them from briefly appearing in an undocked state before the main window is shown

Issue Summary

When you have moved the camera from its initial position and then switch layer to a bitmap layer and fill, the filled region does not match the new camera position.

Actual Results

Fill is happening outside the interpolated frame

Expected Results

The fill always happens within the camera passpartout.

Steps to reproduce

• Move the camera from its initial position
• Select your bitmap layer
• Select the bucket tool
• Fill on the canvas within the new passpartout.

System Information

• Pencil2D Version: Development Build Oct 24 2022 Operating System: macOS 12.6 CPU Architecture: x86_64 Qt Version: 5.15.1