Advise

[Colin Haig]

To All

I have just begun using FWPPC and would like to know -

Is it better to use resource workshop or manually build dialogs and controls - I have created a dialog with BRW and have a static say 'Client ID' but when testing it only displays 'Client' - which leads to my second question - is it better to have the PDA to test on or is the emulator just as good.

What font and font size is recommended.

I also created a edit field and set for right justification for a numeric input but the cursor stays on the left side.

Cheers

Colin

[pawelu]

Colin,

You may use free Pelles C IDE to create dialog for Pocket PC. When you run your applications real device is good choice to test them.

In my projects default font is System 10. This is larger font than default (8) but it's more readable for users.

Sample dialog:

Code: Select all  Expand view

#include "c:\vce\include\arm\windows.h"
#include "c:\vce\include\arm\commctrl.h"

DOKHEAD DIALOG DISCARDABLE 0, 0, 136, 154
STYLE WS_POPUP|DS_MODALFRAME|WS_CAPTION|WS_VISIBLE
CAPTION "Nagł.dokumentu"
FONT 10, "System"
BEGIN
  CONTROL "Klient:", 1001, "Static", SS_RIGHT|WS_GROUP, 0, 2, 22, 11
  CONTROL "Data wyst:", 1002, "Static", SS_RIGHT|WS_GROUP, 0, 24, 36, 11
  CONTROL "Sp. zapł:", 1003, "Static", SS_RIGHT|WS_GROUP, 0, 36, 36, 11
  CONTROL "Termin:", 1004, "Static", SS_RIGHT|WS_GROUP, 0, 49, 36, 11
  CONTROL "Realiz:", 1005, "Static", SS_RIGHT|WS_GROUP, 0, 61, 36, 11
  CONTROL "Upust:", 1006, "Static", SS_RIGHT|WS_GROUP, 0, 73, 36, 11
  CONTROL "W.netto:", 1007, "Static", SS_RIGHT|WS_GROUP, 0, 85, 36, 11
  CONTROL "Ulica:", 1008, "Static", SS_RIGHT|WS_GROUP, 0, 109, 24, 11
  CONTROL "Pna/M:", 1009, "Static", SS_RIGHT|WS_GROUP, 0, 121, 24, 11
  CONTROL "", 1010, "Edit", ES_MULTILINE|ES_AUTOVSCROLL|ES_UPPERCASE|ES_READONLY|WS_VSCROLL|WS_BORDER, 22, 2, 112, 21
  CONTROL "", 1011, "Edit", ES_AUTOHSCROLL|ES_READONLY|WS_BORDER, 36, 24, 50, 11
  CONTROL "", 1012, "Edit", ES_AUTOHSCROLL|ES_READONLY|WS_BORDER, 88, 24, 40, 11
  CONTROL "", 1013, "ComboBox", WS_BORDER|CBS_DROPDOWNLIST|WS_VSCROLL|WS_TABSTOP, 36, 36, 50, 40
  CONTROL "", 1014, "Edit", ES_RIGHT|ES_NUMBER|ES_AUTOHSCROLL|ES_READONLY|WS_BORDER, 102, 36, 26, 11
  CONTROL "", 1015, "SysDateTimePick32", WS_TABSTOP|0x00800000, 36, 49, 50, 11
  CONTROL "+", 1016, "Button", WS_TABSTOP, 88, 49, 12, 11
  CONTROL "-", 1017, "Button", WS_TABSTOP, 102, 49, 12, 11
  CONTROL "0", 1018, "Button", WS_TABSTOP, 116, 49, 12, 11
  CONTROL "", 1019, "SysDateTimePick32", WS_TABSTOP|0x00800000, 36, 61, 50, 11
  CONTROL "+", 1020, "Button", WS_TABSTOP, 88, 61, 12, 11
  CONTROL "-", 1021, "Button", WS_TABSTOP, 102, 61, 12, 11
  CONTROL "K", 1022, "Button", WS_TABSTOP, 116, 61, 12, 11
  CONTROL "", 1023, "Edit", ES_RIGHT|ES_NUMBER|ES_AUTOHSCROLL|WS_BORDER|WS_TABSTOP, 36, 73, 32, 11
  CONTROL "+", 1024, "Button", WS_TABSTOP, 88, 73, 12, 11
  CONTROL "-", 1025, "Button", WS_TABSTOP, 102, 73, 12, 11
  CONTROL "", 1026, "Edit", ES_RIGHT|ES_NUMBER|ES_AUTOHSCROLL|ES_READONLY|WS_BORDER, 36, 85, 48, 11
  CONTROL "", 1027, "Edit", ES_RIGHT|ES_NUMBER|ES_AUTOHSCROLL|ES_READONLY|WS_BORDER, 86, 85, 48, 11
  CONTROL "Obliczenia od cen brutto", 1028, "Button", BS_AUTOCHECKBOX|WS_TABSTOP, 36, 97, 98, 11
  CONTROL "", 1029, "Edit", ES_AUTOHSCROLL|ES_UPPERCASE|ES_READONLY|WS_BORDER, 24, 109, 110, 11
  CONTROL "", 1030, "Edit", ES_AUTOHSCROLL|ES_UPPERCASE|ES_READONLY|WS_BORDER, 24, 121, 32, 11
  CONTROL "", 1031, "Edit", ES_AUTOHSCROLL|ES_UPPERCASE|ES_READONLY|WS_BORDER, 58, 121, 76, 11
  CONTROL "Uwagi", 1032, "Button", WS_TABSTOP, 28, 138, 34, 12
  CONTROL "<<", 1033, "Button", WS_TABSTOP, 64, 138, 34, 12
  CONTROL "Zapisz", 1034, "Button", WS_TABSTOP, 100, 138, 34, 12
END


Regards
Pawel

[Enrico Maria Giordano]

Is it better to use resource workshop or manually build dialogs and controls

Resource editor is better, as usual. But I'm not using it at the moment because I found strange differences in the results on the emulator and on the real device. At least using BRW.

- I have created a dialog with BRW and have a static say 'Client ID' but when testing it only displays 'Client'

We might need of a working RESIZE16 clause as in FWH. Antonio?

- which leads to my second question - is it better to have the PDA to test on or is the emulator just as good.

I haven't a PDA. The emulator seems to work fine and the development is faster as you don't have to upload the EXE in the device after each compilation. But yes, you should make at least a final test on the real PDA.

What font and font size is recommended.

I usually don't use a specific font (ie. the default system font is used).

I also created a edit field and set for right justification for a numeric input but the cursor stays on the left side.

Yes, this is a bug of FWPPC, still unresolved. Antonio?

EMG

[Colin Haig]

Is it better to use resource workshop or manually build dialogs and controls

Resource editor is better, as usual. But I'm not using it at the moment because I found strange differences in the results on the emulator and on the real device. At least using BRW.

- I have created a dialog with BRW and have a static say 'Client ID' but when testing it only displays 'Client'

We might need of a working RESIZE16 clause as in FWH. Antonio?

- which leads to my second question - is it better to have the PDA to test on or is the emulator just as good.

I haven't a PDA. The emulator seems to work fine and the development is faster as you don't have to upload the EXE in the device after each compilation. But yes, you should make at least a final test on the real PDA.

What font and font size is recommended.

I usually don't use a specific font (ie. the default system font is used).

I also created a edit field and set for right justification for a numeric input but the cursor stays on the left side.

Yes, this is a bug of FWPPC, still unresolved. Antonio?

EMG

Thanks Enrico for your reply - as I am just starting I might try Pelles RE as suggested by Palewu - I also dont have a PDA but if there was going to be a great variation between the PDA and emulator I would get a PDA.

Regards

Colin

[Antonio Linares]

Enrico,

> We might need of a working RESIZE16 clause as in FWH. Antonio?

If it is needed then we will implement it

> Yes, this is a bug of FWPPC, still unresolved. Antonio?

We found it as a side effect when using a PICTURE. Afaik if you remember the picture, then the right side style was working fine. We didn't find yet whats the relation between them

[Antonio Linares]

Colin,

> to be a great variation between the PDA and emulator

It may depend on what PDA you may use. We use a HP IPAQ and the emulator and the PDA look exactly the same