Suggestion: Display previous months on calendar view (Upcoming Calendar Indicator)

16
closed
Andrew6rant
Andrew6rant
Posted 1 year ago

Suggestion: Display previous months on calendar view (Upcoming Calendar Indicator) #14

Here is a quick mock-up I made in photoshop to demonstrate: before after

mvan231
mvan231
Created 1 year ago

Something like this? I found that with transparency on it won't render the widget. Probably on the edge of the memory limit 1EF65B33-2ABD-49F3-98D7-CFDF6EF704A0

Andrew6rant
Andrew6rant
Created 1 year ago

That looks great! If it would be at all possible, could you make it so event dots outside of the current calendar month are gray like the numbers?

If you are not willing to have an update to master that hits the memory limit, could you just share the code so I can use and maintain it on my own branch? I have a jailbroken iPhone so I can manually adjust the Jetsam memory allocated to Scriptable.

Thanks a ton!

mvan231
mvan231
Created 1 year ago

That's wild that you can adjust the amount of memory available for it.

Out of curiosity, what is the benefit of having the dots there, if they are gray?

Andrew6rant
Andrew6rant
Created 1 year ago

Thinking about it more, it doesnt really make sense for them to be gray - I kind of just wanted something to emphasize the current month and stay consistent with how the other months are colored.

Maybe turning down the alpha transparency value for them instead?

It's not really a big thing at all, looks great as is right now anyways.

mvan231
mvan231
Created 11 months ago

Excellent! Can you test this 1.9beta for me?

Andrew6rant
Andrew6rant
Created 11 months ago

Works great! Tossed ya a coffee on PayPal

mvan231
mvan231
Created 11 months ago

Thanks so much! Glad you like it so far. I think some further tweaks might be needed and you might want to also make some additional changes as well if you want transparency with it

Andrew6rant
Andrew6rant
Created 11 months ago

Unfortunately, while the widget does render without transparency enabled, it is still close enough to the memory limit that I am getting constant Jetsam crashes from ScriptableWidgetExtension (dk.simonbs.Scriptable.ScriptableWidget). Jetsam crashes are not detectable on non-jailbroken devices, but the processes are still killed and restarted the same. I've gotten well over 100 crashes yesterday, and I believe it has had a noticeable impact on my battery life.

Increasing the hard memory limit from 30mb to 32mb has solved this on my end, but this solution isn't possible for users on non-jailbroken devices. I suggest not pushing Beta 1.9 to release unless you can somehow manage to get the memory footprint down.

mvan231
mvan231
Created 11 months ago

Thanks so much! I'll look into optimizing it further if I can. I've been meaning to try and optimize the memory usage further anyway. I'll hold off 1.9 for now. It would be a shame to have this feature enabled on someone's device and have it end up crashing that much

On Fri, May 21, 2021 at 3:59 PM Andrew6rant ***@wrote:

Unfortunately, while the widget does render without transparency enabled, it is close enough to the memory limit that I am getting constant Jetsam crashes from ScriptableWidgetExtension (dk.simonbs.Scriptable.ScriptableWidget). Jetsam crashes are not detectable on non-jailbroken devices, but the processes are still killed and restarted the same. I've gotten well over 100 crashes yesterday, and I believe it has had a noticeable impact on my battery life.

Increasing the hard memory limit from 30mb to 32mb has solved this on my end, but this solution isn't possible for users on non-jailbroken devices. I suggest not pushing Beta 1.9 to release unless you can somehow manage to get the memory footprint down.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/mvan231/Scriptable/issues/14#issuecomment-846221390, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMENLER7Z4FXBFDXJCECU7LTO23SRANCNFSM44KW3KZQ .

mvan231
mvan231
Created 11 months ago

Actually, I have a question, are you able to see how much memory a widget would use even if it ends early? I'm thinking we could force it to error early so we could try and piece together how much memory each section of the script is using so it could be a more targeted approach. Just an idea I had while looking at the code

Previous