If you are still working on this nuclearBoot[^] bootstrap project... then you should forget about doing this from a MBR bootstrap. How exactly do you plan on mounting NTFS/FAT32/exFAT drives? Do you realize that you would need to implement your own filesystem parsers? At such a low level... you would be dealing with raw disk sectors unless you plan on parsing these file systems yourself.
If I were you I would take a look at BusyBox[^] and use that for your project. It can be customized to do everything you want...
1.) It is customizable and bootable.
2.) It can mount NTFS,FAT,FAT32,Ext2/3/4 and more...
3.) You easily could move/delete/backup files from your application.
4.) You could fill a drive with zeros by doing 'dd if=/dev/zero of=/dev/sda bs=1M'
5.) You could fill a drive with randomness by doing 'dd if=/dev/urandom of=/dev/sda bs=1M'
6.) Everything is open source! You could modify or improve the source code.
this my thread from here am calling the core class member function Repair(CString sz_path,HWND h_wnd) in this i have one more sub function.
when am trying to display message box in Repair function with handle
::MessageBox(h_wnd,_T("Please select a healthy movie file "),_T("Information"),MB_ICONINFORMATION);
it coming Active state but same thing which i do for the sub function saving (HWND h_wnd) it coming in inactive state this not getting close on clicking one time its take two to three click to get close
Help out of this .....
Accessing gui functions from more than one thread is not a good practice. A gui element (window/control) belongs to a process, and to a thread and a module inside that process. What happens in your case is that you have main gui with its message loop on your main thread, and your messagebox function starts another gui loop on the other thread and god knows what happens with focus management in this case, not to mention that a messagebox is meant to be modal and in your case it isn't!
You should ask the main (gui) thread to manipulate the gui for you by placing a job in its message queue and waiting for that job to finish. In windows you can do that by sending a message for example to your main window with WM_USER+XXX message. The main thread in your main window can handle the message and pop up a messagebox on the main thread. (Note: SendMessage() puts a message to the message queue of the thread of the window and block the execution of the current thread until the other (gui) thread executes the message. PostMessage() just places the message in the queue of the other thread and returns immediately.)
You can write a multithreaded MessageBox() function for yourself that can be called from any threads and does the thing I described above.
For longer gui tasks that must be performed from the middle of your worker thread code you should either use PostMessage() with a WM_USER+XXX message that brings up a modal dialog on the gui thread to do the job (and returns from the WM_USER+XXX message only after this), or if you can not perform the gui task immediately where you handle the WM_USER+XXX message then do this:
Use PostMessage() to send the job with its parameters to your gui thread to its main window, there you can do the gui related stuff and after it you can send the results to the worker thread somehow - for example by declaring a blocking message queue implementation in your worker thread. While the gui is working the worker thread can block on the blocking message queue waiting for the result of the gui task.
Before you start putting in some complicated inter-thread interactions to you program you should consider doing the gui job, and starting the thread only after this with ready-made parameters!
EDIT: You are parenting two popup windows that belong to different threads. This is already stinking, never seen such and wouldn't be surprised if that would be illegal. Use always one thread to create and manipulate gui objects!
EDIT: Popping up a messagebox from a thread at a random point is also a bad design even if it is well implemented technically. Redesing the use cases of your program!
am very new to MFC .
what i actually did ,i want explain you .
see i have different class UI cprogress here i am trying to update the progress bar according to some work is going on in back ground . this i did by creating thread in Cprogress class itself.in cprogress class m calling the core repair class, in repair class am sending the user define message for updating the progress ctl.when i want to cancel it am suspending the thread and trying to display the massageBox its appearing in inactive form it wont get exit on 1 click.the cancel event is in cprogress class it self.am used the postmessage(wm_destroy,0,0) to destroy the all the controls
This is how you have to implement some kind of parallel task on a thread with progressbar and cancel button: You setup the thread and start it to do its work. The worker thread posts progress updates to your gui by sending WM_USER+XXX message and an int parameter that is the progress, you should use PostMessage() and not SendMessage() to prevent your thread from waiting for your window to process the WM_USER+XXX message that sets the state of the progressbar. If you want to cancel the task from your gui thread then you should set a cancel flag for your worker thread and then you should poll this flag from your worker thread and stop doing the work if its set. Before exiting your worker thread you should send a WM_USER+YYY message to the gui thread indicating that the work has been cancelled.
i place the massage box in if(condition) this massage box getting inactive state.once i click the cancel the thread will suspended state if its true then i have flag and resume thread to release the memory and to finish the thread .every thing is working fine but the problem is with the message box not getting close with one click i dont know what do please help me out
Well, if you did what I recommended then I dont understand why is your code full of with suspendthread and resumethread, moreover this code isn't enough for us to point out whats wrong with your code, we need the surroundings of this messagebox code plus the codepiece from the thread that triggers this messagebox. If you have a modal messagebox in your program implemented correctly then it can become inactive only if the activation goes to the window of another application.
Another sidenote if you are using MFC: If you create gui elements (windows, etc..) from another thread its a problem because MFC installs hooks on newly created gui stuff and registers this-and-that to its internal structures that are not thread safe and you can cause all kind of diseases!
Then is_from_keyboard() below is better suited. It includes punctuation , spaces etc.
int is_from_keyboard(int ch)
if ( ch>31 && ch<128) return1;
cout<<"The ASCII character -> "<<ch<<" ("<<(int)ch<<") <- is from the keyboard. \n\n";
cout<<"The ASCII character -> "<<ch<<" ("<<(int)ch<<") <- is NOT from the keyboard. \n\n";
i am having a combobox (created through resource), and through code, i am updating the combobox with a list. for example, i am filling with "Kir" and "K". if i use CB_SELECTSTRING to select "K", its always selecting "Kir".
if i use "Kj" in place of "K", then the selection between "Kir" and "Kj" is fine.
from msdn definition : It selects the first list item, if any, that begins with the characters in the specified text.
I construct a CRange object and then call CRange's function get_shapeRange() to get a CShapeRange object.
but it triggers an exception. (but it's OK to call another function get_InlineShapes) I have no idea why it triggers an exception.
does anyone knows why? thanks.
By the way, I call this code in a keyboard hook function.
bool isRangeShape(__in CRange& oRange)
// I promise oRange is correct, because I can call
// like this oRange.get_InlineShapes()
// in word2010 it's ok,but in word2003 triggers an exception
// but corresponding VBA code works fun in word2003 (not fun, I'm sorry)// word2003 don't support this method, oh my god!!!
CShapeRange oShpRange = oRange.get_ShapeRange();
long lCount = oShpRange.get_Count();
if (lCount > 0)
I have one dialog box. I have picture control on that dialog. I'll draw two masks on the canvas using OnMouseMove functionality. one mask is completed, another one is incomplete mask (only a line drawn using pen). When I remove/delete the completed mask, incomplete doesn't get deleted but its not visible. How to show the line after removing the completed mask in MFC.
i am having n-number of points like p1(x,y), p2(x,y), p3(x,y), .... pn(x,y). All points lie on a single line.(either a curve or a straight line). i would like to find, using those points, whether that line is straight or not straight. i googled and tried some of the methods given in examples, (straight line equation, finding if collinear) but those are not working fine even for straight line also.
i am using visual studio 2008 with win32 (not MFC).
One way would be by using slope. Find the slope of the line corresponding to the first two points (y-coord of p2 - y-coord of p1) / (x-coord of p2 - x-coord of p1).
Find the slopes of the lines corresponding to all other points (with respect to the first point), say (y-coord of pk - y-coord of p1) / (x-coord of pk - x-coord of p1), where k varies from 3 to n.
All of these slopes should be within a reasonable tolerance band. And, since all of these lines pass through p1, they all would lie on the same straight line if they fell within the tolerance band.
The above would not work if the x-coordinates of p2 and p1 are the same (because denominator would be zero). In that case, you choose a point whose x-coordinate is unique as the reference point.
Not sure whether this is the most efficient way, but it certainly a way of achieving what you want.
You mean, that your slope value is 0.000002? This means that your line is almost horizontal. Your tolerance values would have to be at least 1/1000 or 1/10000 of your "average" slope value. Then, it would indicate that these points are on a straight line. (You need to use a "double" type to store these numbers, and a "float" may not suffice).
By the way, what is the purpose of this exercise? That purpose would in some sense determine the method of straight-line detection.
- Take the first and last points to build the 3D law of their straightness
- Define the fluctuation radius as "allowed error"
- All other points must lie in the "pipe" =>
=> any point projection onto the law(1) may not be greather as the radius(2)
They sought it with thimbles, they sought it with care;
They pursued it with forks and hope;
They threatened its life with a railway-share;
They charmed it with smiles and soap.
Last Visit: 31-Dec-99 18:00 Last Update: 7-Oct-15 8:24