ExpansionSlot01 V19 Taskbar Problem

[max982]

So here is my problem, i got it to work, but it's like f*cked up, i just wanted some help because i'm haveing headaches of the taskbar...

void CWndSlideBar::OnLButtonDown(UINT nFlags, CPoint point)
{

	MouseLocation = point;
  SetCapture();
}
void CWndSlideBar::OnMouseMove(UINT nFlags, CPoint point)
{
  CRect rectRoot = m_pWndRoot->GetLayoutRect();
  CRect rectWindow = GetWindowRect();
  int FixedY = rectWindow.top;
  int FixedX = rectWindow.bottom;
  int yLimit = rectRoot.bottom - 65;
  
  //Move54 = (MouseLocation.x - point.x);

  if(FixedY != yLimit)
       FixedY = yLimit;

  if(FixedX < rectRoot.bottom - 65)
	  FixedX = rectRoot.bottom - 65;
  else if(FixedX > rectRoot.bottom - 15)
	  FixedX = rectRoot.bottom - 15;

  int diff = (point.x) - (MouseLocation.x);
  FixedX += (diff);	  

  //if(g_bKeyTable[0x01] && IsPush())
  //{
    CPoint point1( FixedX , FixedY );
    Move( point1 );
	//g_bKeyTable[ dwHotkey[i] ] = 0;
  //}
  
	CWndNeuz::OnMouseMove( nFlags, point );
}

As you see here, i wanted to do my own way to move it, and as the Capture thingy didn't work, i used my way to..

So the problem is here

  int diff = (point.x) - (MouseLocation.x);
  FixedX += (diff);

I hope that you guys will help me, i'll be soon releasing my taskbar after finishing all of it. And here is a lucky picture, using that code.


Thanks for helping.

[Jopsi332]

look at your pn box for this.

[xMootie]

Flag the window style with WBS_MOVE, then restrict movement by overriding "CWndBase::SetWndRect"...

[Jopsi332]

Originally Posted by XorLethal

Flag the window style with WBS_MOVE, then restrict movement by overriding "CWndBase::SetWndRect"...

Hrlped himalready.but in wndbase where he move and change the rect with stops etc. Working already

[adeilson123]

Originally Posted by XorLethal

Flag the window style with WBS_MOVE, then restrict movement by overriding "CWndBase::SetWndRect"...

I already did it move into the position x e blocked the y, but
does not have a limit of x (left or right) for him to go, so it goes until the end of the flyff screen

[Jopsi332]

Originally Posted by adeilson123

I already did it move into the position x e blocked the y, but
does not have a limit of x (left or right) for him to go, so it goes until the end of the flyff screen

Just check the actual point and block with if

[Rhyder`]

can you post it here the slidebar source code?

[Crowley™]

Wäre nett wenn wer schreiben würde wie der Error zu fixen geht oder ob er gefixed ist? Oo
mfg. Crowley

[Unleashed!]

Originally Posted by adeilson123

I already did it move into the position x e blocked the y, but
does not have a limit of x (left or right) for him to go, so it goes until the end of the flyff screen

As Lethal already said, override your CWndBase::SetWndRect and add something like this (Just for example, don't now the real var-names right now, and you should calculate the x-coord by substracting the width of the taskbar + the width of the new slotbar, to make it "floating" right, means you wont get problems with users using other resolutions then you do):

if(x < g_Neuz.GetWndRect().right - 500) return;

[adeilson123]

Originally Posted by Unleashed!

As Lethal already said, override your CWndBase::SetWndRect and add something like this (Just for example, don't now the real var-names right now, and you should calculate the x-coord by substracting the width of the taskbar + the width of the new slotbar, to make it "floating" right, means you wont get problems with users using other resolutions then you do):

if(x < g_Neuz.GetWndRect().right - 500) return;

this is no longer necessary already for more than a week since I made him move properly

[Rhyder`]

Originally Posted by adeilson123

this is no longer necessary already for more than a week since I made him move properly

Can you post your code here of your Expasionslot?

[max982]

Originally Posted by jayjei14

Can you post your code here of your Expasionslot?

He won't, because, he, jopsi and me are using the same, and we won't post it right now, it's be on the next source update.