Make a floating box anchored to text using inline code
I'm trying to make an Organizer, including a weekly planner, based on one I found on the net using tex. I've managed, until now, to make some changes to adapt it to my needs and, for example, include my country holydays next to the day and month on the weekly planner. Now I'm trying to make a grey shadow behind the day planning lines only on the holydays and Sundays. This planner uses a python program to make the year macros and it would be easier for me to include this "shadow" anchored to the holyday text and using inline code.
Is there any way to do this?
the macro is something like this:
% Weekly Planner macros for 2019
LeftPageWP{1}{31 Dezembro - scriptsize{Véspera de Ano Novo}}{1 Janeiro - scriptsize{Ano Novo}}{2 Janeiro}{3 Janeiro}
RightPageHeaderWP{Dezembro 2018 -- Janeiro 2019}
RightPageWP{4 Janeiro}{5 Janeiro}{6 Janeiro}{Dezembro}{MonthTblDecPrev}{Janeiro}{MonthTblJan}{Fevereiro}{MonthTblFeb}
This "macro" is then used by a weekly planner tex file and then by a main tex file.
My idea was to include this "shadow" code inline on the macro file itself, next to the name of the holyday (scriptsize{Ano Novo}
) in order for it to be read by the tex processor.
the picture of what I want is something like this:
Thanks in advance
tikz-pgf diagrams
add a comment |
I'm trying to make an Organizer, including a weekly planner, based on one I found on the net using tex. I've managed, until now, to make some changes to adapt it to my needs and, for example, include my country holydays next to the day and month on the weekly planner. Now I'm trying to make a grey shadow behind the day planning lines only on the holydays and Sundays. This planner uses a python program to make the year macros and it would be easier for me to include this "shadow" anchored to the holyday text and using inline code.
Is there any way to do this?
the macro is something like this:
% Weekly Planner macros for 2019
LeftPageWP{1}{31 Dezembro - scriptsize{Véspera de Ano Novo}}{1 Janeiro - scriptsize{Ano Novo}}{2 Janeiro}{3 Janeiro}
RightPageHeaderWP{Dezembro 2018 -- Janeiro 2019}
RightPageWP{4 Janeiro}{5 Janeiro}{6 Janeiro}{Dezembro}{MonthTblDecPrev}{Janeiro}{MonthTblJan}{Fevereiro}{MonthTblFeb}
This "macro" is then used by a weekly planner tex file and then by a main tex file.
My idea was to include this "shadow" code inline on the macro file itself, next to the name of the holyday (scriptsize{Ano Novo}
) in order for it to be read by the tex processor.
the picture of what I want is something like this:
Thanks in advance
tikz-pgf diagrams
Sorry, I am completely lost. Please provide us with am minimal working example, i.e. a compilable document that starts withdocumentclass
, ends withend{document}
and illustrates your point.
– marmot
14 mins ago
add a comment |
I'm trying to make an Organizer, including a weekly planner, based on one I found on the net using tex. I've managed, until now, to make some changes to adapt it to my needs and, for example, include my country holydays next to the day and month on the weekly planner. Now I'm trying to make a grey shadow behind the day planning lines only on the holydays and Sundays. This planner uses a python program to make the year macros and it would be easier for me to include this "shadow" anchored to the holyday text and using inline code.
Is there any way to do this?
the macro is something like this:
% Weekly Planner macros for 2019
LeftPageWP{1}{31 Dezembro - scriptsize{Véspera de Ano Novo}}{1 Janeiro - scriptsize{Ano Novo}}{2 Janeiro}{3 Janeiro}
RightPageHeaderWP{Dezembro 2018 -- Janeiro 2019}
RightPageWP{4 Janeiro}{5 Janeiro}{6 Janeiro}{Dezembro}{MonthTblDecPrev}{Janeiro}{MonthTblJan}{Fevereiro}{MonthTblFeb}
This "macro" is then used by a weekly planner tex file and then by a main tex file.
My idea was to include this "shadow" code inline on the macro file itself, next to the name of the holyday (scriptsize{Ano Novo}
) in order for it to be read by the tex processor.
the picture of what I want is something like this:
Thanks in advance
tikz-pgf diagrams
I'm trying to make an Organizer, including a weekly planner, based on one I found on the net using tex. I've managed, until now, to make some changes to adapt it to my needs and, for example, include my country holydays next to the day and month on the weekly planner. Now I'm trying to make a grey shadow behind the day planning lines only on the holydays and Sundays. This planner uses a python program to make the year macros and it would be easier for me to include this "shadow" anchored to the holyday text and using inline code.
Is there any way to do this?
the macro is something like this:
% Weekly Planner macros for 2019
LeftPageWP{1}{31 Dezembro - scriptsize{Véspera de Ano Novo}}{1 Janeiro - scriptsize{Ano Novo}}{2 Janeiro}{3 Janeiro}
RightPageHeaderWP{Dezembro 2018 -- Janeiro 2019}
RightPageWP{4 Janeiro}{5 Janeiro}{6 Janeiro}{Dezembro}{MonthTblDecPrev}{Janeiro}{MonthTblJan}{Fevereiro}{MonthTblFeb}
This "macro" is then used by a weekly planner tex file and then by a main tex file.
My idea was to include this "shadow" code inline on the macro file itself, next to the name of the holyday (scriptsize{Ano Novo}
) in order for it to be read by the tex processor.
the picture of what I want is something like this:
Thanks in advance
tikz-pgf diagrams
tikz-pgf diagrams
asked 18 mins ago
Unkuiri
1
1
Sorry, I am completely lost. Please provide us with am minimal working example, i.e. a compilable document that starts withdocumentclass
, ends withend{document}
and illustrates your point.
– marmot
14 mins ago
add a comment |
Sorry, I am completely lost. Please provide us with am minimal working example, i.e. a compilable document that starts withdocumentclass
, ends withend{document}
and illustrates your point.
– marmot
14 mins ago
Sorry, I am completely lost. Please provide us with am minimal working example, i.e. a compilable document that starts with
documentclass
, ends with end{document}
and illustrates your point.– marmot
14 mins ago
Sorry, I am completely lost. Please provide us with am minimal working example, i.e. a compilable document that starts with
documentclass
, ends with end{document}
and illustrates your point.– marmot
14 mins ago
add a comment |
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f467871%2fmake-a-floating-box-anchored-to-text-using-inline-code%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f467871%2fmake-a-floating-box-anchored-to-text-using-inline-code%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Sorry, I am completely lost. Please provide us with am minimal working example, i.e. a compilable document that starts with
documentclass
, ends withend{document}
and illustrates your point.– marmot
14 mins ago