Custom Control LinkLabel - mouseover event not fired - Commercial Forums :: How do I... - Web, Cloud & Mobile Applications Delivery and Migration Platform

.net html5 web/cloud/mobile app delivery

Search Forum Home

Forum Commercial Foru... Commercial Foru... Custom Control LinkLabel - mouseover event not fired

2/22/2012 8:01 AM

	olszik
46 posts

Custom Control LinkLabel - mouseover event not fired

Modified By olszik on 2/22/2012 12:03:04 PM)

We have a ListView with one column where on mouseover we display the picture related to that record in ListView into a popup. We used custom control LinkLabel to implement this functionality. The problem we currently have is following: all works correct on development system but when we deploy on client the mouseover functionality doesn’t work anymore. Seems like the MouseOver event it is not fired at all on client system. We cannot really provide you a sample for this issue, but if you can give us some hints, why this happen, will really help.

Thx in advance.

2/22/2012 10:50 AM

	palli
11824 posts

Re: Custom Control LinkLabel - mouseover event not fired

Hi,

Without seeing more details on the implementation of your control customization, it's very hard to recommend anything of much value. What comes to mind if using IE is to try adding your production site in trusted sites list, but that can be completely irrelevant here.

Any chance you can email the customized control only, and possibly a simple ListView example so we can study this further. We would be willing to sign an NDA if that would make it easier for you.

In any case, emailing to support, the email will only be viewed by 1 or 2 persons (me and Ori) and we would not distribute your samples in any way.

Please let me know how you want to continue.

Palli

Páll Björnsson - Visual WebGui support team - Email: support@visualwebgui.com

2/24/2012 3:38 AM

	olszik
46 posts

Re: Custom Control LinkLabel - mouseover event not fired

Hello Palli,

Thx for your feedback and sorry for late reply ... I think we found one deployment issue and seems to be the reason for this behaviour. We'll need to wait for the client to deploy it on their system and at that time we'll know for sure that this was the problem. In case we'll still have it I will be back to you with implementation of custom control we used, but I think will not be the case.

Best regards & thx again.