|
I'm using an html control in my Smartphone2002 application as an output window (so html formatted text is continually being written to it)
My problem is that the control sometimes seems to wait for 3 or 4 lines to be "written" before updating it (which isn't much use when I want a real time update)
Is there something I need to do to force the control to always refresh as soon as I add the text?
--
Help me! I'm turning into a grapefruit!
|
|
|
|
|
You have to send a DTM_ENDOFSOURCE message to make sure that the text is complete. I think that you are depending upon a lateral behaviour of the control that is partially rendering your text. You have no control on its internal buffers and how they are flushed. So I think there is no "nice" solution to this problem.
|
|
|
|
|
Hmm, that was what I was suspecting.
Sadly I need to be able to continually update the text while the app is running. Sending the ENDOFSOURCE message means that the control no longer accepts any more input 
--
Help me! I'm turning into a grapefruit!
|
|
|
|
|
benjymous wrote:
Sending the ENDOFSOURCE message means that the control no longer accepts any more input
Maybe you can work around it. Here is an idea: Set up a buffer where you will add the HTML text. Whenever you have a new text insertion, append it to your buffer, flush the control, and set its contents from the buffer. Maybe you can even try and control the vertical scrollbar, so that the lastest text is always displayed. If you want to avoid flickers, try SetRedraw.
|
|
|
|
|
Yeah, I think that's what I'm going to have to do.
There's an option to jump to a specific anchor, so I'll just write my buffer, followed by an anchor line to the control each time, then jump to that
--
Help me! I'm turning into a grapefruit!
|
|
|
|
|
Everytime I update a notification the notification beep goes off. Is there any flag to disable the notification beep on an update? Thanks.
Joshua Guy
Sonork ID: 100.9944
ICQ: 519642
Hotmail: JoshuaJGuy@hotmail.com
|
|
|
|
|
|
Thanks. I figured out another way.
In the control panel under sounds and notification you can enabled and disable sound for notification that are listed. I added to the registry an entry for my app based on it GUID and did not add the key for the name. I also set the key that tells it to play the sound to 0. Since there is no name it does not show up in the sound notification options giving the user the ability to enabled the sounds. I think this is the preferred approach because there are actually several OS notification that are in there but don't have names so they don't show up in the control panel. Also it won't interrupt an background audio playing. It's worked great for me.
Joshua Guy
Sonork ID: 100.9944
ICQ: 519642
Hotmail: JoshuaJGuy@hotmail.com
|
|
|
|
|
I am developing an application in evc++ on win ce.net.
I want to change font size of menu.
I have tried with onmeasureitem,ondrawitem handlers with
ownerdraw style ofmenus.
But still no o/p.
It draws only top level menu not submenu even dose not dropdown also.
So any help please. 
Mukund
|
|
|
|
|
Hi,
i have a function, which should open a serial Port. Now i wan't to open more than one port with that function:
HANDLE port1, port2;
PortInitialize(portname1, port1);
PortInitialize(portname2, port2);
with that function:
BOOL CPort::PortInitialize(LPTSTR lpszPortName, HANDLE hCommPort)
{
DWORD dwError;
DCB PortDCB;
COMMTIMEOUTS CommTimeouts;
// Open the serial port.
hCommPort = CreateFile (lpszPortName, GENERIC_READ | GENERIC_WRITE, 0, NULL, OPEN_EXISTING, 0, NULL);
.......
}
But unfortunately, the second port2 can't be opened. I think there is a conflict with the handles, because there should be a pointer on the address of the handle, but that's even not working.
Greetings,
Frank
_____ easySMS for pocket PC _____
www.Siedler-Net.de/WinCE/easySMS/
|
|
|
|
|
After CreateFile check this:
if(ERROR_FILE_NOT_FOUND == hCommPort)
{
}
|
|
|
|
|
|
Two questions:
Frank S. wrote:
HANDLE hCommPort
Shouldn't this be HANDLE& hCommPort ?
Are you correctly spelling the COM ports like COM1: and COM2:?
You are using the same code for CreateFile as I did. The only difference is that I opened only one port... Other than these, I have no immediate clues.
|
|
|
|
|
Hi, does someone know how can i detect the directional button presses in a Visual C++ Application. Thanks
|
|
|
|
|
The direction keys work like the standard keyboard keys VK_UP and the others...
|
|
|
|
|
ok, thanks 
|
|
|
|
|
Well, if you have a CListCtrl, you can use that function:
void CList::OnKeydownList(NMHDR* pNMHDR, LRESULT* pResult)
{
LV_KEYDOWN* pLVKeyDow = (LV_KEYDOWN*)pNMHDR;
// TODO: Add your control notification handler code here
if(GetAsyncKeyState(VK_UP))
{
......
}
Hope that helps 
Frank
_____ easySMS for pocket PC _____
www.Siedler-Net.de/WinCE/easySMS/
|
|
|
|
|
Has anyone got any experience of programming for the Symbian OS? If so what tools do you use, and can you recommend any books on the matter, in particular the Sony/Ericsson P800?
Andy
|
|
|
|
|
Download latest SDK (C++/Java/OPL/VB) from Symbian developer website. You will find many sample programs that can get you started quickly. I have used C++ SDK. It is highly object oriented and expected development style took sometime initially.
HTH,
Junkie
"* Code till death *"
http://www.askarya.com
|
|
|
|
|
Hi,
Is it possible to start a user mode process from a kernel mode driver?
Thanks in advance.
Shivpal
|
|
|
|
|
I want to disable all of the items in commandbar, but it doesn't seem to be working. Here's what I'm doing:
if (m_menuBarPtr)
{
m_menuBarPtr = GetMenu();
}
if (m_menuBarPtr)
{
MessageBeep(0);
UINT menuStyle = MF_BYPOSITION | ((m_currentBar == 0) ? MF_ENABLED : MF_GRAYED);
m_menuBarPtr->EnableMenuItem(0, menuStyle);
m_menuBarPtr->EnableMenuItem(1, menuStyle);
m_menuBarPtr->EnableMenuItem(2, menuStyle);
m_menuBarPtr->EnableMenuItem(3, menuStyle);
}
I've also tried setting ther m_menuBarPtr by using the return value of the CCeCommandBar::InsertMenu() function.
If you'll notice the
MessageBeep(0); call, I hear that beep when this code is encountered, indicating that I do indeed have a valid CMenu*, but the menu items are still active. According to the CE help, MF_DISABLED is not supported by CE (what an arbitrarily stupid f***ing decision on Microsoft's part), so I can't use it (although I did try it just to make sure, and of course, my app wouldn't compile with it included in the code).
Why does the interface stuff in CE suck so bad? Why is the documentation a complete waste of a CD? Why hasn't there been a decent book written for PPC2K2 development?
BTW, I also added this line in the constructor to CMainFrame
m_bAutoMenuEnable = FALSE;
------- signature starts
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
Please review the Legal Disclaimer in my bio.
------- signature ends
|
|
|
|
|
John Simmons / outlaw programmer wrote:
Why does the interface stuff in CE suck so bad?
Well, it really is not what you think. The menu visual element is not a menu, but instead a toolbar button. If you want to disable them, you have to know their IDs, which start at 0xF000 (yes, I had to go to MFC's source again).
So, to do what you want, here's a suggestion:
m_wndCommandBar.SendMessage(TB_ENABLEBUTTON, 0xf000, MAKELONG(FALSE,0));
m_wndCommandBar.SendMessage(TB_ENABLEBUTTON, 0xf001, MAKELONG(FALSE,0));
Intuitive, right?
|
|
|
|
|
Oh yeah "intuitive" is always a word I've associated with PocketPC coding.
Here's a new one for you though (or maybe not).
Taking your "they're just buttons" thing one step further, I decided to try also disabling the buttons on the commandbar with the same code. Since the buttons have their own ID's, I decided to try using those ID's in the command instead of the "0xf000" thing.
Well, they were disabled until the new toolbar was displayed, and then they re-enabled themselves. Hmmmm... I tried putting the enable/diable code into the OnUpdate... functions for those buttons, but that effectively made the buttons blink.
I also tried using 0xf004, 0xf005, and 0xf005 (three buttons), but they didn't get disabled at all that way.
Lastly, I tried just using indexes of 0, 1, and 2 - of course, that didn't work any better than the 0xf00n attempt.
As an aside, after the menu items are disabled, the last menu item is graphically truncated - instead of reading "Config", it reads "Con" and you can see one pixel's worth of the "F" in "Config".
Have I mentioned yet that I hate PPC2K2 UI development?
------- signature starts
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
Please review the Legal Disclaimer in my bio.
------- signature ends
|
|
|
|
|
John Simmons / outlaw programmer wrote:
Oh yeah "intuitive" is always a word I've associated with PocketPC coding.
That was an obvious joke (forgot the smiley, though). As a matter of fact, if you want to do anything serious about UI development for the PPC 2002, you gotta read the MFC source. And for two reasons: 1) the eVC help sucks and 2) it is incomplete, at best.
John Simmons / outlaw programmer wrote:
"they're just buttons"
I only figured that out some 10 minutes before posting the message. And being toolbar buttons may explain some of the bizarre functionality you are experimenting.
As for regular buttons, I think you need to access the underlying CToolBarCtrl object through GetToolBarCtrl(), just like I did in my last article on multiple toolbars. When you have a reference to that object, call EnableButton(nID, bEnable) where nID is the button ID and bEnable is the enabling / disabling BOOL.
John Simmons / outlaw programmer wrote:
Have I mentioned yet that I hate PPC2K2 UI development?
Not explicitly, but I did figure it out from your previous posts...
|
|
|
|
|
João Paulo Figueira wrote:
That was an obvious joke (forgot the smiley, though). As a matter of fact, if you want to do anything serious about UI development for the PPC 2002, you gotta read the MFC source. And for two reasons: 1) the eVC help sucks and 2) it is incomplete, at best.
Yeah I know.
João Paulo Figueira wrote:
As for regular buttons, I think you need to access the underlying CToolBarCtrl object through GetToolBarCtrl(), just like I did in my last article on multiple toolbars. When you have a reference to that object, call EnableButton(nID, bEnable) where nID is the button ID and bEnable is the enabling / disabling BOOL.
I already tried that, and I get the same behaviour as before (they disable for a split second, and then get re-enabled somehow.
I guess I'll keep pounding on it, but if you happen to run across anything, don't be shy about sharing it.
------- signature starts
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
Please review the Legal Disclaimer in my bio.
------- signature ends
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
