Are you saying you enabled MavLink 1.0 in the code and recompiled? If so, let's look at the code (GCS_Mavlink)....
0, <------------- load always zero!
battery_voltage1 * 1000, // mV
0, <---------- current always 0!
battery_remaining, // in %
0, // comm drops %,
0, // comm drops in pkts,
0, 0, 0, 0);
There's your problem (it's always zero cause it's not implemented yet), and considering you successfully compiled it, you have 2 choices: add a method to calculate the current youself (and resubmit to the devs--the spirit of open source :) ). or 2. you can add it as a bug if you really need it and see how the devs schedule it in for a version release. The again, if you implement it, I'm not sure if Mission Planner will read it (since it not implemented yet).
There is a bug report related to a scaling issue on battery_remaining from Andrew Fernie, which also adds "current" to the status. The code just got added to the repository a few minutes ago.
current will be added in the next planner version.