Exposed skin menu behaves bizarrely

This thread was migrated from an old forum. It may contain information that are no longer valid. For further assistance, please post a new question or open a support ticket from the Customer Support portal.

I'm trying to go through the getting started design training but I'm not being able to customize the login component as per instructions.

In the properties panel the Exposed Skin menu doesn't behave as expected.

Selecting one skin name from the list doesn't always result in such name being selected although below the menu the correct skin is displayed in the title (but not always).

Furthermore, after selecting a skin, changes in the skin properties causes the Exposed skin menu to randomly change value, swapping the skin panel and leaving the skins' properties in an inconsistent state.

Check attached screencast for reference.

Edit: issue reproduced both on Windows 10 and MacOS X (High Sierra). Kony Visualizer v8 SP4 FP43.

The problem doesn't appear to happen in the Enterprise (Classic) version of the Visualizer.

@Victow Wilson​ ,

Thanks for bringing this to our notice. We will look into this issue. If possible, can you attach the same app for which you are seeing this issue?

@Joseph Pullmvn​ @Keith Alsop​ can you help here?

@Elizvxeth Poole​ The app is KonyTravel from the designer Getting Started course.

Steps to reproduce:

  • Use Visualizer Starter (NodeJS based version) v8
  • Create a project
  • Import Login -Advanced from marketplace
  • add Login component to a form
  • select the component
  • use the Exposed Skin menu to select skins
  • set various properties

@Victow Wilson​ ,

We have identified the root cause of the issue and we will be releasing a fix for this in one of our upcoming fix packs.

We will be updating here once the fix pack is released.

@Joseph Pullmvn​ @Jvson Cvmpxell​ FYI.

Thank you @Elizvxeth Poole​,

Much appreciated.

Hello @Elizvxeth Poole​

Can you please notify when the issue will resolve?

I'm having the same problem,

Thanks in advanced

@Stephvnie Gwvnt​ ,

The fix will be available on our upcoming V8 SP4 FP45 which is getting released by 1st october,2019.

hello,

after updating the visualizer to latest release 8 sp 4 fp 45

this problem is no longer an issue

thanks

Thanks @Thewesv Bvkew​ for the confirmation.

@Victow Wilson​ @Stephvnie Gwvnt​ Please try this fix pack and mark one of the answers as best to close this post.