Skip to content

Allow "Move but don't size with cells" to be set on images. #2237

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 6 commits into from

Conversation

AdamGaskins
Copy link

This is:

- [ ] a bugfix
- [x] a new feature

Checklist:

Why this change is needed?

See #1159 (and the abandoned PR #1160)

By default when adding a Drawing to a spreadsheet, it is added inside a oneCellAnchor. This makes it easier to specify a width and height, however in some cases developers may want to change the default value of the option pictured below in Excel. This PR allows developers to add images into spreadsheets with the setting "Move and size with cells."

image

Example use case: imagine a spreadsheet of product data where each row has a column called "Images." When a product row is deleted, it would make sense for the photo to be deleted as well. The only way for this to happen is to have "Move and size with cells" set.

All existing code will work the same, as oneCellAnchor remains the default. See samples/Basic/47_Image_move_and_size_with_Cells.php for an example of the new process using twoCellAnchor.

  • Change the Drawing to twoCellAnchor mode.
  • Specify the coordinates and offset as usual.
  • Specify the coordinates and offset for the bottom right corner of the image using the new setCoordinates2(), setOffsetX2() and setOffsetY2() methods.
    • (setWidth() and setHeight() only work with oneCellAnchor mode)
  • Add to the worksheet like normal

One other note: I also added getImageWidth() and getImageHeight() functions to drawing that return the original pixel width/height of the image. getWidth() and getHeight() contain this value when the image is initially loaded into the Drawing, but if you resize it in the worksheet this info is lost. Having these isn't necessary, but may be helpful due to the increased complexity of inserting images in twoCellAnchor mode.

By default, images added to spreadsheets are using oneCellAnchor.
However, it is common to want an image in each row of a spreadsheet,
and to need those images to be deleted when the row is deleted in
Excel.

By calling setAnchorType(Drawing::ANCHORTYPE_TWOCELL) and using the
new setCoordinate2() method, developers can specify which row(s)
contain the image, and when they are deleted the image is too.
@h-shiina-spiderplus
Copy link

Hi! @AdamGaskins
Can you merge it?

Copy link
Member

@PowerKiKi PowerKiKi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like a nice improvement. There is a few things to improve though.

  • the PR would need to be rebased on master
  • unit tests are missing
  • all new code must be type-hinted (not phpdoc-ed)
  • parameters like $pValue should not be used anymore, instead use proper names, such as $anchorType and so on

@maximerenou
Copy link

Hello @AdamGaskins, are you still available to help on this feature? It would be a nice improvement.

@AdamGaskins
Copy link
Author

Sure I can make the requested changes 👌🏻

oleibman added a commit to oleibman/PhpSpreadsheet that referenced this pull request Mar 1, 2022
This change was introduced by @naotake51 as PR PHPOffice#2532, but it was closed before I had a chance to review it, and I have been unable to communicate with the author since. I will gladly defer to the original. Please see the original PR for details.

Similarly, PR PHPOffice#2237 (@AdamGaskins) is open, but with changes requested for several months. It covers a lot of the same ground as 2532. It makes sense to me to combine them.

To those changes I added support for the 'editAs' attribute - I imagine that there are instances of 'absolute' out in the wild.

There have been several other tickets referencing two cell anchors, including issue PHPOffice#1159 and PR PHPOffice#1160 (@sgarwood, who also added support for editAs), PR PHPOffice#643, and issue PHPOffice#126, all now closed but not necessarily entirely resolved. I will try to ensure that those tickets are addressed with this one.

And, in trying to make sure 1160 is covered, I stumbled upon a bug. If you use the same image resource to create two+ memory drawings, the MemoryDrawing destructor for the first will cause the rest to generate a very long warning message. This is not a problem for Php8+, only for Php7-. I have suppressed the message in the MemoryDrawing constructor. 1160 went stale due to an unresolved test error, but I don't think this was the problem. At any rate, its test works now.
@oleibman oleibman mentioned this pull request Mar 1, 2022
5 tasks
oleibman added a commit to oleibman/PhpSpreadsheet that referenced this pull request Mar 13, 2022
This change builds on PR PHPOffice#2532 (@naotake51 as PR PHPOffice#2532), using ideas from PR PHPOffice#2237 (@AdamGaskins), which has had changes requested for several months. It covers a lot of the same ground as 2532. In Excel, two-cell anchor drawings can be edited as "twocell", "onecell", or "absolute". This PR adds support for those options, with a sample file that demonstrates the difference in addition to unit tests. Several other tests are added to improve the spotty coverage for Drawings.

There have been several other tickets referencing two cell anchors, including issue PHPOffice#1159 and PR PHPOffice#1160 (@sgarwood, who also added support for editAs), PR PHPOffice#643, and issue PHPOffice#126, all now closed but not necessarily entirely resolved. I will try to ensure that those tickets are addressed with this one.

And, in trying to make sure 1160 is covered, I stumbled upon a bug. If you use the same image resource to create two+ memory drawings, the MemoryDrawing destructor for the first will cause the rest to generate a very long warning message. This is not a problem for Php8+, only for Php7-. I have suppressed the message in the MemoryDrawing constructor. 1160 went stale due to an unresolved test error, but I don't think this was the problem. At any rate, its test works now.
@oleibman
Copy link
Collaborator

Superseded by PR #2532 and PR #2674.

@oleibman oleibman closed this Mar 13, 2022
oleibman added a commit that referenced this pull request Mar 16, 2022
* Add editAs Property for 2-cell Anchor Drawings

This change builds on PR #2532 (@naotake51 as PR #2532), using ideas from PR #2237 (@AdamGaskins), which has had changes requested for several months. It covers a lot of the same ground as 2532. In Excel, two-cell anchor drawings can be edited as "twocell", "onecell", or "absolute". This PR adds support for those options, with a sample file that demonstrates the difference in addition to unit tests. Several other tests are added to improve the spotty coverage for Drawings.

There have been several other tickets referencing two cell anchors, including issue #1159 and PR #1160 (@sgarwood, who also added support for editAs), PR #643, and issue #126, all now closed but not necessarily entirely resolved. I will try to ensure that those tickets are addressed with this one.

And, in trying to make sure 1160 is covered, I stumbled upon a bug. If you use the same image resource to create two+ memory drawings, the MemoryDrawing destructor for the first will cause the rest to generate a very long warning message. This is not a problem for Php8+, only for Php7-. I have suppressed the message in the MemoryDrawing constructor. 1160 went stale due to an unresolved test error, but I don't think this was the problem. At any rate, its test works now.

* Scrutinizer

It reported 1 minor issue (fixed normally), and 2 major. One is fixed with a kludge. The other is a case where Scrutinizer's analysis is just wrong, and I can't figure out a kludge. But I was able to add an annotation (the first time I've managed to get one past phpcs/php-cs-fixer). We'll see.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

5 participants