Pages: 1
Author Topic: large element selection in XMax 7  (Read 2084 times)

Posts: 3

« on: July 25, 2016, 01:45:50 PM »

Hello, I support a product developed using XMax 7.0.  Clients report issues selecting elements that span more than the height of the page.  When the opening tag of the element is clicked, the entire element is selected on mouse down, the screen is scrolled to the middle of the element, and on mouse up the child element that was scrolled to is selected.

The client would like the original selection (mousedown) to remain.  Is this something that can be done using XMax 7?  Does any newer API allow control of this behaviour?  Is the mouseup handling built-in?

Derek Read
Program Manager (XMetaL)

Posts: 2621

« Reply #1 on: July 25, 2016, 02:57:47 PM »

I am unable to reproduce this issue, but as XMAX 7 is very old I am not testing with that version.

This issue does not appear to occur in version 11 either, but I am testing with a simple DTD, simple XML content, simple CSS, absolute minimum CTM settings and no MCR file. XMAX is embedded in an HTML page inside IE version 11. The only script loads a string into XMAX and XMAX is finding the DTD, CSS and CTM files from the path specified in the XML file's DOCTYPE declaration.

I suggest you test with the current release. If the issue still occurs in version 11 please contact XMetaL Support and provide all the files needed to reproduce the issue. The issue you describe could be caused by a script or macro that is running and manipulating the user's selection. If it isn't caused directly by a script or macro then we might be looking for a bug triggered by some very specific combination of DTD, CSS, and CTM settings or perhaps even the content of the XML itself.

If it was easy to reproduce this is the kind of issue that other clients would have reported. There aren't any bugs filed that match what you are describing.
« Last Edit: July 25, 2016, 03:00:53 PM by Derek Read » Logged

Posts: 39

« Reply #2 on: October 11, 2016, 09:59:58 AM »

Dear lefrac01,
we are experiencing the same issue using XMAX 10 within forms. Wondering if you found a work-around solution?
Pages: 1
Jump to: