Skip to main content

Awesome Pie Charts with FoxCharts in zero time

If you haven't been trying out the VFPX project FoxCharts , or you tried but were a little frightened by how to implement it, here's some code that I wrote up quickly to build a nice little pie chart.

I call it GenPie and it gets called with any table and it will summarize it for you.

DO GenPie with "issues","cstatus","1","","Count of Issues"
or

DO genpie WITH HOME()+"SAMPLES\DATA\ORDERS","to_country","order_amt","","Orders"

The code essentially creates a form, drops FoxCharts on it and then uses a built-in cursor to create the chart. You can also pass it a Filter (before the title) and the starting color (in RGB).

DO genpie WITH HOME()+"SAMPLES\DATA\ORDERS","to_country","order_amt","","Orders",RGB(255,150,255)

Here's a sample:


LPARAMETERS tcTable,tcDirField,tcSizeField,tcFilter,tcTitle,tnStartColor
PUBLIC ox
ox = CREATEOBJECT("form")
IF EMPTY(tcTitle)

tcTitle = tcTable
ENDIF
ox.newobject("foxcharts","foxcharts","foxcharts")
ox.foxcharts.width = ox.width
ox.foxcharts.height = ox.height

IF EMPTY(tcFilter)
tcFilter= ".T."
ENDIF
SELECT &tcDirField,CAST(SUM(&tcSizeField) as numeric) as ntotal,COUNT(*) as ncnt FROM (tcTable) WHERE &tcFilter GROUP BY 1 INTO TABLE x

ox.foxcharts.sourcealias = "X"
ox.foxcharts.fieldxaxis = tcDirField
ox.foxcharts.visible = .t.
ox.foxcharts.ChartsCount=2
ox.foxcharts.fieldvalue1 = "ntotal"
ox.foxcharts.fieldvalue2 = "ncnt"
ox.foxcharts.Legend2="# Orders"
ox.foxcharts.Legend1="Total "
ox.foxcharts.ChartType = 1
ox.foxcharts.FieldLegend = tcDirField
ox.foxcharts.fieldcolor = ""
ox.foxcharts.colortype = 3
IF EMPTY(tnStartColor)
    tnStartColor = RGB(255,0,0)
ENDIF
ox.foxcharts.color1 = tnStartColor

ox.foxcharts.Title.Caption = tcTitle
ox.foxcharts.SubTitle.Caption = "Pie"
ox.foxcharts.yaxis.Caption=tcTable
ox.foxcharts.FontName = "Verdana"
ox.FoxCharts.ShowValuesonShapes = .T.
ox.foxcharts.DrawChart()

ox.foxcharts.visible = .t.

ox.show()

*!*    logif = _SCREEN.system.Drawing.Imaging.ImageFormat.Bmp
*!*    ox.foxcharts.oBmp.Save("x1.bmp",logif)


It's really easy and even though there are tons of options with it, this piece of code may make it a little easier to work with. If you notice the commented piece out just above, you can easily save the output as a bitmap.

FoxCharts totally rocks!

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...