search

maschek / imgmap

Javascript based imagemap editor
https://www.maschek.hu/imagemap/
GNU General Public License v2.0
59 stars 32 forks source link

Improvement: Usability - creating areas #12

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what browser/operating system?

Please provide any additional information below.

It would have been more natural if the process for drawing an area is:

1. Press
2. Drag
3. Release

Right now you have to press, release, drag, press to create the area
This concept is difficult for beginners

I guess ;)

Original issue reported on code.google.com by thomasan...@gmail.com on 16 Mar 2008 at 12:24

GoogleCodeExporter commented 9 years ago 
Your guess is right, but due to the nature of web browsers this is harder to 
achieve.
(By default with press/drag/release you will move the image for example, not to
mention the cross-browser event handling apocalypse). But i will take a look 
how hard
it is exactly.

Original comment by adam.mas...@gmail.com on 24 Mar 2008 at 9:56

GoogleCodeExporter commented 9 years ago 
What if the image is a CSS - background image? It may not solve the 
cross-browser
stuff though. 
Anyway this is a great plug-in and we would like to buy a license when the 
product is
ready.

Original comment by thomasan...@gmail.com on 25 Mar 2008 at 6:45

GoogleCodeExporter commented 9 years ago 
Yep, could be a background image, but still i would need a same-sized div to be 
able
to scroll when the image is larger than the container box. I think we can stick 
with
the foreground image and investigate how the desktop behavior could be 
implemented.

Original comment by adam.mas...@gmail.com on 25 Mar 2008 at 11:08

GoogleCodeExporter commented 9 years ago 
When creating many areas close to one another, canvases tend to overlap. This 
makes
it hard to click and define points for a shape. Is there anyway to prevent this 
from
happening? At the moment, I am resorting to moving shapes out of the way, 
defining a
new shape, then moving everything back to their original positions.

Original comment by john.at....@gmail.com on 11 Mar 2009 at 1:02

GoogleCodeExporter commented 9 years ago 
for this last comment see issue #22

Original comment by adam.mas...@gmail.com on 20 Mar 2009 at 12:24