3 Replies Latest reply on Apr 26, 2013 5:52 AM by mikebeargie

    Charts in FM12 vs FM11 - Layout objects too big

    sleepy62

      So we have this very large database solution which has many many chart reports and UI's with charts. After converting from FM11 to FM12 many are essentially broken and all require editing. Im OK with the editing but many of the bar charts and small and intented to fit in a one line subsummary part. Due to the massive increase in layout object size of a chart in FM12 this is no longer possible.

       

      I have not been able to find any discussion of this anywhere so Im wondering if Im missing something?? Ive payed with all the settings til the cows come home, removing titles, legends, fonts sizes to 1pt etc. But still the object is much larger than in FM 11 and our reports are basically impossible to produce. Ive inserted an example below form the FM11 version.

       

      Screen shot 2013-04-25 at 5.30.52 PM.png

       

      Any help would be appreciated.

       

      Mike

        • 1. Re: Charts in FM12 vs FM11 - Layout objects too big
          mikebeargie

          you've tried removing the theme styles using the "remove all styles" button in the inspector, correct? (under the appearance tab).

           

          It seems that charting is a core feature of your solution, and you may want to hold off migrating until you can either come up with an alternative in 12, or fix the issue through trial and error.

           

          Not really relative, but I've done a similar style bar graph in past-days using conditionally formatted text blocks. Not as good as charting, but I was able to control the block size down to a much smaller line height and width.

          • 2. Re: Charts in FM12 vs FM11 - Layout objects too big
            sleepy62

            Yes, all styles removed. We have also considered going back to the FMP6 method of using strings of '"|" characters. Its looking very much like this is what we will have to do. Very sad. The addition of charts was such a big deal in 11. And although they've added a few new features in 12, this change to object characteristics has really ruined things for us. Just to illustrate the point further Ive attached a comparison of sizes between 11 and 12. The disaster here is that the object extends way up above the top of the actual chart, and in order for the object to render properly the top handles must be inside the summary part. So this does not work at all in 12. Its really quite crude compared to 11.

             

            Screen shot 2013-04-25 at 8.48.09 PM.png

            • 3. Re: Charts in FM12 vs FM11 - Layout objects too big
              mikebeargie

              Well, I'm not discounting your problem here, but I've seen a lot of benefits in filemaker 12's direction and interface. It certainly was a "your mileage may vary" kind of update for a lot of developers and a lot of pre-made solutions. The entire front-end rendering of layouts in filemaker 12 is different, as in it's now rendering layouts using a web-like html/css-like engine. While we gained a lot (curved corners, gradient fills, multi-state styles, etc..) with this new frontend, there are cases, such as yours, that seem to deal with a lot of frustration in change. Given the file format change though, this is the direction filemaker is going for the foreseeable future.

               

              Perhaps you need to start looking at alternatives to the native chart objects, and decide if the advantages you can realize from FM12 (IE ExecuteSQL chart data, long-term viability), are worth the time investment to upgrade. You can still do charting via a web viewer ( IE using google charts as a web service). It might also be worth it to invest in some consulting time from some industry experts that do consulting work (IE soliant, seedcode, etc..)

               

              Fortunately from my talks with filemaker, it still seems like they will be allowing licensing of 11 to continue for a while, which should give you plenty of time to work out a viable solution in the fmp12 format while still selling your robust 11 solution for now.