[Editor] A new CurrentPointers class to store current pointers used by the editor

[legraina]

I have created a different PR as requested.

Move current pointer field of DrawingEditor to CurrentPointer class in tools.js. Also, only reset pointer type when user select a new mode.

• PointerType:
  • The pointer types fields have been moved to a CurrentPointer object in tools.js. This object is used by eraser.js and ink.js
  • Clear the pointer type when changing mode, instead of at the end of the session. It seems more stable, as the method is not called this way when the user changes pages.
  • Only clear the pointer type when the mode is changed by an event (the user changes the editor type), otherwise, the same pointer type is kept (the document is changed for example).

[calixteman]

Please update the title of the PR to precise its goal in few words.

[legraina]

I've made most of the modifications asked.

[legraina]

Hi @calixteman, everything looks good ? Or anything else to change/improve ? Thanks

[calixteman]

/botio integrationtest

[moz-tools-bot]

From: Bot.io (Linux m4)

---

Received

Command cmd_integrationtest from @calixteman received. Current queue size: 0

Live output at: http://54.241.84.105:8877/1daf869439e6efa/output.txt

[moz-tools-bot]

From: Bot.io (Windows)

---

Received

Command cmd_integrationtest from @calixteman received. Current queue size: 0

Live output at: http://54.193.163.58:8877/95a4007ba862abb/output.txt

[moz-tools-bot]

From: Bot.io (Linux m4)

---

Success

Full output at http://54.241.84.105:8877/1daf869439e6efa/output.txt

Total script time: 19.64 mins

• Integration Tests: Passed

[moz-tools-bot]

From: Bot.io (Windows)

---

Success

Full output at http://54.193.163.58:8877/95a4007ba862abb/output.txt

Total script time: 45.51 mins

• Integration Tests: Passed

[calixteman]

@legraina could you rebase and squash your PR please ?

[legraina]

@legraina could you rebase and squash your PR please ?

@calixteman Done

[timvandermeij]

Please fix the commit message to have a descriptive title and body so that when reading the git log output it's easy to tell what the change was and why it was introduced.

In general I can recommend https://cbea.ms/git-commit/ which explains how to write good commit messages and why that matters.

[legraina]

@timvandermeij, it's done. Is it better ?