Drawpile 2.0.2 Release

March 27, 2017

Version 2.0.2 is now out. This release fixes the bug that would lock up the application when a session was reset, and many other bugs. It also adds a new logo contributed by Leandro Pacheco. In many ways, this is the release version 2.0.0 should have been.

Changes in this version include:

  • Fixed returning from fullscreen mode to maximized window
  • Fixed server crash when terminating an announced session
  • Restored missing "lock dock positions" feature
  • Messages received during reset while session history is full are now dropped (mitigates auto-reset loop of death)
  • Fixed layer selection after current layer is deleted
  • Separated layer delete & merge menu items
  • Various session template related fixes
  • Session history size is now displayed in the status bar
  • Fixed lockup on reset when navigator was visible
  • Reset no longer clears pinned chat message
  • Fixed "hide from self" layer menu item
  • Fixed selection moving when selection is partially (or completely) outside the canvas
  • Fixed Windows XP and Vista compatibility (32 bit version)

Read more...

Drawpile 1.0.1 Bugfix Release

March 20, 2017

Due to some critical bugs discovered in version 2.0.0, version 2.0.1 is now released a little ahead of schedule.

Changes in this version include:

  • Brush crosshair cursor restored (configurable: activate it from the preferences dialog)
  • Session announcement list error messages are now shown properly
  • New feature: timestamps can now be automatically added to recordings
  • Fixed frequent canvas rollbacks when many people were drawing simultaneously (stroke would disappear, then reappear)
  • Moderator accounts now get OP status correctly (regression fix)
  • Fixed exclusive layer locking
  • Fixed restoring session & layer ACLs after a reset
  • Fixed cut&paste and annotation locking
  • Progress bar is now shown during session reset
  • Fixed missing username in "op granted/revoked" chat messages
  • Fixed duplicate local messages when sending reset snapshot
  • Fixed max session count and session size limit settings in server GUI

Read more...

Drawpile 2.0 stable release

March 18, 2017

The 2.0.0 stable release is finally here! Version 2.0 has finally reached the level of quality where I feel it is ready to replace version 1.0.6 as the official stable release.

Version 2.0 is unfortunately incompatible with 1.x versions. For this reason, version 1.0.6 is still available on the download page as a ZIP package (Windows) that does not require installation, so that it can be used in parallel with the new version.

The public server will be switched over to version 2.0 later today. Privately run 1.x servers will of course continue to function, and the public listing server will continue to accept announcements from the old version.

Compatibility notice: If you get an error saying "this is not a drawpile server" when you connect to a server, that means you're running version 1.0.6 and the server requires 2.0. If you try to connect to a 1.0 server with the 2.0 client, the client will just sit there until the connection times out. (It's waiting for a message in the new format that will not arrive.)

When upgrading from 1.0.6, I recommend first uninstalling the previous version to make sure no old libraries are left over. The Windows version now comes in 64 and 32 bit varieties. If the 64 bit version does not work for you, try the 32 bit one.

So, what's new in version 2.0? Read on to find out. (TL;DR at the end.)

Read more...

Drawpile 2.0 Release Candidate

Feb. 25, 2017

Version 2.0.0 release candidate is now out!

This is the last test release before 2.0.0 stable, which will be released in about two weeks from now. If major bugs are discovered before then, a there will be a second release candidate before the stable release.

Changes in this version include:

  • Added support for parental controls
  • New cursors for brush tools
  • Laser pointer style tweak
  • Server name included in session list
  • Default layer can now be selected
  • Selections can now be moved even when Cut&Paste is disabled

Once 2.0 stable is released, the public server will be switched over to the new version. The new server is, unfortunately, incompatible with 1.x clients, so please give this release candidate a try to see if there are any bugs or missing features that would keep you from using 2.0.0 instead of 1.0.6.

You can report bugs at the issue tracker, the Facebook group or even just by email.

Read more...

Drawpile 2.0 beta 3 released

Feb. 4, 2017

The third and final beta of 2.0 is now out!

This release adds all the remaining features that were planned for 2.0, including many features that went missing during the big rewrite at the start of the 2.0 development cycle.

New features include:

  • File backed sessions (replaces session hibernation)
  • GUI for adding and removing session announcements
  • GUI for setting an operator password
  • GUI for viewing session event log
  • Session settings are now shown in a dialog window
  • Login dialog now shows a progress bar until caught up. Login performance is also improved
  • Annotations can now be aligned vertically
  • Annotations access controls: protect individual annotations and limit annotation creation to operators
  • Individual users can now be blocked from sending chat messages
  • Chat message pinning fixed
  • Tool slots replaced with a tool preset pie menu
  • User accounts can now be configured in the server settings file
  • Session template feature is back
  • Improved server GUI

This version also introduced another few protocol changes, making it incompatible with beta2. The dptxt text format was also overhauled. This unfortunately breaks compatibility with all existing dptxt files. However, the new format is easier to read and more future proof, meaning files made with the new version should remain compatible with almost all future versions.

The next release will be 2.0 Release Candidate, and (if all goes well,) the next one after that will be the 2.0 stable. Please give the new version a try and report any bugs you might find at the issue tracker, the Facebook group or even just by email.

Read more...