Mobile

Re: SIP on PropertyPage disapear!

8-Jan-04 5:07

I use the following method to show/hide the SIP. When the app starts, the sip is hidden. When I display a dialog, I do this:

CMyDialog dlg;
ShowSipButton();
dlg.DoModal();
HideSipButton();

Here's the code for showing and hiding the sip:

// in the header file
class CMainFrame
{
protected:
	HWND  m_hwndSIP;
	CRect m_SIPRect;
	BOOL  m_bSIPHidden;
public:
	void HideSipButton();
	void ShowSipButton();
};

int CMainFrame::OnCreate(LPCREATESTRUCT lpCreateStruct)
{
	if (CFrameWnd::OnCreate(lpCreateStruct) == -1)
	{
		return -1;
	}

	m_hwndSIP = ::FindWindow(_T("MS_SIPBUTTON"), NULL);
	ASSERT(NULL != m_hwndSIP);
	::GetWindowRect(m_hwndSIP, &m_SIPRect);
	m_bSIPHidden = FALSE;
	HideSipButton();

	return 0;
}

//------------------------------------------------------------------------------
// Hides the SIP button by moving it OFF the visible screen.
//------------------------------------------------------------------------------
void CMainFrame::HideSipButton()
{
   if (!m_bSIPHidden)
   {
	   ASSERT(NULL != m_hwndSIP);
	   ::MoveWindow(m_hwndSIP, 0, 0, 0, 0, TRUE);
	   m_bSIPHidden = TRUE;
   }
}


//------------------------------------------------------------------------------
// Displays the SIP button by moving it back onto the visible screen.
//------------------------------------------------------------------------------
void CMainFrame::ShowSipButton() 
{
   if (m_bSIPHidden)
   {
	   ASSERT(NULL != m_hwndSIP);
	   ::MoveWindow(m_hwndSIP,
	                m_SIPRect.left,
	                m_SIPRect.top,
	                m_SIPRect.right - m_SIPRect.left + 1,
	                m_SIPRect.bottom - m_SIPRect.top + 1,
	                TRUE);
	   m_bSIPHidden = 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

"You won't like me when I'm angry..." - Dr. Bruce Banner

Please review the Legal Disclaimer in my bio.

------- signature ends

VOlivier8-Jan-04 5:53

VOlivier

8-Jan-04 5:53

Thanks a lot John.
Finally I found another method:

- In each CPropertyPage::InitDialog, I force the SIP status with :

SHSipPreference(AfxGetMainWnd()->GetSafeHwnd() ,SIP_UP);

Thanks again.

Re: SIP on PropertyPage disapear!

cmk9-Jan-04 21:09

cmk

9-Jan-04 21:09

Instead of moving the SIP window I think the suggested method is to use SipShowIM or SipSetInfo.

#include "sipapi.h"

bool  FkGetSipVisible( void )
{
	SIPINFO  si;
	memset(&si, 0, sizeof(si));
	si.cbSize = sizeof(si);

	if( !::SipGetInfo(&si) )  return(false);

	return( si.fdwFlags & SIPF_ON );
}

bool  FkSetSipVisible( bool V )
{
	DWORD  v = V ? SIPF_ON : SIPF_OFF;
	return( ::SipShowIM(v) == TRUE );
	// You could also use SipSetInfo()
}

I then call these in OnSetfocus*() and OnKillfocus*() methods for any edit control.
(The OnLButtonDown() allows me to dismiss the SIP by tapping anywhere on the disalog/page outside an edit cotrol.)
e.g.

void CkPgEditInfo::OnLButtonDown(UINT nFlags, CPoint point) 
{
	CPropertyPage::OnLButtonDown(nFlags, point);
	FkSetSipVisible(false);
	SetFocus();
}

void CkPgEditInfo::OnSetfocusEdit  ()  { FkSetSipVisible(true);  }
void CkPgEditInfo::OnKillfocusEdit ()  { FkSetSipVisible(false); }

...cmk

Rosencrantz: I don't believe in it anyway.
Guildenstern: What
Rosencrantz: England
Guildenstern: Just a conspiracy of cartographers then.

Save the whales - collect the whole set

It is possible to save a drawing? (.Net)

Nick Seng8-Jan-04 0:05

This is not a programming question

8-Jan-04 0:05

What I mean is, in my application, through GDI+, I've enabled to user to draw/scribble/write on a certain area on the screen. The problem is, the Image.Save function is not enabled in mobile apps, so is there another way to save that image?

"if you vote me down, I shall become more powerful than you can possibly imagine" - Michael P. Butler.

Support Bone

It's a weird Life

Nick Seng7-Jan-04 21:49

7-Jan-04 21:49

I've just got a pocket pc to develop apps on, and I've been playing around to get a feel on it. The thing that's got me stumped is, how do you close an application? I've tried "clicking" on the "x" button on the upper right side of the screen, but all that does is minimizes it somewhere (and I can't find it again, but that's another issue).

Anyway, how do you close any applications in pocket pc?

"if you vote me down, I shall become more powerful than you can possibly imagine" - Michael P. Butler.

Support Bone

It's a weird Life

João Paulo Figueira7-Jan-04 22:20

7-Jan-04 22:20

Believe it or not, that is the standard way of "closing" a Pocket PC application. Anyway, that is what Microsoft wants you to do should you want to make your application logo compatible. You can read all about it here:

Designed for Windows for Pocket PC Handbook for Software Application (PDF)[^]

This is a standard behaviour that is enforced by the system, unless you create an "Exit" menu item. When your application receives this command, you just need to send a WM_CLOSE message to the main window. But this is basic stuff...

If you are working with MFC, there is also a neat trick (in fact this is also a Pocket PC standard, although a de facto one - so I believe) that allows you to close an application when the Ctrl+q key message is sent to the appication's main window.

Finally, there is an undocumented way of making the Smart Minimize Button (that is how (X) is called) close your application. You can find the article here:

QA: How can I close my application by clicking the smart minimize (X) button?[^]

Please read the article discussion as well.

Regards,
João Paulo

Nick Seng7-Jan-04 22:34

7-Jan-04 22:34

But why would there be a "Smart Minimize Button" and not a Exit button? Sometimes, I wonder about MS. Roll eyes | :rolleyes:

Anyway, thanks a bunch for the info

"if you vote me down, I shall become more powerful than you can possibly imagine" - Michael P. Butler.

Support Bone

It's a weird Life

João Paulo Figueira7-Jan-04 22:54

7-Jan-04 22:54

Nick Seng wrote:
But why would there be a "Smart Minimize Button" and not a Exit button?

Here is my personal opinion: I believe that Microsoft designed the Pocket PC environment targetting Palm users. If you look at the Palm OS (I once was a happy Palm user) you will see a lot of features that seem to have been "forced" into the Pocket PC. One of these is the inability to close an application. Another one is the artificial restriction on document locations (File Open dialog) and the way document-based applications manage their documents (Pocket Word and Excel, for instance).

Regards,
João Paulo

Nick Seng8-Jan-04 0:03

create login page in WinCE

8-Jan-04 0:03

I never thought of that. D'Oh! | :doh:

"if you vote me down, I shall become more powerful than you can possibly imagine" - Michael P. Butler.

Support Bone

It's a weird Life

Detect Bluetooth device

Cedric Moonen7-Jan-04 4:41

Cedric Moonen

7-Jan-04 4:41

Hello

I have a bluetooth device that establish a connection with my Pocket PC (Serial port connection type). In my program, I analyse the data sent by this device. But I want first to check if the connection is well established.

The function CreateFile returns a valid handle even if no bluetooth conncetion was established. So, when I try to write on this port, the program hangs...

Any solution ?
Thanks

psyclope6-Jan-04 22:35

psyclope

6-Jan-04 22:35

How to create login page in WinCE? Please provide me with sample application.

Truly Weird

#realJSOP6-Jan-04 5:59

6-Jan-04 5:59

Okay, more on my exception problems...

The problem is this:

Our app starts up fine, and I can go into a property sheet. If I click OK in the property sheet, the app goes into it's infernal standby mode (as if I had hit the "OK" thing in the titlebar).

At first, I thought it was an exception firing, but that's not the case. When I'm in the debugger, I can step cleanly through the OnOK function, and when the program returns conrtol to CMainFrame, the app is in standby mode.

If anyone has an idea of what to look for, I'd be interested in hearing about 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

"You won't like me when I'm angry..." - Dr. Bruce Banner

Please review the Legal Disclaimer in my bio.

------- signature ends

João Paulo Figueira6-Jan-04 6:36

6-Jan-04 6:36

When do you show the property sheet? Before or after creating the main frame?

Regards,
João Paulo

#realJSOP6-Jan-04 6:39

6-Jan-04 6:39

After, as a result of a menu item selection from the commandbar.

------- 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

"You won't like me when I'm angry..." - Dr. Bruce Banner

Please review the Legal Disclaimer in my bio.

------- signature ends

João Paulo Figueira6-Jan-04 6:48

6-Jan-04 6:48

Now, that is truly weird... Can you show the code you use to dismiss the property sheet?

Regards,
João Paulo

#realJSOP7-Jan-04 4:27

7-Jan-04 4:27

Well, not really, but here's a description of the situation:

0) Here's the code in CMainFrame that starts the prop sheet:

HideSipButton();
CMypropSheet dlg(_T("Title"));
dlg.DoModal();
ShowSipButton();

1) I have a base class derived from CPropertySheet. This base class implements a toolbar that contains the only button (Okay), as well as a header. There is no "OnOkay" handler in this class.

2) The derived class handles the button presses in the toolbar (and the button ID is IDC_PROPSHEETOK).

2) There are two property pages on the sheet, created dynamically 9and are deleted when the property sheet is dismissed.

3) When the user presses the okay button, the propertysheet calls a public "okay()" method within each page object. These okay() methods simply tell a globally declared object to save the appropriate data to a disk file. Afterwards, the propertysheet calls "EndDialog(IDOK)".

4) In CMainFrame (where I instantiated the propertysheet), there is no additional programming other than re-showing the SIP button. I tried removing the showing/hiding of the SIP button ut that had no effect on the problem.

-----------------------

I initially thought that an exception might have been thrown as a result of trying to write the data files in step 3, but the property sheet is terminating normally with no excpetions, and no memory leaks.

The program itself is still running, but it's almost like the program received the hibernate command from the OS...

------- 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

"You won't like me when I'm angry..." - Dr. Bruce Banner

Please review the Legal Disclaimer in my bio.

------- signature ends

Voice call using phone

misha_grewal6-Jan-04 1:21

misha_grewal

6-Jan-04 1:21

I want to be able to manage a cellular phone book (CDMA phones ) via PDA (pocket PC). Is it possible to dial a number from PDA which will tell the phone connected to make a voice call. Basically can i use some API (TAPI) on PDA to make a voice call using Cellular phone. When the line gets connected I'll start talking on the cellular phone.. but the PDA will dial the number for me from the phone book which is there on the PDA?

Any ideas appreciated..

João Paulo Figueira6-Jan-04 2:57

6-Jan-04 2:57

Check the AT commands from the Nokia documentation. There is a command that does exactly what you want (I've already done that).

Regards,
João Paulo

João Paulo Figueira6-Jan-04 3:01

6-Jan-04 3:01

Check these AT codes:

Start a voice call: ATDT nnnnnnnnn; (semicolon needed).

Hang up the call: ATH

Answer incoming call: ATA

Regards,
João Paulo

misha_grewal7-Jan-04 20:27

misha_grewal

7-Jan-04 20:27

Thanks, I am now aware of how to use AT commands as such. I was looking for some TAPI API for this. I want to have this coded in one program.Can I use these AT commands prgrammatically?

Thanks in advance..

João Paulo Figueira7-Jan-04 22:10