Window position conflicts with Breaktime Module.

[BlackSwampDM]

Love the module, I also use the Breaktime module which adds a Breaktime option to the players bar. This makes the player bar larger. With your window in a fixed position relative to the height of the unmodified player window, it now obscures part of your modules window.
Any luck getting a window position option? Thanks

.

[BlackSwampDM]

I was able to disable breaktime module then move your module then re-enable so, no worries mate. Nevermind. Thanks for a gretat Mod!

[unsoluble]

Glad you sorted it out. As noted over in #137, I'm working on a way to nudge the SmallTime window away from Players for cases like this, just isn't done yet.

[BlackSwampDM]

Thanks for the response.

…

On Thu, Jul 28, 2022, 11:39 AM John Weston ***@***.***> wrote: Glad you sorted it out. As noted over in #137 <#137>, I'm working on a way to nudge the SmallTime window away from Players for cases like this, just isn't done yet. — Reply to this email directly, view it on GitHub <#139 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXPJF3PMHHDP3BF5YGHQAGLVWKSTHANCNFSM545D7GMA> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[Aeristoka]

on 1.15.4, I believe this isn't the intended behavior?

[unsoluble]

Mmmm depends? If the SmallTime window was pinned to the top of the Players list, then no it shouldn't do that (but I can't reproduce here). If it was manually placed, it could happen.

[Aeristoka]

Mmmm depends? If the SmallTime window was pinned to the top of the Players list, then no it shouldn't do that (but I can't reproduce here). If it was manually placed, it could happen.

Was snapped to the top of the player list, had all players exit, snapped it to top again, the moment they started loading in (as you can see, I have 7 of them) it got buried again.

[Aeristoka]

if I snap it to the top while they're all loaded in, I also get the drag bar buried under the player list:

[unsoluble]

Yeah I can't reproduce that here no matter what I try. Maybe try a Control-F5, something might be cached?

[Aeristoka]

I'll fiddle with it more after session... very strange...

[unsoluble]

You on Foundry v9 by any chance?

[Aeristoka]

You on Foundry v9 by any chance?

Sure am.

[unsoluble]

Got it. Sorry, I haven't been taking the time to test everything thoroughly in v9 on new builds; all my attention's been on v10 lately. Should be working better in 1.15.5 (out in a sec).

[Aeristoka]

No worries, appreciate your work! (and your GitHub avatar, showing your disappointment in yourself whenever you commit)