|
Nope, need a little more idea of what you mean. The terms you use are broad enough that you could mean one of several things.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
I want to open a .html file via ShellExecute, but it has
warning. So I want to try use memory map file instead of
the file on disk, thanks your reply. 
|
|
|
|
|
Yeahhh - can't see that making any difference. What was the warning you got?
[edit]Also - i know of no way to tell an application (using ShellExecute, CreateProcess or whatever) to open a file using a memory mapped file rather than any other mechanism - the way it opens files is a design decision of hte application and likely hard-coded into it.[/edit]
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
|
ShellExecute opens shell items - objects that the shell is aware of. If you can make your memory mapped file visible to the shell (via a shell extension) you could make ShellExecute open it - but trust me, this is not something you want to do 
|
|
|
|
|
After searching around i still can't get the right way.
Firstly, since there are lots of web tabs, how can I determine the exact one's HANDLE?
Secondly, there are a lot of code involving COM and BHO to solve this problem, common on, I just need the current webpage's source code, I don't need and don't want to learn the architect of COM and BHO before I can solve this problem!
Can somebody give me some hints, source code provided will be more appreciated!
BTW, somebody told me I can get the url and socket-send-receive the source code. But that didn't work because the URl in the address toobar of IE sometimes doesn't reflect the exact page so the safer way is to try to find the source code in local disk or somewhere else in my own computer.
Thanks!!
Jack
|
|
|
|
|
A BHO will be the easiest to do this.
Visual Studio ATL COM project wizard does give you the option to create a BHO.
An instance of the BHO is loaded for each tab of the browser.
So you needn't worry about identifying the correct tab.
A BHO must implement the IObjectWithSite interface.
When the BHO is loaded the IObjectWithSite::SetSite function is called and the web browser control interface pointer is passed in.
You can retrieve the web page source using IHTMLElement::get_outerHTML.
«_Superman_»
I love work. It gives me something to do between weekends.
|
|
|
|
|
cs60089 wrote: I don't need and don't want to learn the architect of COM and BHO before I can solve this problem!
Let me rephrase that for you:
"I have a tin of pineapple chunks. I don't nned and don't want to learn how to use a tinopener before I can solve this problem!"
Iain.
Codeproject MVP for C++, I can't believe it's for my lounge posts...
|
|
|
|
|
As the dispute continues between me and doc/view, I'm posting my next rant/questions.
[The sample I'm talking about is simply the wizard generated SDI executable, without touching the keyboard. So the perfect default application in VS2005]
Ok, first off, How do I debug a document application, for example an SDI, When I click on "Save" from the menu, where does the command land? More importantly, How do I see it? Where should I keep the break point. just blows my mind.
Second, When you click on "save" it goes through Serialize() function [God only knows how it gets called], and when you check for "IsStoring()" that says true and hence..save. BUT, When I open a document, It doesn't go through the Serialize method. WTH?? It's been clearly said in the book. If "IsStoring()" is false, it means you are opening a document.
Serialize(CArchive& ar)
{
if (ar.IsStoring())
{
AfxMessageBox("Saving");
}
else
{
AfxMessageBox("Loading");
}
}
Third,
And on what basis, do these handlers exist in the file where CMyApp theApp object exists. Where is the handler for "OnFileSave"? Why is it not transparent? Why do they need to show only New & Open option here? Do you agree with me, they are least intuitive when it comes to Doc/View? 
ON_COMMAND(ID_FILE_NEW, &CWinApp::OnFileNew)
ON_COMMAND(ID_FILE_OPEN, &CWinApp::OnFileOpen)
Thanks.
|
|
|
|
|
grassrootkit wrote: Ok, first off, How do I debug a document application, for example an SDI, When I click on "Save" from the menu, where does the command land? More importantly, How do I see it? Where should I keep the break point. just blows my mind.
Look at the message maps - they tell you where the messages go. Also, pop a breakpoint on your Serialize method and look at the call stack - that shows you where the message has been routed.
grassrootkit wrote: Second, When you click on "save" it goes through Serialize() function [God only knows how it gets called], and when you check for "IsStoring()" that says true and hence..save. BUT, When I open a document, It doesn't go through the Serialize method. WTH?? It's been clearly said in the book. If "IsStoring()" is false, it means you are opening a document
The reason an open command might not land on your Serialize method is because you're re-opening the currently open document - that's certainly what I've found. MFC detects that case and performs no action (unless, I suspect, you've altered the document since you last saved it).
grassrootkit wrote: And on what basis, do these handlers exist in the file where CMyApp theApp object exists. Where is the handler for "OnFileSave"? Why is it not transparent? Why do they need to show only New & Open option here? Do you agree with me, they are least intuitive when it comes to Doc/View?
The handlers live with your app because you may have multiple documents and document types - the app attempts to determine what type of document you're opening before opening the document and asking it to load the file - even if you only have one document type and one document.
Yes, it can be obscure. The best way to approach MFC is to just go with the MFC flow and accept that it does loads of weird sh*t. Or try and work through a copy of MFC Internals[^]. And then accept that MFC's going to do what MFC does
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
|
Stuart Dootson wrote: Also, pop a breakpoint on your Serialize method and look at the call stack - that shows you where the message has been routed.
Hmm, as you see in my case, it will not get into the serialize method. So I cannot put a break point anywhere and so can't catch the call stack.
A the worst case would be the "Save". I do not find any message map for "save". It would have been much difficult if it malfunctioned during save, I do not have a visible handler and it doesn't go through Serialize method. It'd be clueless, but anyway no problem yet with Save command.
Okay now , I see the handler for "OnOpen" command. But as you know it did not get into serialize method, I cannot put a break point there. If I want to see where the control goes, which file should I open to put the break point? In short,where will CWinApp::OnFileOpen() be defined?
ON_COMMAND(ID_FILE_NEW, &CWinApp::OnFileNew)
ON_COMMAND(ID_FILE_OPEN, &CWinApp::OnFileOpen)
Please hold on till I get the book 
|
|
|
|
|
The SAVE message map should be in your doc class.
As I said, I found the serialize method is invoked when you open a different file than the one you currently have open (I saved a file called a.a then re-opened it - MFC detects that condition and doesn't re-open).
CWinApp is in the MFC source - I can't remember off the top of my head which file and I haven't got enugh battery to open VMWare Fusion (I use OS X normally) at thh moment Still - go into the MFC source directory and grep for OnFileOpen.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
Stuart Dootson wrote: The SAVE message map should be in your doc class.
Oops! You are right.
Stuart Dootson wrote: As I said, I found the serialize method is invoked when you open a different file than the one you currently have open (I saved a file called a.a then re-opened it - MFC detects that condition and doesn't re-open).
I knew my question was not clear this time.Sorry. Actually I understood what you said in your last reply. I was talking in context with the 0 size files. "Assuming I'm opening the 0 size file" and trying debugging, trying to catch the call stack. etc. Anyway helped enough already.
Stuart Dootson wrote: CWinApp is in the MFC source - I can't remember off the top of my head which file and I haven't got enugh battery to open VMWare Fusion (I use OS X normally) at thh moment Smile Still - go into the MFC source directory and grep for OnFileOpen.
Oh! okay No probs. You are clever to move out of windows .
|
|
|
|
|
grassrootkit wrote: I knew my question was not clear this time.Sorry. Actually I understood what you said in your last reply. I was talking in context with the 0 size files. "Assuming I'm opening the 0 size file" and trying debugging, trying to catch the call stack. etc. Anyway helped enough already.
(Back on AC now!) You're quite right - it doesn't bother calling serialize for zero byte files - makes sense, I guess.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
hello every one
I make an ActiveX using Flash.ocx, i didn't create a window for Flash control, just use windowless object(IOleInPlaceObjectWindowless).
and i use OleDraw() to draw the Flash content to my HDC:
OleDraw(pFlashViewObject, DVASPECT_TRANSPARENT, hDC, &rc);
Everything is good in the "ActiveX Control Test Container", the Flash content is drawn.
but when i use my ActiveX in Internet Explorer, the OleDraw() draw nothing!
the HRESULT is ok, but hDC is just white(i save it to a BMP file)! 
I test my ActiveX on some other browers(support ActiveX), they work fine too!
only IE has this problem! IE don't like an ActiveX(mine) OleDraw another ActiveX(Flash.ocx)??
Is it a security problem of Internet Explorer? (i mean: IE prevent calling OleDraw or something else from my ActiveX to Flash.ocx??)
i want to draw Flash content to my ActiveX's HDC, and use it on IE browser, is there any solution??
|
|
|
|
|
Hello everyone,
I’ve got a serious problem that is killing our product and requires an immediate solution. Our situation is CRITICAL!
We have implemented support for a real-time serial protocol in our Windows XP Embedded based device. It uses a regular 16550 based UART/COM port on the motherboard and the following settings: 19.2Kbps, space parity, one stop bit, and eight data bits. The COM port is configured with COMMTIMEOUTS = { 5, 0, 0, 0, 0 }. The machine contains a 1.6GHz Celeron M processor and 1GB or RAM, which is not completely used.
The protocol requires our embedded device to respond to a packet within 20ms so it is imperative that our process receive the packet from the kernel (serial.sys) as fast as possible. The end of a packet is identified by 5ms or more passing between bytes. We’ve implemented several different solutions using both synchronous and overlapped I/O and have determined that the most reliable way to get the data as fast as possible is to start up a read thread with real-time priority and invoke ClearCommError() at 5ms intervals while tracking the amount of data in the receive buffer with COMSTAT. cbInQue. When the amount of data does not change for 5ms we call ReadFile() to obtain it. This solution seems to work fairly well for a few minutes and then suddenly ReadFile() begins returning the data after 100ms or more instead of the 10ms-15ms it was previously. It’s also returning the data in non-contiguous fragments even though our serial line monitor shows that the data is being sent to our device in one solid block (that never exceeds 260 bytes and is usually 32-48 bytes). The only “solution” we’ve found so far is to shutdown and restart the process. We’ve even tried having the process close and reopen the port with no success.
I’ve considered modifying serial.sys to automatically handle packet reception at the device level, but I’m concerned that it wouldn’t solve the problem because it appears to be a latency issue coming from somewhere other than the driver. The protocol code is very large and complex so moving it into a driver is so undesirable that we will probably move to embedded Linux instead (if it’s necessary).
Please help!
Thanks,
Peni
|
|
|
|
|
Hi,
welcome to CodeProject. And, good first post!
first of all it is very ambitious to mention Windows, real-time and 5 or 20 msec all in one sentence.
I do have quite some experience with Windows serial ports, it is getting a bit rusty though. Amongst others, I did a serial protocol where overall bandwidth was most important, but so was latency time for the first message. So I did experiment with all the timeout parameters a lot.
The scheme you described seems rather complex, and makes me wonder how the hell you can ever test that to satisfaction as data can and will come in asynchronously with respect to your 5msec operations, which (1) may interfere with the driver's normal operation, and (2) may have some timing jitter.
BTW: how do you create that 5msec period?
Although you did describe a lot, I would want to know more, such as: Is it binary data, or text (8-bit or 16-bit)? How many bytes or characters would make up a single message? is throughput relevant, or just latency? why did you choose 19200 Baud? would it be possible to change the protocol? and the port's settings?
Also I wouldn't mind some background info, what it really is about; it tends to help me focus on the technical solution when I know what kind of application is involved.
Give me some more info, and I'll probably come up with a direction I would be inclined to take, to get something both simple and hopefully as reliable as Windows can offer.
Luc Pattyn [Forum Guidelines] [My Articles]
- before you ask a question here, search CodeProject, then Google
- the quality and detail of your question reflects on the effectiveness of the help you are likely to get
- use the code block button (PRE tags) to preserve formatting when showing multi-line code snippets
|
|
|
|
|
Hi Luc,
I don’t have control over the protocol specification so I can’t change things like the baud rate, word size, parity, or timing constraints. It is an 8-bit binary protocol so any value in the range [0, 255] may be transmitted or received. It’s an old industry standard protocol used for communication between industrial devices. Unfortunately I can’t go into much detail because I’ve signed an NDA.
The only way I can determine where one packet ends and the next one starts is by measuring 5ms or more between two characters. If there is no next packet then I just need to detect when 5ms passes after the last character is received. This is usually easy to manage because packets are typically transmitted in bursts with less than 1ms between characters.
If there were a way to configure Windows (or serial.sys) to return the data it has received in a more timely fashion to the process waiting for it then I’d have a solution. Ideally, I’d like to be able to rely on the driver to detect the 5ms inter-character period set with COMTIMEOUTS, but trying that resulted in my process receiving the data at least 80ms after it arrived at the PC. It was more like 100ms on average.
|
|
|
|
|
Hi,
the protocol being fixed is very unfortunate; protocols should serve both parties involved, not used one, and receiving is much more difficult than transmitting, you figured that out yourself by now.
AFAIK the Windows serial driver's timing is based on the system timing, which in Windows leaves much to be desired. And all pre-empting, sleeping, and timeouts are based on a single clock which ticks at some 16 msec, the number may vary but AFAIK it never is down to the msec region. I wrote an article on timing from the .NET perspective, it may provide some insight; and if you happen to have .NET installed, you may run the app for some experiments.
Here are two ways for you to go and probably get better results than what you have now:
1. forget all timeouts, just start polling, i.e. have one thread dedicated to reading one byte from the serial port, zero timeout, create your own timeout (1, 2 or 3 msec) with a multimedia timer. That way you should be able, if system load by other processes and threads allows it, to
detect the absence of new characters for an interval of 5 or 6 msec. I would not recommend doing anything other to the serial port than just reading the data byte amd/or the status, changing the status might introduce extra phenomena.
2. the "hard" way: insert another device, micro-controller based, no OS required, that deals with the incoming bytes, and turns them into text-oriented characters with a proper and unique end-of-message marker (could be as simple as hex text, so each incoming 8-bit becomes two hex digits at a higher baud rate, detect end-of-message by timing and send an extra ASCII CR. Then ask the Windows serial driver for a line of text, it knows how to handle a single end-of-line marker, and should work swiftly (i.e. as swiftly as MS stuff can).
Both of the above still make you depend on the limited predictability of Windows stuff.
I have no idea how critical it is to you not to miss a single message...
final remark: do you know anything about the control lines, are they alive, i.e. is the other side signaling start and end of message using one of them. If so, you might poll the line and only launch a read when you already know the data has been received.
Luc Pattyn [Forum Guidelines] [My Articles]
- before you ask a question here, search CodeProject, then Google
- the quality and detail of your question reflects on the effectiveness of the help you are likely to get
- use the code block button (PRE tags) to preserve formatting when showing multi-line code snippets
|
|
|
|
|
Hi Luc,
The solution I’m using now functions in pretty much the way you suggest. I have a read thread with real-time priority that polls for the presence of received serial data by calling ClearCommError(). After this polling loop detects that no new data has arrived for 5ms it calls ReadFile() to obtain and process the data. Prior to this implementation I was invoking ReadFile() and appending new data to a buffer until ReadFile() returned no data for 5ms (or more), but this solution didn’t perform quite as well as using ClearCommError() to poll for the received data size. The protocol also does not use any modem control signals so I can’t use them to detect when data has arrived.
Unfortunately I don’t have the option to add new hardware to the device or I would definitely offload some of the protocol support to a microcontroller. I could also add it to a dedicated Windows driver since the serial device will always be an integrated 16550 compatible USART, but I don’t have enough time right now divide the protocol implementation between a driver and the user mode process.
I found that reducing the time quanta given to each thread in the system provides just barely enough response time to make the protocol implementation function under typical conditions, so the implementation I have now does not satisfy the protocol specification but it does work in typical real-world conditions. Hopefully it will satisfy our needs until a better solution can be implemented.
Thanks for the fast feedback and all your help. The information I have received from everyone in response to my post has been invaluable.
|
|
|
|
|
Luc Pattyn wrote: first of all it is very ambitious to mention Windows, real-time and 5 or 20 msec all in one sentence.
Welcome again in the CP's memorable quote list [^].
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
PeniWize wrote: This solution seems to work fairly well for a few minutes and then suddenly ReadFile() begins returning the data after 100ms or more instead of the 10ms-15ms it was previously
That's probably because some other thread is getting a time-slice instead of your responder thread. You could try marking your thread[^] with a time-critical priority in an attempt that it isn't interrupted.
However, a WIndows XP embedded time-slice (aka thread quantum) is around 90-100 milliseconds[^] which means that if you let any thread have processing time instead of your, you will not be able to respond to events in that 90-100ms window. That is why Windows XP (even the embedded version) is not a real-time operating system - you cannot deterministically respond to events within a small time-frame.
You could try reducing the thread quantum[^], but you can't get it below about 30ms.
PeniWize wrote: The protocol code is very large and complex so moving it into a driver is so undesirable that we will probably move to embedded Linux instead (if it’s necessary).
A driver was what I was going to suggest - but embedded Linux is a good option so long as it has a real-time kernel[^].
Good luck!
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
Hi Stuart,
Thanks for the feedback. It has given me some good leads. I forgot to mention in my post that my process is high priority and its serial I/O thread is real-time priority. Do you know of anything else that I could do to encourage the serial device driver or Windows kernel to return the packets to my process more quickly?
|
|
|
|
|
Remove as many other Windows processes as you possibly can - services you don't need etc.
Tune the thread quantum to as small a value as you can.
The trouble is that the Windows scheduler gives processes a full time slice once they've started, even if your process suddenly gets data. That means that there is always the chance that some other process might be running when your data arrives. You have real time timing constraints, which means you need to design a real time solution - and Windows isn't real time capable.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
. These aren't passing through serialize method - a great finding 
