Skip to content

Column number override#34

Open
stribioli wants to merge 2 commits intoadrienverge:masterfrom
stribioli:master
Open

Column number override#34
stribioli wants to merge 2 commits intoadrienverge:masterfrom
stribioli:master

Conversation

@stribioli
Copy link

Hi, thanks for your software!

I introduced the ability to manually set the number of columns. I find it quite useful, since the new auto-layout algorithm introduced in 1.4 generates strange grids sometimes.

This is a quick-and-dirty implementation, feel free to do whatever you please with it :)

Introduces a new option to manually set the number of columns in
the layout. If 0, the usual autosensing applies.

Layout is now regenerated every time the SettingsDialog is closed
with ok. This might be unwanted.
Copy link
Owner

@adrienverge adrienverge left a comment

Choose a reason for hiding this comment

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

Hey @sassospicco, looks good!

Would it be possible for you to change the settings appearance? I'm thinking about something like:

Layout
------

[x] automatic          number of columns: |   |

dialog.destroy()
if self.history:
self.render_preview()
self.regenerate_layout()
Copy link
Owner

@adrienverge adrienverge Sep 29, 2016

Choose a reason for hiding this comment

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

Please regenerate layout only if the number of cols changed. Users don't want their collage to change if they just chose a different border color.

Copy link
Contributor

Choose a reason for hiding this comment

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

@adrienverge, I see that it has not been decided for a long time. I can reopen this PR with line self.regenerate_layout() instead of self.render_preview(). Ok?

Copy link
Owner

@adrienverge adrienverge Jul 5, 2021

Choose a reason for hiding this comment

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

@andreynovikov95 I'm not sure it's a good idea, as this PR would bring more complexity to the tool, which is not needed here. But thanks for proposing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants