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
I was able to figure out by removing the /dl from the end of the url, it then displayed an xml and i was able to figure to add the file name and extension to the url minus the /dl and it immediately downloaded the exe that i needed, but i am not sure that others will know to do that. I would suggest as an easy solution to maybe have a link with a page that has the direct urls for the user to select based on what operating system they are using. I understand that the xml comes in to play once the user has it installed and that works nicely. I m just suggesting so that a first time user does not get discouraged if they cant figure it out.
Expected Behavior (and Current Behaviour)
When I clicked on the link to download ChroMapper, I was expecting that a file would begin downloading right away but instead only an image was displayed and no action appeared to be happening.
Additional Context
The suggested fix would be to have a page to direct users to that would provide several direct links for a user to click on that will begin the downloading process for them. Hope this helps some other users, other wise keep up the good work.
The text was updated successfully, but these errors were encountered:
sorry for the delay just saw your response. I tested it in
Chrome version 101.0.4951.54 (Official Build) (64-bit) and i tried it in
The Edge Version 101.0.1210.39 (Official build) (64-bit)
When I load the page now I do see the buttons for each of the operating systems which is perfect but for sure when i tested earlier i did check from multiple machines and multiple browsers from each machine but the operating system on both machines that i tested from was Windows 10 and a Windows 11 machine. but looks solid now. I am attaching a small bit of code that you could optionally include, just set the method getDebugInfo(); to run on window load and then add a div with an id of "debug-container" below where the buttons are now and when the user loads the page it will display the browser and operating system that they are currently viewing the page on so that they definitely grab the right version. Even without this extra piece it looks and behaves like i believe it was intended to.
ChroMapper version
The item being reported is not related to the actual version of ChroMapper
Describe the Issue
I am on Windows 11 64 bit operating system and when i go to the download link nothing actually happens. It just displays an SVG image. Here is a link to the image. (https://drive.google.com/file/d/1-EyAU_lg1PS5LptE_BUlO40rn0mZPYYq/view?usp=sharing)
I was able to figure out by removing the /dl from the end of the url, it then displayed an xml and i was able to figure to add the file name and extension to the url minus the /dl and it immediately downloaded the exe that i needed, but i am not sure that others will know to do that. I would suggest as an easy solution to maybe have a link with a page that has the direct urls for the user to select based on what operating system they are using. I understand that the xml comes in to play once the user has it installed and that works nicely. I m just suggesting so that a first time user does not get discouraged if they cant figure it out.
Provide Screenshots or Videos
https://drive.google.com/file/d/1-EyAU_lg1PS5LptE_BUlO40rn0mZPYYq/view?usp=sharing
Stack Trace
N/A
Steps to Reproduce
N/A
Expected Behavior (and Current Behaviour)
When I clicked on the link to download ChroMapper, I was expecting that a file would begin downloading right away but instead only an image was displayed and no action appeared to be happening.
Additional Context
The suggested fix would be to have a page to direct users to that would provide several direct links for a user to click on that will begin the downloading process for them. Hope this helps some other users, other wise keep up the good work.
The text was updated successfully, but these errors were encountered: