Hey, I’m trying to resize the bullets since i have them “clickable” and on my touchscreen (raspberry pi os) i can’t swipe (it bugs) and clicking works.
But the bullets are too small to click.
Do you have any idea how to css them and where?
This is what I have but it has no effect @Bram_Kragten
Hey all, I am using this with a raspberry pi and a touchscreen, chromium. And I experience that swipe just won’t work. It won’t fully swipe as it should and it’s laggy. Did others experience this issue, and found a solution for this?
added the .js file in www/custom-lovelace/swipe-card/
added resources:
url: /local/custom-lovelace/swipe-card/swipe-card.js?v=3.0.0
type: module
to the top of lovelace yaml but get this error when trying to make a custom card… ??
UI editor is not supported for this config:
Cannot read property ‘setConfig’ of undefined
You can still edit your config in yaml.
lovelace:
mode: yaml
# Include external resources only add when mode is yaml, otherwise manage in the resources in the lovelace configuration panel.
resources:
- url: /local/my-custom-card.js
type: module
- url: /local/my-webfont.css
type: css
Technically you can. Just create Picture or Glance Cards and insert those inside the Swiper Card. Then use the correct parameters and components (like navigation and/or pagination). Then you have what you showed in the demo.
I tried to make a simple example and I’m not sure that what I’m trying to do is possible…
In fact the “Thumbs” component is a way to sync two swipers so the main swiper has another instance of a swiper in parameter
So two question about the code example below (which doesn’t work) :
Is vertical stack the right way to do it?
Can I instantiate my sub swiper in the main swiper ?
Is there a way to have the cards auto swype? I have all my notifications setup but I want them to auto scroll and also somehow hide the pages without any active notifications.
Well figured out autoscroll but I still need to to hide inactive cards, anyone with a tip?
Figured it out but I am still getting t.set error if I refresh the page, until I open another tab with another swipe-card in it. I wonder if it has something to do with custom stack in card and loading it in a tab without a stack in card it fixes it. And I cant hide the header toggle something is breaking the show_header_toggle: false and the show_empty: false was the key to hide empty slides
Hopefully with the new grid stack card in 118 I won’t have to use the custom card anymore and it will work.
Any update on the “t.setConfig is not a function” error? I was hopeing it would have been fixed with the new grid card but im still getting it. Getting “t.setConfig is not a function” every time its in any nested card.
So it loads 100% of the time if i go into edit mode and move the tab its on either left or right then move it back. This works for about a day then something internal refreshes and I then get the error again, this also causes a annoying issue of triggering the notification that the frontend has changed and needs to refresh.
Love this card and I’m using it to swipe between two picture-elements cards for my groundfloor and first floor floorplan.
On these I have different light entities that I can control by a long-press (which calls the browser_mod service) which shows different controls.
Used this card two combine those two views into one swipe card.
However the long press on an entity on each of the picture elements cards doesn’t respond anymore.
Anyone knows how to fix this?
Hy, thank to your works.
I try it with card type: picture-entity but every picture in swipe card appear in black and white ?
How i can visualizze in color?
Has anyone figured out a way to make the swiper card switch to a specific card? I would love to have a button or UI element switch to a different card than is currently displayed (ie. card 2 out of the 3). I believe the underlying code used by the card supports it, but have no idea if anyone has figured out how to do it from lovelace.
I don’t think it’s possible, since a button would need a service call to envoke swiper card, which swiper doesn’t have. It would need to be a custom component instead of only a custom card.
But honestly, what’s the point in using swiper card if you want to use buttons or other UI elements. That defeats the whole purpose of swiping the card (it’s in the name).
You are better off using state-switch card in your case. I use that myself as well for some elements. That card allows you to switch to different cards/views and use hash and entities to envoke it. See -> https://github.com/thomasloven/lovelace-state-switch