pughmat

Members
 View Profile  See their activity

  • Content count

    9

  • Joined

  • Last visited

Posts posted by pughmat

  2. Posted · Report reply

    This is a much-needed small feature. When you have a large difference in values across a chart, many of the smaller values are not readable given the Y axis current supports the largest value.  This is a fairly common feature across most charting packages.  (Very basic example attached) Given the original request in 4 years old, I suspect your not likely to add it. However, please keep me updated if you do.  Thanks, Matt

    scale breaks.png

  4. Posted · Report reply

    3 hours ago, Prerana said:

    Hello,

    As a workaround,

    1. Type about:config in the url bar of firefox.
    2. Search dom.w3c_touch_events.enabled
    3. Set the value to 0 and then check that whether the chart is working or not.

    Regards,

    Prerana Singh

    Hi Prerana,

     

    I followed the steps and it does allow both funnel charts and pie charts to work correctly which is great. However, I can't expect our tens of thousands of users to complete this kind of a step should they encounter the issue.  Firefox displays a very stern warning indicating a violation of warranty prior to making this kind of change and most of our users wouldn't feel comfortable trying this to begin with.  Additionally, the client would have to experience the problem before the solution could be provided.

    Can we expect a built in fix in an upcoming release soon?

    Thanks,

    Matt

     

     

  7. Posted · Report reply

    Fusion Team - 

     

    This bug ALSO exists in version 3.5.  Per your instructions of trying 3.5, we very quickly discovered two additional bugs within 5.0 that are logged here:

     

    Funnel 3.5.0, streamlinedData=0, Cannot read property 'fontSize' of undefined
     
    DragNode 3.5.0 cannot drag without link firing

     

    Can you provide a patch to 3.4 to address this issue as 3.5 has additional bugs preventing us from using it.

     

    Finally - just a suggestion to take it or leave it.  Before asking your clients to test new versions to determine if bugs still exist, I would recommend testing them on your own first.  When I read your post asking us to evaluate the newest version, I first thought perhaps you knew it was fixed and suggested trying 3.5.  Upon discovering the bug was not fixed, I have the feeling that you didn't know if it was fixed or not and that I was testing it for you. 

     

    Matt

  8. Posted · Report reply

    Do you have a ship date for the next release?  Will there be access to a pre-release version for testing on our side?  

     

    We had hoped our next product release would use your latest version (3.3.1-sr3.21100) [javascript only], however, we have noticed differences between the Flash and Javascript versions that will force us to go back to an older version of your product. 

     

    Thanks.

     

    Matt