From: =?iso-8859-1?Q?<mar...@la...> - 2002-12-16 18:27:40
|
> =0D=0A> =0D=0A> mar...@la... schrieb:=0D=0A> =0D=0A> >>=0D= =0A> >>By the way, I=B4d rather use a field with a drop down list but=0D= =0A> >=0D=0A> > pilot db=0D=0A> >=0D=0A> >>doesn=B4t allow adding new= entries to the list without=0D=0A> >=0D=0A> > rewriting the list=0D=0A= > >=0D=0A> >>and then re-editing all records. Is there hope that this=0D= =0A> >=0D=0A> > will be changed=0D=0A> >=0D=0A> >>sometime?=0D=0A> >= =0D=0A> >=0D=0A> > like a lot of body you didn't read the documentation= . The=0D=0Alist=0D=0A> > are inside the field properties.=0D=0A> =0D=0A>= I >did< read the documentation, and, from my question about=0D=0Aadding = >new< =0D=0A> entries to an existing drop down list, I think it follows=0D= =0Athat I know =0D=0A> about creating a drop down list first hand. What I= didn=B4t=0D=0Aknow, and what =0D=0A> I couldn=B4t find in the documentat= ion is, that editing an=0D=0Aexisting drop =0D=0A> down list means to com= pletely redefine the field. Maybe=0D=0Athat=B4s an =0D=0A> intenional par= t of pilot db or maybe that=B4s a bug or maybe ...=0D=0A> =0D=0A> Thanks = for your help!=0D=0A> =0D=0A> Guido=0D=0A> =0D=0A=0D=0AThere is not bug o= n this part. front of your list field (in=0D=0Athe database designer) you= have an arrow which drop down a=0D=0Alist with "properties" entry. tape = on it and you will see the=0D=0Abox with your full list of entries.=0D=0A= =0A=0AAcc=E9dez au courrier =E9lectronique de La Poste : www.laposte.net = ; =0A3615 LAPOSTENET (0,13 =80/mn) ; t=E9l : 08 92 68 13 50 (0,34=80/mn)"= =0A=0A |
From: =?iso-8859-1?Q?<mar...@la...> - 2002-12-16 18:52:58
|
read the ch07s02.html file in the documentation or=0D=0A=0D=0Ahttp://pilo= t-db.sourceforge.net/doc/en/ch07s02.html=0A=0AAcc=E9dez au courrier =E9le= ctronique de La Poste : www.laposte.net ; =0A3615 LAPOSTENET (0,13 =80/mn= ) ; t=E9l : 08 92 68 13 50 (0,34=80/mn)"=0A=0A |
From: Guido P. <gui...@gm...> - 2002-12-16 18:47:15
|
mar...@la... schrieb: >> >>mar...@la... schrieb: >> >> >>I >did< read the documentation, and, from my question about > > adding >new< > >>entries to an existing drop down list, I think it follows > > that I know > >>about creating a drop down list first hand. What I didn´t > > know, and what > >>I couldn´t find in the documentation is, that editing an > > existing drop > >>down list means to completely redefine the field. Maybe > > that´s an > >>intenional part of pilot db or maybe that´s a bug or maybe ... >> >>Thanks for your help! >> >>Guido >> > > > There is not bug on this part. front of your list field (in > the database designer) you have an arrow which drop down a > list with "properties" entry. tape on it and you will see the > box with your full list of entries. This exactly is not the case. I tip on the arrow and the list, full before, is now empty. The same with a default value of a text field. Scott says to wait for version 1.1beta. I´ll do that and check whether both problems disappear. In the mailinglists archive there´s an entry (oct.2002) which reports the same default value problem. Thanks! Guido |
From: Guido P. <gui...@gm...> - 2002-12-16 20:15:56
|
The following was sent to me via private mail as a reply to my various postings. My reply to this, I think, clears up the confusion I had about editing existing drop down lists. It might be of some interest for you, which is why I send it to the mailinglist. If it´s not, please ignore. > Guido Pinkernell wrote: > >> mar...@la... schrieb: >> >>>> There is not bug on this part. front of your list field (in >>>> the database designer) you have an arrow which drop down a >>>> list with "properties" entry. tape on it and you will see the >>>> box with your full list of entries. >>> >>> >> >> This exactly is not the case. I tip on the arrow and the list, full >> before, is now empty. > > > You didn't! > At least you didn't tap the *correct* arrow. > There are two of them. > > One completely on the left (left to the field *name*) and one in the middle > (left to the field *type*). > > You most likely tapped the one left to the field *type*. > Marc talks about the one left to the field *name*. Ahhh. I know now what I did. I did tap the correct arrow, but not exactly like you described it: First I tapped on the "type" arrow on the right and selected "list" to check whether the field really was type "list". Drop down list is empty, yes. But I aborted and then selected the property arrow on the left side and, here the drop down list is empty too although I aborted type selection before. Somehow I must have done this two or three times, every time checking whether the field "really" is a list and then finding my dropdown list in "properties" gone and empty. Maybe that´s some bug? Doesn´t matter anymore to me, but maybe there are some other people out there who behave like me and start asking. So you might want to know about this little story. Again, thanks for all your help and patience. Guido |
From: Scott W. <swa...@my...> - 2002-12-17 19:19:57
|
Thanks for going the extra mile with this and figuring out /exactly/ what made your results different than marc's. I've corrected this, but it didn't make it into the 1.1 Beta 1. It will be in the 1.1 Beta 2 as soon as I get some feed back on the Beta 1. -Scott > > Ahhh. I know now what I did. I did tap the correct arrow, but not > exactly like you described it: > > First I tapped on the "type" arrow on the right and selected "list" to > check whether the field really was type "list". Drop down list is empty, > yes. But I aborted and then selected the property arrow on the left side > and, here the drop down list is empty too although I aborted type > selection before. |
From: Scott W. <swa...@my...> - 2002-12-17 19:27:43
|
I have just released the official beta 1 version of pilot-db 1.1. Please test it out and let me know of any problems. As always, make sure you backup your device completely, and use the uninstall.prc program to remove your original version of db (this will not delete db databases). If you are interested in playing a bigger role in making db a better product, I would ask you to send the form that follows back to me, so I can ask for some help from time to time to track down bugs. I know a lot of you have already offered service, but for those who haven't here's your time to help out the community! Basically, all that would be involved is trying to reproduce bugs so I can find and fix them faster. A lot of my time goes to trying to figure out the exact button presses just to duplicate an error, before I can look at the code and fix it. Anyway, if you're interested here's the info I'd like (this will /not/ be distributed to anyone other than a pilot-db developer.) Thanks, Scott -------------------------------------------------------------------------- Name: Email: Your Palm Device: Palm OS Version: What year did you start using db?: Have you used the emulator before?: Have you compiled db from source?: -------------------------------------------------------------------------- |
From: <aji...@t-...> - 2002-12-17 21:23:03
|
Hi Scott, I still have a problem with the Sony HiRes. I have a Sony T625-C and have installed the standrard-version (after de-installing with the deinstall program) First Problem: The high-res check-box has no effect, even if I exit the program and re-start. Irrespective of the status of the high-res check-box I see the following: The view that is opened when a database is clicked on (What is that view - ie. the list of records - called officially, by the way? - Is this called the list view, or is the list of databases called the list-view and if not, what is the list of databases called?) is still 'pixeled', and does not (like in all other views) use the elegant high-res Clie-fonts. The view with the list of Databases e.g. uses the Clie-Font. Furthermore if the Largest Font is selected, then the spacing between the databases is doubled. I had mentioned thesehi-res bugs in the past as well. The only 'new' bug is that the hi-res check box has no effect! This can be duplicated using the Clie-POSE and the corresponding ROM-File. Furthermore after installing DB for the first time and after the Clie turned off automatically, the screen remained black - I had to reset the Clie. This cannot be reproduced, so I presume it only happens the very first time. This happened with the 1.0.1 as well, but I thought it was a coincidence, since I could not reproduce it then either. No other bugs found (yet). Thanks, Hans -----Ursprüngliche Nachricht----- Von: pil...@li... [mailto:pil...@li...]Im Auftrag von Scott Wallace Gesendet: Dienstag, 17. Dezember 2002 20:27 An: pil...@li... Betreff: [pilot-db-list] Request for testing help. I have just released the official beta 1 version of pilot-db 1.1. Please test it out and let me know of any problems. As always, make sure you backup your device completely, and use the uninstall.prc program to remove your original version of db (this will not delete db databases). If you are interested in playing a bigger role in making db a better product, I would ask you to send the form that follows back to me, so I can ask for some help from time to time to track down bugs. I know a lot of you have already offered service, but for those who haven't here's your time to help out the community! Basically, all that would be involved is trying to reproduce bugs so I can find and fix them faster. A lot of my time goes to trying to figure out the exact button presses just to duplicate an error, before I can look at the code and fix it. Anyway, if you're interested here's the info I'd like (this will /not/ be distributed to anyone other than a pilot-db developer.) Thanks, Scott -------------------------------------------------------------------------- Name: Email: Your Palm Device: Palm OS Version: What year did you start using db?: Have you used the emulator before?: Have you compiled db from source?: -------------------------------------------------------------------------- ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Pilot-db-list mailing list Pil...@li... https://lists.sourceforge.net/lists/listinfo/pilot-db-list |
From: Craig B. <cr...@bo...> - 2002-12-17 23:04:54
|
Anyone else seeing a fatal exception every time a card based DB is opened (on the HandEra 330). This was not an issue on previous pilot-db versions. On selecting the DB, there is a pause, and then the Fatal. After the reset, a copy of the database remains in RAM, and can be opened fine. The same occurs regardless of existing or newly V1.1 created databases.\ -Craig Bowers |
From: Craig B. <cr...@bo...> - 2002-12-17 23:43:41
|
Why do the current 1.1 plug-ins have the launchable bit set? Surely we don't want them visible in the launcher (as they currently are, until I turn off that bit). |
From: Scott W. <swa...@my...> - 2002-12-18 15:41:15
|
> Why do the current 1.1 plug-ins have the launchable bit set? > Surely we don't want them visible in the launcher (as they currently are, > until I turn off that bit). This seemed to be the easiest way to get them to show up in the palm's 'delete' menu. However, they also have a 'hidden' attribute which is makes them invisible in the launcher (at least on the OS versions I have tested). Do you use a replacement launcher? If this is a big problem for lots of people, we could explore other options.... -Scott |
From: Craig B. <cr...@bo...> - 2002-12-18 17:32:01
|
> This seemed to be the easiest way to get them to show up in the > palm's 'delete' menu. However, they also have a 'hidden' attribute which > is makes them invisible in the launcher (at least on the OS versions I > have tested). Do you use a replacement launcher? If this is a big > problem for lots of people, we could explore other options.... Ah, yes in fact, LauncherX 1.03 I do see the hidden bit as well. Given that, it would appear to be a LauncherX bug. My Bad. I take it you were looking for a way of giving users the ability to delete individual plugins without using a file manager, as obviously having the same creator code, the plug-ins would be deleted along with DB, if DB was deleted. |
From: Scott W. <swa...@my...> - 2002-12-18 18:28:20
|
> > I take it you were looking for a way of giving users the ability to delete > individual plugins without using a file manager, as obviously having the > same creator code, the plug-ins would be deleted along with DB, if DB was > deleted. Yes, exactly. And most importantly, we want people to be able to remove plugins easily without removing db itself. -Scott |
From: Scott W. <swa...@my...> - 2002-12-19 14:44:59
|
I'm looking into the db3vfs plugin problem. It may take a few days. It looks like I need to use windows to debug the vfs and this is not setup very well yet. -Scott |
From: Craig B. <cr...@bo...> - 2002-12-18 00:02:20
|
Of the issues of old that seem to remain (at least on my 330): -Categorization is lost for card based databases on removal/reinsertion of the card. -The initial view of databases can't be set to page-up or down via the UP/Down buttons, regardless of Global prefs. Which becomes an issue when due to above, the databases all keep getting bumped back into Unfiled. -Databases still reside in /Palm/Launcher, rather than /Palm/Programs/Pilot-DB (or alternative). |
From: Scott W. <swa...@my...> - 2002-12-18 15:38:08
|
On Tue, 17 Dec 2002, Hans Ajiet Holtkamp wrote: > Hi Scott, > > I still have a problem with the Sony HiRes. the 1.1 beta is branch begins between the version of db 1.0.2 and 1.0.3, and I have tried not to change any of the sony hi-res code at all. I think marc finally decided that the sony hi-res api was all but useless, but I'm not sure. I'll check into this 'new' bug you mention. But as for re-esatblishing full hi-res support, I'll have to talk to marc about his experience before I start dealing with windows for development. > > I had mentioned thesehi-res bugs in the past as well. > The only 'new' bug is that the hi-res check box has no > effect! > > This can be duplicated using the Clie-POSE and the > corresponding ROM-File. > > Furthermore after installing DB for the first time and > after the Clie turned off automatically, the screen > remained black - I had to reset the Clie. This cannot > be reproduced, so I presume it only happens the very > first time. This happened with the 1.0.1 as well, but > I thought it was a coincidence, since I could not > reproduce it then either. Hm. Does it happen with the emulator too? -Scott |