-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Get position of the pressed button in the inline JS #414
Comments
Getting line numbers and positions of inline elements is not possible in reading mode, which is a limitation of the Obsidian API. |
Is it possible to get the rendered output, i.e. the contents of
preview/reading mode? This would help with another issue.
Moritz Jung ***@***.***> schrieb am Mo., 16. Sep. 2024, 20:59:
… Getting line numbers and positions of inline elements is not possible in
reading mode, which is a limitation of the Obsidian API.
—
Reply to this email directly, view it on GitHub
<#414 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABL3CWIY2Q4ETKXGI56RLODZW4TA5AVCNFSM6AAAAABOJ3UYEKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJTGY4DKNBTGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
what exactly do you mean by output? The HTML element of the button? You should never modify that. |
I did not want to modify the rendered html. I want to parse it, actually
not the button but the context (section below it).
Moritz Jung ***@***.***> schrieb am Mo., 16. Sep. 2024, 21:43:
… what exactly do you mean by output? The HTML element of the button? You
should never modify that.
—
Reply to this email directly, view it on GitHub
<#414 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABL3CWNJ7D47DNGUUZK42TTZW4YGHAVCNFSM6AAAAABOJ3UYEKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJTG43TGMBXGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Maybe my question was misleading. With inline I ment inline of the button
definition, not in markdown inline code.
The issue is that your plugin provides notePosition to
e.g. runReplaceSelfAction but not to runInlineJsAction. In that inline Js
code I would need to position.
Am Mo., 16. Sept. 2024 um 20:59 Uhr schrieb Moritz Jung <
***@***.***>:
… Getting line numbers and positions of inline elements is not possible in
reading mode, which is a limitation of the Obsidian API.
—
Reply to this email directly, view it on GitHub
<#414 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABL3CWIY2Q4ETKXGI56RLODZW4TA5AVCNFSM6AAAAABOJ3UYEKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJTGY4DKNBTGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
In the next version of the plugin you can access some extra information about the button including its location (if known) via |
Great, thanks.
Any planned release date?
Am Sa., 21. Sept. 2024 um 14:02 Uhr schrieb Moritz Jung <
***@***.***>:
… In the next version of the plugin you can access some extra information
about the button including its location (if known) via
context.buttonContext
—
Reply to this email directly, view it on GitHub
<#414 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABL3CWN2UTCYITIQ6LZEFTDZXVN5RAVCNFSM6AAAAABOJ3UYEKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRVGE3DCNRZG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
No. When it's ready. A canary release will come tomorrow, if you can't wait. |
Please fill out these Check-boxes
Is your Feature Request related to a Problem or Annoyance?
No response
Describe the Feature you'd like
I need to process the text in the context of the button, e.g. the markdown section below the button.
For that I need to know the buttons line or offset.
The editors cursor might be somewhere else.
Alternatives
At least get the ID of the button. But would be off much less help because duplicating section with related buttons would lead to non-distinguishable IDs.
Additional Context
No response
The text was updated successfully, but these errors were encountered: