C / C++ / MFC

FirstPrevNext

Re: How: each doc/view in own thread (advanced) #realJSOP13-Jul-01 1:41 #realJSOP 13-Jul-01 1:41  I would probably create a thread that handles the TCP/IP connection itself, and when it has data for displaying in a view, would send a message to the approriate view. Each view would have to register itself with the TCP/IP thread so that the thread would know who to send the data to, and the thread would have to maintain a list of views' pointers that are registered with it. I think this might give you back your interface response because the views are now only displaying data that the TCP/IP thread tells them they have. Re: How: each doc/view in own thread (advanced) EiSl13-Jul-01 3:12 EiSl 13-Jul-01 3:12  Hello John, Thanks for reply!! This is already how it's working now. When a new document is created (OnNewDocument), a communication thread (WinThread) is started, which is using CAsyncSockets for communications. When data has to be printed, it is passed to the document. But... When I've have more than 3 documents active, and they generating quite a lot data, the main app starts become less responsive since all the documents/view updates are done under the hood of the main application thread. That was the reason for asking a thread handling doc/view archtecture. EiSl Re: How: each doc/view in own thread (advanced) #realJSOP13-Jul-01 7:29 #realJSOP 13-Jul-01 7:29  What kind of view are we talking about? CEditView? CListView? CFormView? Re: How: each doc/view in own thread (advanced) EiSl15-Jul-01 19:47 EiSl 15-Jul-01 19:47  Hello John, Does this really matters?!? Ok in case of a CFormView yes it matters. In my case we're talking about a read-only CEditView, but maybe this is changed to a CListView. Sincerly, EiSl Re: How: each doc/view in own thread (advanced) #realJSOP16-Jul-01 0:29 #realJSOP 16-Jul-01 0:29  You'd probably be better off with a CFormview with a CListBox in it. I'd be willing to bet that (with the CEditView) you are simply adding the newest message to the existing contents of the edit control. At first, performance is pretty good, but the longer the program runs, the worse less responsive the program gets. If you change to a list box, you have better control over how much data is contained in the control (you could limit it to say 1000 lines). With an edit control, you have to call SetWindowText with a string that is larger each time. This takes a lot of processing time (a lot more time than adding a single string to a list box). I would advise against using a list control unless you need multiple columns for some reason. A list box would be a better choice. Re: How: each doc/view in own thread (advanced) EiSl16-Jul-01 21:41 EiSl 16-Jul-01 21:41  Thanks for your answer! Most the time you read answer like: "better do this way" without a clear explaination why to do so. I've never thougth about the combination of CFormView with ListBox, because I was only looking to derivation of the View. Since it only accepts xxxView I was thinking about the ClistView or CEditView and have chosen for the editview. When everything is working fine I will take a look for changing that part, since it's quite easy to change. Happy programming! Eize Re: How: each doc/view in own thread (advanced) #realJSOP17-Jul-01 1:53 #realJSOP 17-Jul-01 1:53  I had the same problem in a previous project that I inherited. We were storing messages coming across a network in an edit control. These messages could be anywhere from 2-64k in length, and that we got approximately 150 messages per minute, and we were simply adding them to the edit control with no thought of the size of the string *in* the edit control. Performance slowed to such a point that the CPU utilization was pegged at 100% and we got so far behind in the message queue that the only recourse was to do a hardware reset. The really embarassing part was that our app was the only one running. LOL Anyway, we needed to have the edit control, so we changed the code buy only storing only the previous message in the edit control. Performance improved dramatically, and we regained keyboard control of the system. Good luck on your project. Re: How: each doc/view in own thread (advanced) Stephen C. Steel13-Jul-01 13:11 Stephen C. Steel 13-Jul-01 13:11  I don't think that a thread per doc/view is a good approach: there are a lot of complications, and it doesn't change the fact that only one thread can update the GUI at a time (the GDI calls are serialized). A much better approach, which I have used successfully in a couple of commercial applications, is to have one worker thread per doc, with the original GUI thread handling all the views. The worker threads can update each documents contents to reflect the input recieved via TCP/IP independently. You can run into some problems invoking window related functions from a worker thread because of the need to link C++ objects like CWnds with the associated Windows HWND (look up handle maps in the VC++ docs if you want the messy details). As long as the worker threads stick to updating the data in the CDocument derived class, you won't have problems. You may have to use critical sections or some other form of synchronization to stop the GUI thread from reading partially updated document contents though. I get around the handle map problem by defining a user message UM_UPDATE_VIEWS. The worker threads POST (not send) this message to the main window after changing the document contents. The main GUI thread processes this message, by calling CDocument::UpdateAllViews() for the CDocument derived object passed as a pointer in the LPARAM. This way UpdateAllViews() gets invoked by the main GUI thread, so there is no problem with handle maps. Stephen C. Steel Kerr Vayne Systems Ltd. COleDateTime 12-Jul-01 23:19 12-Jul-01 23:19  I try to create an application which composed by a dialog box. The first aim of this application is to connect an access database, so i put a button to do that. After the connection done, i want to compare a Date which is kept in an edit box in my dlg box to dates in my database. So, I declare m_dlgDate as a COleDateTime variable. When I run the application, even if the dlg date and one of the data date are the same, my application return an AfxMessageBoxwith the message "Not Good Dates". So, I would like to know if my declarations that's wrong or not?? gerald Re: COleDateTime markkuk13-Jul-01 8:12 markkuk 13-Jul-01 8:12  Perhaps you should use a DateTimePicker control instead of a text box? Is the messagebox a complaint from the MFC framework or a result of your own code? The COleDateTime and SQL timestamp both contain clock time in addition to date, you need to take care that it's masked out if you want to compare only the dates. Getting parts of the Platform SDK 12-Jul-01 23:15 12-Jul-01 23:15  Hi I need two files, psapi.h and psapi.dll. But according to the platform sdk setup,I must download over 80 meg for that. Since I am on a modem connection, the idea isn't appealing to me. Is there any other way of getting individual files? ftp.microsoft.com is down.... Re: Getting parts of the Platform SDK EiSl12-Jul-01 23:40 EiSl 12-Jul-01 23:40  Hello, I've got those file locally. (psapi.h,*.lib and .dll, total 27kB). It's way smaller than 80MB If you provide me an e-mail address for sending it to you, I will sent it. EiSl Strange implementation in one of the samples... EiSl12-Jul-01 23:12 EiSl 12-Jul-01 23:12  Hello all, Please take a look to one of the submitted code snippets, where the layout is recalculated: Link to sample in CodeProject: http://www.codeproject.com/docking/sizing_tabctl.asp Part of the code: void CMainFrame::RecalcLayout(BOOL bNotify) { CMDIFrameWnd::RecalcLayout(bNotify); CMDIFrameWnd::RecalcLayout(bNotify); } Question: Why does the author calls the same RecalcLayout twice ?!?! Thanks, EiSl CPropertySheet::RemovePage in MFC causes memory leak Serge Desmedt12-Jul-01 23:11 Serge Desmedt 12-Jul-01 23:11  Hi, In an application we've written we have a dialog based MFC application based on the CPropertySheet class. We are dynamically adding and removing pages while the the dialog is displayed. If the property pages we're adding and removing contain controls (i've tried it with buttons and treecontrols), then we have a memory leak: when I constantly add and remove pages, thus always returning to a same initial state, the application consumes more and more memory. It has nothing to do with the CPropertyPage derived objects themselves. I added several integer members to them, to make the memoryfootprint of the object bigger, but this doesn't cause the memory leak to be bigger. However, when I fill the dialog (by using the dialog editor of visual studio 6.0) with a lot of buttons, then the memory leak is getting bigger. I've added no functionality to the buttons, and not to the CPropertyPage derived class, except for one button with which I can add and remove pages to the CPropertySheet derived dailogbox. Thus it looks like MFC doesn't destroy the dialog template, or the controls on it. The page we're removing is NOT the active page. I've tried explicitly callling destroywindow on the propertypage that gets removed but this does not work neither. The only functionality the application has, is adding and removing CPropertyPage derived objects, so the memoryleak can not be caused by anything else. Does anyone have an idea what can be wrong and how to solve it Thanks, Serge Desmedt Re: CPropertySheet::RemovePage in MFC causes memory leak Tomasz Sowinski13-Jul-01 0:00 Tomasz Sowinski 13-Jul-01 0:00  Platform SDK documentation says that you shouldn't use PSM_REMOVEPAGE message (which is wrapped by CPropertySheet::RemovePage) during processing of some notifications: "A number of messages and one function call occur while the property sheet is manipulating the list of pages. While this action is taking place, attempting to modify the list of pages will have unpredictable results. Accordingly, you should not use the PSM_REMOVEPAGE message in your implementation of PropSheetPageProc or while handling the following notifications and Microsoft Windows messages: PSN_APPLY, PSN_KILLACTIVE, PSN_RESET, PSN_SETACTIVE, WM_DESTROY, WM_INITDIALOG" Tomasz Sowinski -- http://www.shooltz.com Re: CPropertySheet::RemovePage in MFC causes memory leak Serge Desmedt13-Jul-01 5:33 Serge Desmedt 13-Jul-01 5:33  I'm not doing anything of the above. On the propertypage derived classes there is a button, which sends a message to the propertysheet derived class, who then deletes a page which is not the current active page, and without changing the active page (so PSN_KILLACTIVE and PSN_RESET don't get send). Neither is the dialog startinh or closing, so none of the other meddages get send to the propertysheet. Serge Desmedt Saving HICON to a file Deian12-Jul-01 22:45 Deian 12-Jul-01 22:45  Hello, I'm experiencing problems saving a HICON to an icon file. Can you give me an example of doing that? Why not delete the CSingleDocTemplate ndkk12-Jul-01 22:01 ndkk 12-Jul-01 22:01  I build a SDI project.when the application had exited ,I found memoy leaks detected.The CSingleDocTemplate hadn't been deleted.Someone can tell me what will cause this.Thanx. Problem in RegQueryValueEx Yamuna12-Jul-01 21:35 Yamuna 12-Jul-01 21:35  Hi , I try to query a value from a remote registry using RegQueryValueEx.But I get an error code which says RPC_S_INVALID_BOUNDS.I tried changins my buffersize from small to large values but to no use.Can anyone please tell me the solution? Thank You, Yamuna.E. Yamuna.E. ByteBuffer 12-Jul-01 21:12 12-Jul-01 21:12  Hi all, I have a class to print individual pixels on a labelprinter. My barcodes are great but I would also like to print images and/or text. For this purpose I had the idea to create a CDC, place all my bitmaps and text in that cdc and then to convert it to a byte-buffer which I could send to the printer. Why bytes? Because the labelprinter only takes bytes and each byte represents 8 black/white pixels. I (think) cannot send the bytes from a cdc directly because I also need to send control codes to the printer to indicate newlines/formfeeds/margins... Any ideas on how to convert the CDC to a BYTE-buffer that suits my needs? Other ways to solve this are also greatly appreciated. Re: ByteBuffer Tomasz Sowinski13-Jul-01 0:20 Tomasz Sowinski 13-Jul-01 0:20  Seems that you need to create a DIB section, select it into DC, perform drawing, then convert the DIB bits to format accepted by your device. CodeProject has an article describing the wrapper class for dib sections - search for 'DIBSection wrapper' Tomasz Sowinski -- http://www.shooltz.com Scrollview & Zoom 12-Jul-01 20:14 12-Jul-01 20:14  I am developing an application which has a Scrollview - derived Control. Using the normal drawing functions i´m drawing into this DC. With the API ::SetWorldTransform i´m zooming in and out. Works perfectly until now.. the only problem i have got is that i would like to center the whole shista when i´m zoomin in and out. I´ve tried a couple formulas.. and didn´t get it going to set the scrollbars correctly.. so that i can zoom in and out and stay in the middle of the document. (the scrollbars get smaller if i´m zoomin...) Another problem is that i would like to center the pic in the view (when the zoom - factor is so small, that i don´t need the scrollbars. I hope at least some of you could understand my question... and i hope someone could help me out. thanx in advance the visual c student Re: Scrollview & Zoom Tomasz Sowinski13-Jul-01 0:14 Tomasz Sowinski 13-Jul-01 0:14  Another problem is that i would like to center the pic in the view (when the zoom - factor is so small, that i don´t need the scrollbars. CScrollView has an undocumented protected data member m_bCenter that does exactly that. Tomasz Sowinski -- http://www.shooltz.com Caller ID Vishnu Vijayan12-Jul-01 20:01 Vishnu Vijayan 12-Jul-01 20:01  We are using NT and dialogic board. I am interested in getting the callerid using TAPI. Could you explain it? We have the caller id enabled in the exchange and also with our telephone. We could get the caller id using a sample dialogic program ( the dialogic program uses dialogic api's whereas we are looking for a TAPI based solution). Now if you could explain it, it would be great. Thanks P.V.V. Re: Caller ID Michael P Butler12-Jul-01 22:49 Michael P Butler 12-Jul-01 22:49  Firstly do you have a TAPI Service provider for the dialogic board? If not then you won't get very far. Basic overview ----------------- Initialise TAPI with lineInitalizeEx Open the device with lineOpen When you receive the LINE_CALLINFO message make a call to lineGetCallInfo. The CallerID is in the LINECALLINFO structure. sCallerID = (LPSTR)((DWORD)m_lpCallInfo+ (DWORD)m_lpCallInfo->dwCallerIDOffset); http://www.julmar.com/samples.htm has some source code that might help.

Last Visit: 31-Dec-99 18:00     Last Update: 18-Apr-24 0:35 Refresh ᐊ Prev1...18181181821818318184181851818618187181881818918190 Next ᐅ

General    News    Suggestion    Question    Bug    Answer    Joke    Praise    Rant    Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.