You can subscribe to this list here.
1999 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(23) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2000 |
Jan
(15) |
Feb
(11) |
Mar
(6) |
Apr
(47) |
May
(14) |
Jun
(13) |
Jul
(20) |
Aug
(4) |
Sep
(15) |
Oct
(28) |
Nov
(40) |
Dec
(11) |
2001 |
Jan
(28) |
Feb
(9) |
Mar
(17) |
Apr
(10) |
May
(26) |
Jun
(31) |
Jul
(83) |
Aug
(66) |
Sep
(106) |
Oct
(82) |
Nov
(139) |
Dec
(76) |
2002 |
Jan
(138) |
Feb
(140) |
Mar
(118) |
Apr
(179) |
May
(85) |
Jun
(92) |
Jul
(53) |
Aug
(39) |
Sep
(60) |
Oct
(48) |
Nov
(114) |
Dec
(71) |
2003 |
Jan
(76) |
Feb
(58) |
Mar
(83) |
Apr
(70) |
May
(23) |
Jun
(63) |
Jul
(27) |
Aug
(233) |
Sep
(74) |
Oct
(35) |
Nov
(24) |
Dec
(42) |
2004 |
Jan
(85) |
Feb
(99) |
Mar
(33) |
Apr
(43) |
May
(17) |
Jun
(29) |
Jul
(17) |
Aug
(16) |
Sep
(17) |
Oct
(5) |
Nov
(3) |
Dec
(15) |
2005 |
Jan
(38) |
Feb
(24) |
Mar
(11) |
Apr
(14) |
May
(4) |
Jun
(15) |
Jul
(11) |
Aug
(5) |
Sep
(3) |
Oct
(14) |
Nov
(9) |
Dec
(3) |
2006 |
Jan
(9) |
Feb
(4) |
Mar
(4) |
Apr
(2) |
May
(6) |
Jun
(1) |
Jul
(3) |
Aug
(10) |
Sep
|
Oct
(1) |
Nov
|
Dec
(7) |
2007 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(3) |
Oct
|
Nov
(2) |
Dec
|
2008 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
(2) |
May
|
Jun
(3) |
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Larry W. V. <lv...@ca...> - 2001-01-03 15:45:56
|
I wonder if anyone else has seen this. I have installed 11 DB databases via the install software. I have selected 'rescan' from the advanced options. But DB 0.3.0 only shows me 4 of the 11 databases. I would like to be able to see all of the databases. Is there anything I can do to fix this? -- Never apply a Star Trek solution to a Babylon 5 problem. Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/> Even if explicitly stated to the contrary, nothing in this posting should be construed as representing my employer's opinions. -><- |
From: KANE P. (CA) <Pet...@er...> - 2000-12-28 00:05:04
|
It works on my Palm Vx with no worries -----Original Message----- From: Tom Dyas [mailto:td...@us...] Sent: Tuesday, 19 December 2000 15:28 To: Larry W. Virden; pil...@li... Subject: Re: [pilot-db-list] db binary compatibility On Monday 18 December 2000 05:23, Larry W. Virden wrote: > I am possibly going to be able to upgrade to a newer model of palm in the > next few weeks. Has the prc for db being tried on a variety of Palm > devices? I think the new model will be a Vx. DB should work on all devices running PalmOS 2.0 or higher. _______________________________________________ Pilot-db-list mailing list Pil...@li... http://lists.sourceforge.net/mailman/listinfo/pilot-db-list This e-mail (including any attachments) may contain confidential or privileged information and is intended for the sole use of the person(s) to whom it is addressed. If you are not the intended recipient, or the person responsible for delivering this message to the intended recipient, please notify the sender of the message or send an e-mail to mailto:hel...@er... immediately, and delete all copies. Any unauthorised review, use, alteration, disclosure or distribution of this e-mail by an unintended recipient is prohibited. Ergon Energy accepts no responsibility for the content of any e-mail sent by an employee which is of a personal nature. Ergon Energy Corporation Limited ABN 50 087 646 062 Ergon Energy Pty Ltd ABN 66 078 875 902 |
From: Dale P. S. <dp...@en...> - 2000-12-21 14:48:35
|
Greetings List. I'm attempting to build db-0.3.0 on a Debian Potato system with the prc-tools and pilrc packages installed. First, my executables are named like "m68k-palmos-coff-gcc", so I edited the Makefile apropriately. Then I find there is no "Palm.h" file on my system, however I did find a few "Pilot.h" files: dsmith@sammy:~/src/db-0.3.0$ locate Pilot.h /usr/lib/gcc-lib/m68k-palmos-coff/2.7.2.2-kgpd-071097/include/PalmOS1/Pilot.h /usr/lib/gcc-lib/m68k-palmos-coff/2.7.2.2-kgpd-071097/include/PalmOS2/Pilot.h /usr/m68k-palmos-coff/include/PalmOS1/Pilot.h /usr/m68k-palmos-coff/include/PalmOS2/Pilot.h Creating a Palm.h that contains "#include <PalmOS1/Pilot.h> (or PalmOS2) in the current directory and adding "-I." to CFLAGS gives me complaints about UInt16 being undefined (also UInt8 and UInt32). Looks like I'm missing some things. Where do I get Palm.h? What are the definitions for UInt* ? What else am I missing? Thanks for your help. -Dale -- Dale P. Smith Altus Technologies Corporation ds...@al... 440-746-9000 x309 |
From: Tom D. <td...@us...> - 2000-12-19 05:29:43
|
On Monday 18 December 2000 05:23, Larry W. Virden wrote: > I am possibly going to be able to upgrade to a newer model of palm in the > next few weeks. Has the prc for db being tried on a variety of Palm > devices? I think the new model will be a Vx. DB should work on all devices running PalmOS 2.0 or higher. |
From: Larry W. V. <lv...@ca...> - 2000-12-18 11:30:48
|
Sorry, but that doesn't seem to be helping - at least, here's what I get now. CC -DHAVE_CONFIG_H -I. -I/ldatae/PilotBuilding/DB/palm-db-tools-0.3.1/libpalm -I.. -I/ldatae/PilotBuilding/DB/palm-db-tools-0.3.1 -I/ldatae/PilotBuilding/DB/palm-db-tools-0.3.1/libpalm -g -c File.cpp -KPIC -DPIC -o File.o "File.cpp", line 121: Error: Formal argument x of type const std::pair<PalmLib::Block*, std::pair<std::fpos<__mbstate_t>, unsigned>>& in call to std::vector<std::pair<PalmLib::Block*, std::pair<std::fpos<__mbstate_t>, unsigned>>, std::allocator<std::pair<PalmLib::Block*, std::pair<std::fpos<__mbstate_t>, unsigned>>>>::push_back(const std::pair<PalmLib::Block*, std::pair<std::fpos<__mbstate_t>, unsigned>>&) is being passed std::pair<PalmLib::Block*, std::pair<std::fpos<__mbstate_t>, int>>. "File.cpp", line 124: Error: Formal argument x of type const std::pair<PalmLib::Block*, std::pair<std::fpos<__mbstate_t>, unsigned>>& in call to std::vector<std::pair<PalmLib::Block*, std::pair<std::fpos<__mbstate_t>, unsigned>>, std::allocator<std::pair<PalmLib::Block*, std::pair<std::fpos<__mbstate_t>, unsigned>>>>::push_back(const std::pair<PalmLib::Block*, std::pair<std::fpos<__mbstate_t>, unsigned>>&) is being passed std::pair<PalmLib::Block*, std::pair<std::fpos<__mbstate_t>, int>>. 2 Error(s) detected. make[2]: *** [File.lo] Error 1 make[2]: Leaving directory `/ldata2/Pilot/PilotBuilding/DB/palm-db-tools-0.3.1/libpalm' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/ldata2/Pilot/PilotBuilding/DB/palm-db-tools-0.3.1' make: *** [all-recursive-am] Error 2 -- Never apply a Star Trek solution to a Babylon 5 problem. Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/> Even if explicitly stated to the contrary, nothing in this posting should be construed as representing my employer's opinions. -><- |
From: Larry W. V. <lv...@ca...> - 2000-12-18 10:24:08
|
I am possibly going to be able to upgrade to a newer model of palm in the next few weeks. Has the prc for db being tried on a variety of Palm devices? I think the new model will be a Vx. -- Never apply a Star Trek solution to a Babylon 5 problem. Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/> Even if explicitly stated to the contrary, nothing in this posting should be construed as representing my employer's opinions. -><- |
From: Tom D. <td...@va...> - 2000-12-15 07:45:47
|
On Thu, 14 Dec 2000, Larry W. Virden wrote: > When I try to build the latest release of the tools, using Sun's C++ compiler, > I get this error: > > CC -DHAVE_CONFIG_H -I. -I/ldatae/PilotBuilding/DB/palm-db-tools-0.3.1/libpalm -I.. -I/ldatae/PilotBuilding/DB/palm-db-tools-0.3.1 -I/ldatae/PilotBuilding/DB/palm-db-tools-0.3.1/libpalm -g -c File.cpp -KPIC -DPIC -o File.o > lmLib::Block*, std::pair<std::fpos<__mbstate_t>, unsigned>>>>::push_back(const std::pair<PalmLib::Block*, std::pair<std::fpos<__mbstate_t>, unsigned>>&) is being passed std::pair<PalmLib::Block*, std::pair<long, int>>. > lmLib::Block*, std::pair<std::fpos<__mbstate_t>, unsigned>>>>::push_back(const std::pair<PalmLib::Block*, std::pair<std::fpos<__mbstate_t>, unsigned>>&) is being passed std::pair<PalmLib::Block*, std::pair<long, int>>. > 2 Error(s) detected. Try the attached patch (or make the modifications noted in the patch) by moving into the libpalm/ directory and running: patch -p0 < File.cpp.patch |
From: Tom D. <td...@va...> - 2000-12-15 07:36:08
|
palm-db-tools 0.3.1 is now in the normal place and the home page has been updated. The normal place is: http://download.sourceforge.net/palm-db-tools/ Minor note: The contact address is td...@us... and not td...@va... (which will go away soon) so if anyone sends to td...@va... don't be surprised if the mail bounces. |
From: Tom D. <td...@va...> - 2000-12-14 20:26:07
|
On Thu, 14 Dec 2000, Larry W. Virden wrote: > Someone recently said something on news:comp.sys.palmtops.pilot about > a recent (within last 7 days) update to DB. Is this source only, or is a > new prc available? I don't have build capabilities right now and time is > too short to develop such capabilities. I've been checking stuff into CVS that I did on an airplane back from a consulting gig. Still some bugs to work out before it is ready for even a testing release. I still have to integrate the third-party patch. |
From: Larry W. V. <lv...@ca...> - 2000-12-14 19:53:57
|
When I try to build the latest release of the tools, using Sun's C++ compiler, I get this error: CC -DHAVE_CONFIG_H -I. -I/ldatae/PilotBuilding/DB/palm-db-tools-0.3.1/libpalm -I.. -I/ldatae/PilotBuilding/DB/palm-db-tools-0.3.1 -I/ldatae/PilotBuilding/DB/palm-db-tools-0.3.1/libpalm -g -c File.cpp -KPIC -DPIC -o File.o lmLib::Block*, std::pair<std::fpos<__mbstate_t>, unsigned>>>>::push_back(const std::pair<PalmLib::Block*, std::pair<std::fpos<__mbstate_t>, unsigned>>&) is being passed std::pair<PalmLib::Block*, std::pair<long, int>>. lmLib::Block*, std::pair<std::fpos<__mbstate_t>, unsigned>>>>::push_back(const std::pair<PalmLib::Block*, std::pair<std::fpos<__mbstate_t>, unsigned>>&) is being passed std::pair<PalmLib::Block*, std::pair<long, int>>. 2 Error(s) detected. -- Never apply a Star Trek solution to a Babylon 5 problem. Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/> Even if explicitly stated to the contrary, nothing in this posting should be construed as representing my employer's opinions. -><- |
From: Larry W. V. <lv...@ca...> - 2000-12-14 18:58:36
|
Someone recently said something on news:comp.sys.palmtops.pilot about a recent (within last 7 days) update to DB. Is this source only, or is a new prc available? I don't have build capabilities right now and time is too short to develop such capabilities. -- Never apply a Star Trek solution to a Babylon 5 problem. Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/> Even if explicitly stated to the contrary, nothing in this posting should be construed as representing my employer's opinions. -><- |
From: Tom D. <td...@va...> - 2000-12-13 23:51:23
|
ftp://palm-db-tools.sourceforge.net/pub/palm-db-tools/dbtools_0_3_1.zip ftp://palm-db-tools.sourceforge.net/pub/palm-db-tools/palm-db-tools-0.3.1.tar.gz Version 0.3.1 is on the SourceForge ftp site right now since SourceForge is having problems making file releases the normal way. Any ways, it is the same as 0.3.1pre1 except I updated the README and TODO files. |
From: Tom D. <td...@va...> - 2000-11-22 04:44:47
|
For those who reported the bugs in 0.3.0 of the conversion utilities, does the recent 0.3.1pre1 fix the problems? |
From: Tom D. <td...@va...> - 2000-11-17 22:42:00
|
On Mon, 6 Nov 2000, Volker Lapczynski wrote: > Is there anbody out there using "OnBoardC" for database > compiling? Nope. DB supports compilation with prc-tools 2.0 and SDK 3.5update1 currently. > I like to use OnBoardC for DB, but i am not able to convert source- > code to OnBoardC source. DB uses the multisegment capability of prc-tools 2.0 among other features. I'm not familiar with OnBoardC. What is stopping you from converting? |
From: Tom D. <td...@va...> - 2000-11-15 14:21:32
|
A prerelease of the next version of the conversionutils is available. Go to: ftp://palm-db-tools.sourceforge.net/pub/palm-db-tools/dbtools_0_3_1_pre1.zip ftp://palm-db-tools.sourceforge.net/pub/palm-db-tools/palm-db-tools-0.3.1-pre1.tar.gz Basically, this version adds support for JFile v3 databases. Bug fixes to the DB 0.3.x support and DB 0.2.x support. Can convert more field types now including date and time. This only makes sense for JFile3 for now, but when DB gets more field types, the infrastructure is there. |
From: Volker L. <vl...@gm...> - 2000-11-06 13:51:21
|
Hi! Is there anbody out there using "OnBoardC" for database compiling? I like to use OnBoardC for DB, but i am not able to convert source- code to OnBoardC source. Volker from Norway vl...@gm... |
From: KANE P. (CA) <Pet...@er...> - 2000-11-06 01:38:56
|
I have started using a DB database as a journal (none of the existing journal programs I have tried have exactly the features I want, but that is another story! DayNotez comes closest, but not close enough, and why load a new app if DB can do the job) I then started thinking what new features of DB would enhance this use of DB. There are a few changes to fields, views, and some thoughts on categories that I'd like to comment on: FIELDS * a memo field for very long text. Probably most urgent for this app. * a date field with today as default, but editable * a time field with now as default, but editable * probably a date-time field as well, with now as default. Not needed for the journal app, but probably needed for completeness. CATEGORIES Thoughts on categories: Tom's recent e-mail on categories are correct. It is a filtering function, not for views or sorting. As a suggestion, could you assign one field as the category, and filter for all records matching this category (implies getting a sorted list of unique entries in the category field). Possibly there should be the ability to have a single field of type 'category' per database? However, this may be too specific a feature, and cripple a more general-purpose filtering capability. VIEWS * One new thought for views: A new feature worth considering is adding the ability to use one field as a sub-heading in the list view (eg. in the journal application this would be the date). Implies the data in the view is sorted by sub-heading first. The sub-heading would be displayed on it's own line in (say) inverted, bold text, followed by records with a matching sub-heading field. * (already suggested in previous correspondence) a read-only page view of each record similar to the address book. OTHER, BUGS etc. Is it possible to create a 'shortcut' app that starts up DB limited to a single database (eg my Journal)? This could have it's own icon and appear for all intents & purposes to be a separate application? The edit view & other configuration features would have to be disabled. * auto-capitalisation of text fields (like in memo-pad and other apps) * If a headings is too wide for the column width, should it end in '...' like fields in the list view? * ability to set fonts? * LinkMaster title needs to be more explanatory. More than one published link has the same name (I'm using progect, and it supports LinkMaster) * bug In display driver. If last field is string and uses all characters, then the last line is not always displayed if you have to scroll to see it (I could probably send you an example, but should be easy to re-create) Sorry about the lengthy e-mail, but as you can see, I am trying to get the most out of DB, and I guess that it pushes up against the limits. _______________ Peter Kane Ergon Energy Capricornia PO Box 308 (185 Richardson Rd) Rockhampton Q 4700 Phone: (07) 4931-2658; Fax: (07) 4931-2238; Mobile: 0409 495 008 mailto:pet...@er... > http://www.ergon.com.au > > > > > This e-mail (including any attachments) may contain confidential or privileged information and is intended for the sole use of the person(s) to whom it is addressed. If you are not the intended recipient, or the person responsible for delivering this message to the intended recipient, please notify the sender of the message or send an e-mail to mailto:hel...@er... immediately, and delete all copies. Any unauthorised review, use, alteration, disclosure or distribution of this e-mail by an unintended recipient is prohibited. Ergon Energy accepts no responsibility for the content of any e-mail sent by an employee which is of a personal nature. |
From: Tom D. <td...@va...> - 2000-11-04 09:01:26
|
On Sat, 4 Nov 2000, Nathan Kurz wrote: > I'm having problems debugging 'db-en.prc' with Pose and GDB. > Essentially, any code put in the main section works fine, but anything > explicitly put into a different section (eg, EDITSECT) can not be > debugged. I just tried patching and compiling the new version of GDB, > but to no avail. As of June, multiple segments were a problem for GDB. > Are they still a problem or is there some way to make it work? It is still a problem. The bugs fixed in the more recent gdb+patch were in retrieiving the values of variables off the device. Still buggy with regard to multiple sections. |
From: Nathan K. <na...@va...> - 2000-11-04 08:44:40
|
I'm having problems debugging 'db-en.prc' with Pose and GDB. Essentially, any code put in the main section works fine, but anything explicitly put into a different section (eg, EDITSECT) can not be debugged. I just tried patching and compiling the new version of GDB, but to no avail. As of June, multiple segments were a problem for GDB. Are they still a problem or is there some way to make it work? Versions: m68k-palmos-coff-gdb: 5.0 m68k-palmos-gdb: 4.18 pose: emulator 3.0a7 SDK: 3.5 plus update 1 linux: 2.2.16 Thanks! --nate |
From: Tom D. <td...@va...> - 2000-11-03 22:32:53
|
On Fri, 3 Nov 2000, Nathan Kurz wrote: > Here's my first try at navigation between fields in the edit view. It > basically works, although it is not well tested. I'll test tomorrow. > I ended up changing more than I planned to. This is not necessarily a > good thing. I could probably minimize the changes if desired. The > patch is against the test version of 0.3.1. Stylistic corrections > appreciated -- I'm still familiarizing myself with Palm programming. Not to nitpick, but could you resend the patch in "unified diff" format? Pass the -u option to the diff command when making the patch. It is *much* easier to read a unified diff then the old/new context diff that the diff command normally makes. Thanks. |
From: Miguel M. <mi...@yo...> - 2000-11-03 12:33:42
|
Greetings... > Does anybody else have any thoughts on the user interface stuff? . . . > For moving fields, maybe I should implement the drag&drop support that > exists on the database picker screen for changing the order? > Personally I like the drag and drop model. I would like it for other things in DB too. Maybe a row of small icons in the bottom? A delete, a edit and a beam icon. You would drag the rows and drop them there. You could also add some icons to give quick access to Edit List Views and Edit Database Design. Perhaps that could be used for the list views to allow you to drag the different fields around instead of using the menus of all fields for each line which I thought was a bit clunky. The other thing that would be nice, would be if you could tap the titles of each column in a database to sort on that field. (I kept doing that when I read sorting had been implemented) Maybe with small icon which would toggle descending/ascending. Just some ideas which some may dislike, I happen to like the drag and drop style of interface. Miguel C. Miguel Marques, York University, Computing & Network Services e-mail: mi...@yo..., voice: (416)736-2100x22684, fax: (416)736-5830 |
From: Nathan K. <na...@va...> - 2000-11-03 09:09:26
|
Tom Dyas writes: > > On Thu, 2 Nov 2000, Nathan Kurz wrote: > > > I find it reasonable, but a little odd. What was wrong with the > > pulldown menu at the top right that you looked to be starting with? I > > was thinking that along with a similar pulldown at the upper right of > > the list view for selecting the current view would be quite nice. > > I'd rather reserve that for selecting one of two things: > > a) filtering since it is similar in spirit to a category selector > b) some sort of "combo" mode setting list view, sort order, and filter all > at once. The second of those sounds like a fine plan to me. Before I saw that you had come up with a sorting interface, I spent some time thinking about how those three could be combined. I concluded that list views and sort orders should be synonymous and available on the pulldown, but that filters need to be separate but also available directly. I envisioned a second popup at the bottom of the page that could replace the current find and find next buttons, expandable to multiple lines. > > I also found a bit of bugginess with the new view editor, or at least > > something confusing. It seems that if I edit 'All Fields' to be > > something that is not all fields, make and delete another view, that > > 'All Fields' reverts to its default definition, losing my changes. > > When you create a new view, it makes one called "All Fields" with one > column per field. If one of your existing views is being overwritten, then > this would be a bug. However, in this case, is the "All Fields" one the > new one or the modified old one? I'm not exactly sure what happened, and I'm having trouble recreating it. I think what I saw was not bug, but a confusion of naming. I think my old view was entitled 'new view', so that was the one I deleted, thinking that it was the new view and that 'All Fields' was the old. Perhaps the new views could be given some other name? It seems a little awkward that it calls all new views 'All Fields'. --nate |
From: Nathan K. <na...@va...> - 2000-11-03 09:09:03
|
Here's my first try at navigation between fields in the edit view. It basically works, although it is not well tested. I'll test tomorrow. I ended up changing more than I planned to. This is not necessarily a good thing. I could probably minimize the changes if desired. The patch is against the test version of 0.3.1. Stylistic corrections appreciated -- I'm still familiarizing myself with Palm programming. ---------------------------------------------------------------------- *** edit.c Fri Oct 20 01:51:08 2000 --- edit.nate.c Fri Nov 3 02:13:28 2000 *************** *** 26,31 **** --- 26,34 ---- #define GetObjectPtr(f,i) FrmGetObjectPtr((f),FrmGetObjectIndex((f),(i))) #define noFieldIndex 32 + #define labelColumn 0 + #define fieldColumn 1 + typedef struct { MemHandle h; Boolean b; *************** *** 54,69 **** static void EditViewLoadTable(TablePtr table) EDITSECT; static void EditViewInitTable(TablePtr table) EDITSECT; static void EditViewResizeDescription(EventPtr event) EDITSECT; ! #if 0 ! static void EditViewHandleSelectField(UInt16 row, const UInt8 column) EDITSECT ; ! #endif static void EditViewScroll(WinDirectionType direction) EDITSECT; static Boolean ValidateData(void) EDITSECT; static void SaveRecord(void) EDITSECT; static void SetupRecordData(void) EDITSECT; - static Err EditViewLoadRecord(void * table, Int16 row, Int16 column, Boolean editing, MemHandle * textH, Int16 * textOffset, --- 57,70 ---- static void EditViewLoadTable(TablePtr table) EDITSECT; static void EditViewInitTable(TablePtr table) EDITSECT; static void EditViewResizeDescription(EventPtr event) EDITSECT; ! static void EditViewNextField(WinDirectionType direction) EDITSECT; ! static void EditViewSelectField(TablePtr table, UInt16 fieldIndex) EDITSECT; static void EditViewScroll(WinDirectionType direction) EDITSECT; static Boolean ValidateData(void) EDITSECT; static void SaveRecord(void) EDITSECT; static void SetupRecordData(void) EDITSECT; static Err EditViewLoadRecord(void * table, Int16 row, Int16 column, Boolean editing, MemHandle * textH, Int16 * textOffset, *************** *** 389,396 **** } /* Enable the label and data columns. */ ! TblSetColumnUsable(table, 0, true); ! TblSetColumnUsable(table, 1, true); /* Figure out the width of the label column. */ labelWidth = FntCharsWidth(CurrentSource->schema.fields[0].name, --- 390,397 ---- } /* Enable the label and data columns. */ ! TblSetColumnUsable(table, labelColumn, true); ! TblSetColumnUsable(table, fieldColumn, true); /* Figure out the width of the label column. */ labelWidth = FntCharsWidth(CurrentSource->schema.fields[0].name, *************** *** 412,417 **** --- 413,421 ---- TblSetSaveDataProcedure(table, 1, EditViewSaveRecord); EditViewLoadTable(table); + + /* set focus to the first field */ + EditViewSelectField(table, 0); } static void *************** *** 492,529 **** } } - #if 0 static void ! EditViewHandleSelectField(UInt16 row, const UInt8 column) { ! TablePtr table; ! FieldPtr fld; ! UInt16 fieldNum; ! Char buf[16]; ! StrIToA(buf, column); ! FrmCustomAlert(alertID_Debug, "row = ", buf, " "); ! table = GetObjectPtr(FrmGetActiveForm(), ctlID_EditView_Table); ! fieldNum = TblGetRowID(table, row); ! if (fieldNum != CurrentField) { ! if (TblGetCurrentField(table)) { ! TblReleaseFocus(table); ! FrmCustomAlert(alertID_Debug, "focus released", " ", " "); ! } ! TblUnhighlightSelection(table); ! TblGrabFocus(table, row, 1); ! fld = TblGetCurrentField(table); ! if (fld) { ! FldGrabFocus(fld); ! FldMakeFullyVisible(fld); ! } ! FrmCustomAlert(alertID_Debug, "focus grabbed", " ", " "); ! CurrentField = fieldNum; } } - #endif static void EditViewScroll(WinDirectionType direction) --- 496,600 ---- } } static void ! EditViewSelectField(TablePtr table, UInt16 fieldIndex) { ! UInt16 fieldRow; ! FieldPtr fld; ! UInt16 tableIndex; ! FormPtr form; ! ! /* NOTE: must unhighlite selection first */ ! TblUnhighlightSelection(table); ! ! /* remove the old focus before setting the new */ ! /* FUTURE: is there a more efficient yet safe way of doing this? */ ! form = FrmGetActiveForm(); ! FrmSetFocus(form, noFocus); ! tableIndex = FrmGetObjectIndex(form, ctlID_EditView_Table); ! FrmSetFocus(form, tableIndex); ! ! /* scroll in case nextRow is not already visible on the screen */ ! if (! TblFindRowID(table, fieldIndex, &fieldRow)) { ! /* NOTE: only the rows shown on the screen are present in the table */ ! CurrentField = fieldIndex; ! EditViewLoadTable(table); ! TblRedrawTable(table); ! /* find the next row within the scrolled version of the table */ ! ErrFatalDisplayIf(! TblFindRowID(table, fieldIndex, &fieldRow), ! "could not find specified row"); ! } ! ! /* set the focus according to the field type */ ! switch (CurrentSource->schema.fields[fieldIndex].type) ! { ! case FIELD_TYPE_STRING: ! case FIELD_TYPE_INTEGER: ! TblSelectItem(table, fieldRow, fieldColumn); ! TblGrabFocus(table, fieldRow, fieldColumn); ! fld = TblGetCurrentField(table); ! FldGrabFocus(fld); ! FldMakeFullyVisible(fld); ! break; ! case FIELD_TYPE_BOOLEAN: ! /* no focus allowed for boolean so select the label instead */ ! TblSelectItem(table, fieldRow, labelColumn); ! break; ! default: ! ErrDisplay("field type not supported"); ! break; ! } ! return; ! } ! ! ! static void ! EditViewNextField(WinDirectionType direction) ! { ! FormPtr form; ! TablePtr table; ! Int16 currentRow; ! Int16 currentColumn; ! UInt16 currentFieldIndex; ! UInt16 lastFieldIndex; ! UInt16 nextFieldIndex; ! ! form = FrmGetActiveForm(); ! table = GetObjectPtr(form, ctlID_EditView_Table); ! if (! table) return; ! /* NOTE: TblEditing() would return false if a label was selected */ ! ! /* FUTURE: check that something indeed is selected */ ! /* NOTE: TblGetSelection() is false after initial automatic selection? */ ! TblGetSelection(table, ¤tRow, ¤tColumn); ! ! currentFieldIndex = TblGetRowID(table, currentRow); ! lastFieldIndex = CurrentSource->schema.numFields - 1; ! ! if (direction == winDown) ! { ! if (currentFieldIndex < lastFieldIndex) ! nextFieldIndex = currentFieldIndex + 1; ! else ! /* last field cycles forward to first field */ ! nextFieldIndex = 0; ! } ! else /* winUp */ ! { ! if (currentFieldIndex > 0) ! nextFieldIndex = currentFieldIndex - 1; ! else ! /* first field cycles back to last field */ ! nextFieldIndex = lastFieldIndex; } + + EditViewSelectField(table, nextFieldIndex); + + return; } static void EditViewScroll(WinDirectionType direction) *************** *** 819,825 **** FormPtr form; TablePtr table; UInt16 fieldNum; - FieldPtr fld; switch (event->eType) { case frmOpenEvent: --- 890,895 ---- *************** *** 873,915 **** case tblSelectEvent: table = event->data.tblSelect.pTable; fieldNum = TblGetRowID(table, event->data.tblSelect.row); ! if (event->data.tblSelect.column == 0) { ! switch (CurrentSource->schema.fields[fieldNum].type) { ! case FIELD_TYPE_STRING: ! case FIELD_TYPE_INTEGER: ! /* A tap on the label edits the field. */ ! if (TblGetCurrentField(event->data.tblSelect.pTable)) { ! TblReleaseFocus(event->data.tblSelect.pTable); ! } ! TblUnhighlightSelection(event->data.tblSelect.pTable); ! TblGrabFocus(event->data.tblSelect.pTable, ! event->data.tblSelect.row, 1); ! fld = TblGetCurrentField(event->data.tblSelect.pTable); ! if (fld) { ! FldGrabFocus(fld); ! FldMakeFullyVisible(fld); ! } ! return true; ! default: ! break; ! } ! } else if (event->data.tblSelect.column == 1) { ! switch (CurrentSource->schema.fields[fieldNum].type) { case FIELD_TYPE_BOOLEAN: ! if (TblGetItemInt(table, ! event->data.tblSelect.row, ! event->data.tblSelect.column)) ! fields[fieldNum].b = true; ! else ! fields[fieldNum].b = false; ! IsDirty = true; ! break; - default: - break; - } - } return false; case ctlSelectEvent: --- 943,966 ---- case tblSelectEvent: table = event->data.tblSelect.pTable; fieldNum = TblGetRowID(table, event->data.tblSelect.row); ! EditViewSelectField(table, fieldNum); ! if (event->data.tblSelect.column == 1) { ! switch (CurrentSource->schema.fields[fieldNum].type) { case FIELD_TYPE_BOOLEAN: ! if (TblGetItemInt(table, event->data.tblSelect.row, ! event->data.tblSelect.column)) ! fields[fieldNum].b = true; ! else ! fields[fieldNum].b = false; ! IsDirty = true; ! break; ! ! default: ! break; ! } ! } return false; case ctlSelectEvent: *************** *** 977,992 **** } } break; ! default: return HandleCommonMenuEvent(event->data.menu.itemID); } break; - default: - break; ! } return false; } --- 1028,1071 ---- } } break; ! default: return HandleCommonMenuEvent(event->data.menu.itemID); } break; ! case keyDownEvent: ! if (EvtKeydownIsVirtual(event)) ! { ! switch (event->data.keyDown.chr) ! { ! case vchrPageUp: ! EditViewScroll (winUp); ! return true; ! ! case vchrPageDown: ! EditViewScroll (winDown); ! return true; ! ! case vchrNextField: ! EditViewNextField (winDown); ! return true;; ! ! case vchrPrevField: ! EditViewNextField (winUp); ! break; ! } ! } ! else /* key is not virtual */ ! { ! /* FUTURE: allow checkboxes to be toggled using keyboard */ ! } + default: + break; + + } + return false; } ---------------------------------------------------------------------------- Goodnight! --nate |
From: Nathan K. <na...@va...> - 2000-11-03 08:56:47
|
Tho...@rw... writes: > > If you use the sdk 3.5 update 1 the new version compiles without the > linker errors. You can find the file attached. > > Regards > Thorsten Tietz Danke Schoen! You are correct. Once I installed the new libPalmOSGlue.a the segments all fit and things starting working like they should. I think this is because the replacement library is 4K smaller, and we are pushing the edge of how big the UI section can be. -rw-r--r-- 1 root root 22618 (old version) libPalmOSGlue.a -rw-r--r-- 1 root root 16038 (new version) libPalmOSGlue.a --nate |
From: Nathan K. <na...@va...> - 2000-11-03 08:56:42
|
Tom Dyas writes: > The m68k-palmos-gdb provided by prc-tools is buggy. If you extract > the gdb patch from prc-tools CVS on SourceForge and rebuild gdb > manually, then you'll get better results. Will this take care of the way that gdb handles the multiple sections? Currently, they seem to be all jumbled up, so that the only way I can debug functions is to put them in the main section. There is a 'section' command within gdb, but I haven't had any luck using it. --nate |