You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my current use case, I'm using Image Hotspots for an office seating plan. There are around 40 hotspots placed on an office diagram.
In my front end template, each hotspot is accompanied by a number, and a key for the number and label is then displayed under the image. This is because there's not enough room to show all names on the image at the same time, and I need a printable version of the image and key, so interaction is not an option.
Editing them is quite tricky, as there's no indication of which label corresponds to which number.
If the plugin could include an option to display the index of the hotspot in the CP, it would make a huge difference to this use case.
Something like this:
I appreciate this is a specific use case, but even without the use of the label index in the front end, I think it does help to display the label information within the CP more clearly.
The text was updated successfully, but these errors were encountered:
In my current use case, I'm using Image Hotspots for an office seating plan. There are around 40 hotspots placed on an office diagram.
In my front end template, each hotspot is accompanied by a number, and a key for the number and label is then displayed under the image. This is because there's not enough room to show all names on the image at the same time, and I need a printable version of the image and key, so interaction is not an option.
Editing them is quite tricky, as there's no indication of which label corresponds to which number.
If the plugin could include an option to display the index of the hotspot in the CP, it would make a huge difference to this use case.
Something like this:
I appreciate this is a specific use case, but even without the use of the label index in the front end, I think it does help to display the label information within the CP more clearly.
The text was updated successfully, but these errors were encountered: