Skip to content
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

🐞 forceColumns and columnHeight not working properly #424

Open
3 of 7 tasks
drmy022 opened this issue Jun 18, 2024 · 0 comments
Open
3 of 7 tasks

🐞 forceColumns and columnHeight not working properly #424

drmy022 opened this issue Jun 18, 2024 · 0 comments

Comments

@drmy022
Copy link

drmy022 commented Jun 18, 2024

Check for existing bug reports before submitting.

  • I searched for existing Bug Reports and found no similar reports.

Expected Behavior

Pick any wordy statblock (i.e. Ancient Black Dragon)

```statblock
monster: Ancient Black Dragon
columns: 4
forceColumns: 1
columnWidth: 300
columnHeight: 200
```

This should make the statblock appear in 4 separate columns of 300px wide and 200px high

Current behaviour

Currently, playing around with columnHeight has no bearing on the shape of the statblock at all.
Furthermore, forceColumns does not actually force the statblock into the correct number of columns.

In the current exemple, it only renders 3 columns. If you change columns to 5, it will add a forth column.

image

image

image

image

Reproduction

Pick any new vault

Install Fantasy Statblock Plugin

Generate any statblock using a the statblock codeblock (lengthier ones are more obvious to work with like Ancient Black Dragon)

Add the fields columns, forceColumns, columnWidth and columnHeight in the statblock codeblock

Set columns > 3

Set forceColumns to true

Set column Height to any integer

Go in reading view - The note will not be the number of columns asked nor will the height move.

Which Operating Systems are you using?

  • Android
  • iPhone/iPad
  • Linux
  • macOS
  • Windows

Obsidian Version Check

1.6.3

Plugin Version

4.4.2

Confirmation

  • I have disabled all other plugins and the issue still persists.

Possible solution

No response

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

No branches or pull requests

1 participant