|
You're right! Sometimes I have the feeling that MFC 3.0 for CE is really a half-baked and, in some points, a poorly implemented library. This kind of things just makes me wonder how fast the MFC team had to adapt the library for CE. Way too fast.
|
|
|
|
|
I am running Windows CE.
I want to trigger a function every 30 minutes. I understand that this can be done by using timers. But a timer object needs DispatchMessage() function for TimerProc() to get called.
Is it possible to provide a message loop in a windowless DLL? If yes, where should the message loop be defined?
(I tried providing a message loop in the DLL but the DLL started showing strange behavior. Is it at all possible?)
Windows ce does not support Timer Queues or Waitable timers. Is there any other option?
Any suggestions would be highly appreciated.
Thanks,
Ruchika
|
|
|
|
|
Another option would be to use a thread. Worker threads do not need a message loop and you can control their timing with equal (if not greater) accuracy. The code would look something like this:
BOOL bLoop = TRUE;
while(bLoop)
{
Sleep(30*60*1000);
}
Please note that this code might not be the best for battery saving purposes.
|
|
|
|
|
Thank you so much for the suggestion.
I am leaning more towards not adding a background thread mainly becz I already have three threads in my module. So, I am thinking of modifying one of the threads that I have to wait for RETRANSMIT_TIME, do the job and again wait.
Ruchika
|
|
|
|
|
Hi Guys,
Not sure if this is the correct message board for this issue, but here I go anyway:
I'm attempting (unsuccessfully) to Sync my Compaq IPAQ 3835 to my desktop (DELL GX260) at work. After installing ActiveSync 3.5, I am instructed to "Get Connected", ie make a connection from my Pocket PC to my Desktop PC. The problem is that this connection always fails. The PC doesn't recognize my device, so a connection can't be created.
Does anyone have any trouble shooting tips for me?
Any help would be appreciated
Thanks
Nick
|
|
|
|
|
Missing info:
1-What is your desktop OS and version?
2-What connection method (serial, USB, Bluetooth, IR)?
To try: ActiveSync 3.6 - download it from Microsoft web site.
Good luck!
João Paulo
|
|
|
|
|
OS- NT 4.0
Connection Method- Serial
Sorry about that. Thanks Joao
Nick
|
|
|
|
|
nicholas.gionfriddo wrote:
Connection Method- Serial
Check if there is another application accessing (or trying to access) the COM port you are using. Check for modem drivers, for example. ActiveSync will not work through the COM port if it is already opened.
Good luck!
João Paulo
|
|
|
|
|
João Paulo Figueira wrote:
application accessing (or trying to access) the COM port
Joao,
I don't have a modem running on this compu. Also, when the connection to the PocketPC fails, a pop-up shows that my port (COM1) is available.
Are there other ways I can check my Port availability?
Thanks for the help
Nick
|
|
|
|
|
nicholas.gionfriddo wrote:
Are there other ways I can check my Port availability?
 I'm not sure... NT 4.0 is remote history for me.
Try connecting to COM2. Also check for other software that might be hooked into your COM1 (it can be anything...) 
Good luck,
João Paulo
|
|
|
|
|
I´m having a problem when a try to load:
(*pArchive) >> m_nId;
Do you have to do some kind of cast...?
|
|
|
|
|
What kind of problem (compile-time or run-time)? Normally you use the CArchive object as a reference, not as a pointer, but I cannot see why this should cause any problem.
|
|
|
|
|
It´s run-time error... "An attempt was made to access an unnamed file past its end"
|
|
|
|
|
The only reason I can think of is that you are trying to read more than you wrote to the file. I always try to make the serialization code symmetrical, i.e. for each insert I write an extract. This has worked seamlessly for me.
|
|
|
|
|
Has anybody used serialize... Some code examples would be good.
Thanks!
|
|
|
|
|
PocketPC 2002: works just like the desktop Win32 version -- CFile and CArchive.
|
|
|
|
|
Hi!
I can't get the activesync to work?
I create a project in eVC++ and start Desktop Handheld PC Pro Emulation
But it wont work the eVC++ says that activesync must be installed??
I installed the hole package Microsoft eMbedded Visual Tools 3.0
Anny suggestions on what might be wrong?
/Jarek
He believed the commercials that said drink beer, get laid
but at closin' time he was alone, he didn't get paid.
Last night his lover was a razorblade..
"Dan Reed song Mix it up"
What do you want to patch today?
|
|
|
|
|
I had a similar problem with the PocketPC 2002 emulator. It is documented somewhere in MSDN that in order for the connection between eVC and the emulator to work, you must have a working and connected network card with the TCP/IP protocol. Well, if you don't have one, you can always install the Microsoft Loopback Adapter. Its is a dummy software-only network card driver that will allow you to work with the emulator. It should have been delivered in your OS installation. You can install it through the Hardware Wizard in W2K, or similar in other OS.
Good luck,
João Paulo
|
|
|
|
|
Thank you!
I have a small Network at home 3 computers so it can't be that
I dowmloaded the newest Activesync from MS but it wont help?
I think I have to get a good book about the eVC++ or RTFM once again.
/Jarek
He believed the commercials that said drink beer, get laid
but at closin' time he was alone, he didn't get paid.
Last night his lover was a razorblade..
"Dan Reed song Mix it up"
What do you want to patch today?
|
|
|
|
|
When i press the X of my aplication, it doesn´t kill it... It´s a kind of minimize. Shouldn´t it pass througth the destructor.
|
|
|
|
|
PocketPC 2002? Yeah, it does not close your app unless it is a dialog-based app... The OS is supposed to automatically manage memory.
|
|
|
|
|
i have one dialog(login) and a few CWnd... is their a way to "kill" the application, when i press the close button(X)?
|
|
|
|
|
Mariz wrote:
press the close button(X)
Well, it is NOT a close button. Microsoft calls it a "smart minimize" button. When you press it on the main window, you get a stream of messages, the first of which is WM_IME_NOTIFY with wParam = IMN_CLOSESTATUSWINDOW. The second message is WM_IME_SETCONTEXT with wParam = FALSE and lParam = ISC_SHOWUIALL.
Maybe you can intercept these messages and close your application appropriately, by sending a WM_CLOSE message to your main window.
|
|
|
|
|
I think your solution is good but... visual doesn't recognize WM_IME_NOTIFY(i put it in MainFrame Message_Map).
Any idea...?
|
|
|
|
|
Developing with MFC? Handling "strange" messages is a bitch. Gess what: you have to intercept the window's message loop and do some old-style C-like message handling. Nice huh? Hack the window class WindowProc!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
