C / C++ / MFC

25-Oct-11 7:07

Just click on the Email link at the bottom of this message.

Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman

Splitter with fixed size

Dialecticus24-Oct-11 8:28

24-Oct-11 8:28

I have SDI application and two panes. I would like bottom pane to have fixed size (instead of top pane having it). When user moves splitting line bottom pane should maintain newly fixed size. When window is resized, so that there is no room for top pane, bottom pane should occupy whole area. When window is enlarged again bottom pane should occupy last fixed size (ie. enlarge to a certain point and then stay fixed). Standard CSplitterWnd does not have this functionality, and last pane is always expanded to the end, and all previous panes are fixed. I was searching here for appropriate splitter class, but no luck so far. Maybe I'm missing something obvious. Is there a ready made solution? How should I solve this problem?

App_24-Oct-11 9:04

App_

24-Oct-11 9:04

Does this help?

If not, more here on splitters.

Dialecticus24-Oct-11 9:30

24-Oct-11 9:30

In linked article there is no mention of fixing the size of particular pane. The only advantage of featured class is that it works on CDialog, and that it uses registry. I've checked all other splitting classes, but either required functionality does not exist, or I can't find it. Hence the original question.

TheGreatAndPowerfulOz24-Oct-11 9:51

TheGreatAndPowerfulOz

24-Oct-11 9:51

handle the WM_SIZE message in the parent class (parent of splitter), then size each splitter panel appropriately.

If your actions inspire others to dream more, learn more, do more and become more, you are a leader." - John Quincy Adams
You must accept one of two basic premises: Either we are alone in the universe, or we are not alone in the universe. And either way, the implications are staggering” - Wernher von Braun

Dialecticus24-Oct-11 10:04

Re: Solution: use CSplitterWnd::SetRowInfo

24-Oct-11 10:04

My current solution is a monstrosity of a workaround that includes CMainFrame::OnSize handler, and a class derived from CSplitterWnd that exposes "ideal" sizes (you can set them but can't get them), and reroutes TrackRowSize/TrackColumnSize to CMainFrame so that proper size fiddling can be achieved. I am not proud of it, but it seems to be working for now.

Goto_Label_24-Oct-11 11:18

Goto_Label_

24-Oct-11 11:18

First read Minimum size splitter

then try:

CSplitterWnd::SetRowInfo (horizontal)

Call this member function to set a new minimum height and ideal height for a row. The row minimum value determines when the row will be too small to be fully displayed.

When the framework displays the splitter window, it lays out the panes in columns and rows according to their ideal dimensions, working from the upper-left to the lower-right corner of the splitter window's client area.

void CMyFrame::OnSize(UINT nType, int cx, int cy) 
{
	if(::IsWindow(m_wndSplitter.m_hWnd) && ::IsWindow(m_wndSplitter2.m_hWnd))
	{
		m_wndSplitter.SetRowInfo(0, cy*2/3, 10);
		m_wndSplitter.SetRowInfo(1, cy/3, 10);

		m_wndSplitter2.SetColumnInfo(0, cx/4, 10);
		m_wndSplitter2.SetColumnInfo(1, cx*3/4, 10);
			
		RecalcLayout();
	}
}

CSplitterWnd::SetColumnInfo (verticle)

Call this member function to set a new minimum width and ideal width for a column. The column minimum value determines when the column will be too small to be fully displayed.

When the framework displays the splitter window, it lays out the panes in columns and rows according to their ideal dimensions, working from the upper-left to the lower-right corner of the splitter window's client area.
Example

void CChildFrame::OnSize(UINT nType, int cx, int cy) 
{
   CMDIChildWnd::OnSize(nType, cx, cy);

   CRect rect;
   GetWindowRect( &rect );
   if( m_bSplitterCreated )  // m_bSplitterCreated set in OnCreateClient
   {
      m_wndSplitter.SetColumnInfo(0, rect.Width()/2, 10);
      m_wndSplitter.SetColumnInfo(1, rect.Width()/2, 10);
      m_wndSplitter.RecalcLayout();
   }
}

CSplitterWnd::RecalcLayout

Call this member function to correctly redisplay the splitter window after you have adjusted row and column sizes with the SetRowInfo and SetColumnInfo member functions. If you change row and column sizes as part of the creation process before the splitter window is visible, it is not necessary to call this member function.

Re: Solution: use CSplitterWnd::SetRowInfo

Dialecticus24-Oct-11 22:48

24-Oct-11 22:48

Thank you for MSDN reference, but my goal has nothing to do with splitter's minimum size. The ideal solution would be the one that has different RecalcLayout algorithm that recalculates layout the way I want it, having in mind what panes have fixed size (until user changes it), and what panes should be resized when the window is resized. Currently only the last pane is resized (the rightmost, or the "bottomest"), and all previous are fixed. Along with RecalcLayout rewrite there should be an update in TrackRowSize/TrackColumnSize so that fixed panes remain fixed (unless the user is resizing one just now), and resizable panes get resized to compensate for current pane reconfiguration.

TheGreatAndPowerfulOz25-Oct-11 5:06

TheGreatAndPowerfulOz

25-Oct-11 5:06

I wonder if what you want to use is CDockablePane.

The MFC "Visual Studio" Project style (available in VS2010) demonstrates usage of the CDockablePane and has the behavior you're describing.

Dialecticus25-Oct-11 6:14

how to Add the help file in SDI Application

25-Oct-11 6:14

Funny this. I created project from VS template and tested it a bit. If you shrink the window to a minimum then left and right dockable panes will also shrink and will not grow back. Then I tried the same thing with Visual Studio itself and the same thing happens. Dockable panes shrink, but do not grow back. But at least we have middle area that takes all the non-fixed space.

If those dockable panes could be prevented from undocking, hiding, auto-hiding, and if they could be made without titlebars, so that they resemble another client area, then I would have something close to original idea. But without the panes growing back when there's available space.

sarfaraznawaz23-Oct-11 21:01

sarfaraznawaz

23-Oct-11 21:01

how to add the help file in an SDI Application i tried with this

::HtmlHelp(this->m_hWnd,_T(" WordRecovery.chm"),HH_DISPLAY_TOPIC,NULL);

Re: how to Add the help file in SDI Application

Richard MacCutchan23-Oct-11 22:38

Re: How to call the html help api

23-Oct-11 22:38

sarfaraznawaz wrote:
i tried with this

And what exactly happened?

[edit]
This article[^] may be of interest.
[/edit]

Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman

App_24-Oct-11 6:25

App_

24-Oct-11 6:25

MSDN says:

The following example calls the HH_DISPLAY_TOPIC command
to open the help file named Help.chm and display
its default topic in the help window named Mainwin.

Generally, the help window specified in this command is a standard HTML Help Viewer.

MSDN Example

HWND hwnd =
  HtmlHelp(
           GetDesktopWindow(),
           "c:\\Help.chm::/Intro.htm>Mainwin",
           HH_DISPLAY_TOPIC,
           NULL) ;

SetCurrentDirectory

sarfaraznawaz23-Oct-11 19:42

sarfaraznawaz

23-Oct-11 19:42

hi i have use the GetCurrentDirectory now i want to change the Directory with SetCurrentDirectory can any one explain with Example

thanks
SARFARAZ

Re: SetCurrentDirectory

tolw23-Oct-11 21:58

tolw

23-Oct-11 21:58

Well, the MSDN can, as always: SetCurrentDirectory[^]

If after reading the article something is still unclear, please post a detailed description (with source code showing what you have tried). It's hard to target a specific problem with a general question...

Re: SetCurrentDirectory

App_24-Oct-11 2:58

App_

24-Oct-11 2:58

#include <windows.h>
#include <stdio.h>
#define BUFFER_SIZE 200
 
int main()
{
  TCHAR infoBuf[BUFFER_SIZE];

  // Change accordingly to other path of your machine
  TCHAR lpPathName[200] = "c:\\";

  // get the current working directory
  if(!GetCurrentDirectory(BUFFER_SIZE, infoBuf))  printf("GetCurrentDirectory() failed!\n");

  printf("Your current directory is: %s\n", infoBuf); printf("Changing directory...\n");

  // set to current working directory
  if(!SetCurrentDirectory(lpPathName))  printf("SetCurrentDirectory() failed!\n");

  // do some verification...
  if(!GetCurrentDirectory(BUFFER_SIZE, infoBuf))   printf("GetCurrentDirectory() failed!\n");

  printf("Your current directory is: %s\n", infoBuf);

  // get and display the Windows directory.
  if(!GetWindowsDirectory(infoBuf, BUFFER_SIZE))   printf("GetWindowsDirectory() failed!\n");

  printf("Your Windows directory is: %s\n", infoBuf);

  // get and display the system directory.
  if(!GetSystemDirectory(infoBuf, BUFFER_SIZE))  printf("GetSystemDirectory() failed!\n");

  printf("Your system directory is: %s\n", infoBuf);
 
  return 0;
}

working with byte arrays

jkirkerx22-Oct-11 8:58

22-Oct-11 8:58

I understand now that the data I receive from a socket is a byte array.

But I don't understand how to pass the byte array to a function for further processing. Plus I'm not sure if I should leave it as a byte array, or try to convert it to a string, so I can extract data from it. I'm confused as to whether this buffer is a pointer to data somewhere else, and If I need to make a copy of it, before passing it to a function. When I pass it to a function, the data is lost.

Kind of tired of going around in circles here on this, and I need road map to head in the right direction.

I make my receive buffer
char recvbuf[256];

I get data
0x05 '' 0x54 'T' 0x53 'S' 0x65 'e'

And I try to pass it to a function for processing. Unless just extracting the info I need does not require a function. Suggestion?

void _process(char *pbuffer)
{
}

Chuck O'Toole22-Oct-11 9:35

Chuck O'Toole

22-Oct-11 9:35

I can't speak for your application nor what data you will be receiving from the socket. But if the data is a "protocol", that is, some well defined sequence of bytes with fields, flags, data, etc, then it is most likely that the information is "binary", that is, not all the data maps nicely into printable or viewable characters, all zero bytes comes to mind, your 0x05 example too.

C and C++ "string" variables, whether CString or std::string and their manipulation functions are not really tolerant of nulls intersperced in the data.

C# strings do allow nulls in the data and I have seen many a C / C++ programmer get totally confused by the idea of nulls in strings.

So, I'd say save yourself some future grief and use a byte array. Passing a byte array is no different than passing a char array other than some folks incorrectly equate "char array" with "string" in all cases.

jkirkerx22-Oct-11 15:46

22-Oct-11 15:46

Great Information!

In this case, the data being received are byte stream?

Header stuff, ServerName:WWW;Custered:false;NamedPipe:\\pipename;Version:1.5.02.23;empty space

Taking into consideration the thread below yours, I will make a copy of the buffer, and pass the copy to the function to fish out the server name, and version.

Thanks for looking at my post, your advice puts back on track.

jkirkerx

Albert Holguin22-Oct-11 12:02

Albert Holguin

22-Oct-11 12:02

Don't convert it to a string... that's a bad idea... extract whatever data bytes according to whatever API you happen to be using, then cast the converted bytes to whatever type they're supposed to be. As far as whether you need to copy the data before passing it, it depends on where you defined your recvbuff[] and whether it'll be used again, if the buffer is a local variable within your receive method, then it'll automatically go out of scope when the method is finished, so you should copy the data... also, if the buffer is to be used repeatedly (receiving multiple packets), then the data should be copied over to another buffer before moving on, otherwise it might be overwritten before it's used downstream.

jkirkerx22-Oct-11 15:51

22-Oct-11 15:51

The research I did made it sound like std:string was the swiss army knife or manipulation.

I used memset to copy the data, because I could not figure out how to use strcpy, the copy has the first 2 bytes, and stopped.

I still can't figure out why when I pass the data, I only get the first 2 bytes.

You wisdom gives me a map to use, so I can focus on the copy and pass, then I have to tackle the data extraction.

Thank you very much

jkirkerx

Richard MacCutchan22-Oct-11 21:46

22-Oct-11 21:46

You seem to be working at this from the wrong direction. The first thing you need to do is work out (or ask the sender) the exact format of the data you are receiving. All data read from sockets is presented as a stream of bytes, and without knowing the significance, format and values of each byte or group of bytes, there is no way you can do anything with the information you receive. Never assume that data is presented as a string unless you are certain that is how it has been sent.

Unrequited desire is character building. OriginalGriff

jkirkerx23-Oct-11 8:07

23-Oct-11 8:07

The sender is microsoft's sql browser. I discovered the return packet data using etherreal, and sending various request to it, until I got the reply I was looking for. Then I wrote the socket program. I have the data packets coming back from all the sql servers on the lan, and they all send the same format back to me. I just need to extract the server name and version number of sql out of the byte array.

Richard MacCutchan23-Oct-11 8:26