bramkragten / swipe-card

Card that allows you to swipe throught multiple cards for Home Assistant Lovelace
245 stars 36 forks source link

setConfig error after upgrade to 0.107.1 #9

Closed jeremywillans closed 4 years ago

jeremywillans commented 4 years ago

Following upgrade to 0.107.1 I get the following issue when using the swipe-card

image

Test Config

cards:
  - card:
      content: |
        Test Markdown Card
      type: markdown
    conditions:
      - entity: input_boolean.vacation
        state: 'on'
    type: conditional
parameters:
  allowTouchMove: true
  autoplay:
    disableOnInteraction: false
  effect: coverflow
  grabCursor: true
type: 'custom:swipe-card'
bramkragten commented 4 years ago

Yeah, I have a fix for that on the master branch waiting to be tested. Could you maybe test that?

Stephan296 commented 4 years ago

I will ;-)

jeremywillans commented 4 years ago

Im getting hit and miss results after switching to Master on HACS.

the error message has cleared, however in my current configuration, the card appears to be freezing during animation, reproducable both on desktop (chrome) and ios (native app)

(screenshot width is equal to expected card width)

image

bramkragten commented 4 years ago

@jeremywillans that seems to be a different issue (not really sure I understand the issue) can you please create a new issue for that?

samgundel commented 4 years ago

This issue was closed. Does it mean the setconfig problem is solved on master?

I am using master now and I still have the setConfig issue. Only when clicking on the three dots (update ui), the card loads

Update: If the swipe card is on the default view, where home assistant starts, the setconfig problem appears systematically. If nevertheless the swipe is on another tab in which I need to click on the tab, then the problem does not happen. Is there a way to force a refresh somewhere? I still would like to use the swipe-card on my main view because it's so awesome 👍

jeremywillans commented 4 years ago

@jeremywillans that seems to be a different issue (not really sure I understand the issue) can you please create a new issue for that?

Sorted - removing the coverflow effect in configuration fixed this issue.