Sounds awesome. Yeah I use views now to show things like a popup card would do. And I navigate to those views via buttons. Because those views are hidden they won’t swipe. I want to be able to swipe on hidden views but only certain ones. In my example it would look something like this:
views 1 to 5 are visible and swipable
views 6 to 30 are hidden, but when I land on view 10 (via a navigate action) I’d like to be able to swipe on pages 10-11-12 but those tabs must remain hidden so it cannot be swiped to from the first 5 tabs.
Sorry for the explanation again, I just find it hard to understand myself if I read it back Anyways thanks again for your hard work and thanks for fixing the default tab 2 issue.
I like the name View Groups. The config could be something like:
view_groups:
group_1:
name: Group 1
views: 1-5
group_2:
name: Group 2
views: 8-20
And it could even go a step further by defining view groups to a user agent.
exceptions:
- conditions:
user_agent: Macintosh
config:
view_groups: group_1
mayker
(maykar (pronounced "maker" with a southern accent))
1084
Since this would really only apply to swiping, I think making it something like swipe_groups: true and it would just operate by not skipping over tabs. So if you had show_tabs: 5 to 7, 9 to 12 it would only swipe between the tabs in each range, but not from 7 to 9.
but then if I use the header it would show me those tabs as well. Am I correct? I would love to have only 5 tabs visible in the header but being able to swipe on other views like suggested.
Well for me it would not be a problem to remove the header all together though. So this change would already be very nice XD
mayker
(maykar (pronounced "maker" with a southern accent))
1086
Ah, okay. I was misunderstanding a bit. This is a bit more involved, but still doable. It would be more flexible this way as well.
hi everyone. i stumbled across this and looking to see where exactly i am supposed to be configuring the CCH… ive done a few searches of this topic and looked through the docs on github but it doesn’t really say. am I adding this as a card in lovelace yaml? or am i doing this in the configuration.yaml?
i did add the module to lovelace and it auto removes the header text, but not quite sure where i need to add configs to customize the views based on user
Hello!
I have problem when installing this. It started when updating from 0.95.3 to 0.97.2.
I get this message:
#> # Log Details (ERROR)
Wed Aug 14 2019 17:11:32 GMT+0200 (centraleuropeisk sommartid)
https://my domain:port/local/community/compact-custom-header/compact-custom-header.js:211:5 Uncaught TypeError: Cannot read property ‘shadowRoot’ of null
I installed it using HACS, but it doesn’t save the files in /config/custom_components it installs it in /config/local/community/compact-custom-header, that’s why I have that folder adress. It worked before the update. I tried to uninstall and reinstall it with no luck. What can be the problem?
mayker
(maykar (pronounced "maker" with a southern accent))
1091
This is the correct folder for it to be installed. The custom_components folder is for components, this is not a component. There hasn’t been a anything related to shadowRoot on that line of code (211) since version 1.2.2 from july 11th. Current version is 1.3.5. This is most likely a caching issue, either you need to clear your cache or there is something off in your resources section.
I’m the creator of HACS, can you please elaborate what is wrong with that?
Could it be that you are simply mixing two different things?
One being the local folder, and the other being an endpoint (that you access in the browser)
Because with that logic you should actually use https://mydomain:port/config/www/community/..../.../...js which you probably know will not work
And if you don’t use the endpoint (yes, all lovelace resources are enpoints and not folder locations) that HACS suggest you should use, you will not get the benefits that HACS gives you:
Cache free hosting (would explain your issue)
Compressed file serving (Faster transfers with less data between the server and the client)
There were a few updates of CCH these last two weeks but the “hide” bug is still present. Do you have other ideas ? Any troubleshooting step to help you identify the problem ?
Thanks,
Anyways thanks again for your hard work and thanks for fixing the default tab 2 issue.
