I suppose you used two CustomDataSource classes in you're Gantt:

One good side effect of all this (I was hopping this would come around sooner or latter) : Completion works fine now on GraphCtrl

This works (at least when modifying it thriugh the layout designer) : maybe a Refresh() is missing somewhere
Normaly the updateSizes() method recalculates all the internal sizes taking into account the margins but it is for internal use and is called by Refresh()
Question : When you resize you're app, all is recalculated so the new margin values should be taken into account : does this work for you ?

	gantt.SetTopMargin(1).SetLeftMargin(1).SetBottomMargin(1).SetRightMargin(1);

This work in progress, it is mearly at start point : I intend to use it to enable things like selection (draw the point with a different style : highlight for example)

Hello Pradip,
This is either upp version that needs update or a memory corruption du to my latest modifications...
If it doesn't disapear with an upp update, don't bother, it's probably the same problem I'm tracking with my delete bug.

Sorry for this I published it to soon

just need to find out how to adjust the margins

	class BlankAreaElement : public GraphElement
	{
	public:
		typedef BlankAreaElement CLASSNAME;
		typedef GraphElement _B;

		BlankAreaElement() {}
		
		virtual ~BlankAreaElement() {}
		virtual void PaintElement(Draw& dw, int scale) { /* do noting */}
		virtual void SetElementWidth(int v) { _width = Upp::max(v, 3); }       // --- REMOVE THIS lINE ---

	private:
		BlankAreaElement( BlankAreaElement& p)  {}
	};

For the rest, I have no idea. I will check tonight

I have no idea why this was here and it is useless ( just checked, it's been around for years 6.5 years LOL ), I am removing it from the code base

For the rest, if you send me the code of you're GanttCtrl (and only that) it would be easier

bool IsHoliday(Date) 

One suggestion:
CustomData::Intersects and CustomData::Contains deal with bounding box of the data point. In some situations the bounding box depends on screen coordinates, please consider this.

One suggestion:
CustomData::Intersects and CustomData::Contains deal with bounding box of the data point. In some situations the bounding box depends on screen coordinates, please consider this.

I did a quick check on you're code, and after only renaming what needed to be renamed and commented the code for which I didn't have the data types, all compiled and works fine:
grid and axis are draw as you wan't and only Y axis is inverted.
I uploaded the modyfied code
So maybe it's the app code that modifys the configuration ?