Sometimes, my value is 99.x and the gantt writes 100%, which is annoying since 99% isn't 100%.

 

The gantt also seems to round off values in mysterious ways as 99.1 will become 100, instead of 99 ; 92.01 is displayed as 90% etc.

 

In any case, 100 should never be anything else than a full 100, I find, as 99.9 could mean that a sub-task isn't completely finished yet.

I spent quite a long time every now and then creating conditional format rules, wondering why they weren't working.

Seems that's because the UI is case sensitive and one needs to enter fields respecting their uppercase and lowercase.

 

I didn't test that extensively, but I did reproduce it with 2 different fields I tested (starting with a capital letter followed by lowercase letters)

 

Can somebody verify that ? Thanks.

 

(I added that as a rule in the manual for the moment, until it's fixed. There are at least one or 2 other things about conditional formats that should be fixed --  they make its usage antiuserfriendly)

WYSIWYG printing works and is very convenient, but :

 

- big black squares appear instead of items bullets and these actually partly cover the items' text

- The check boxes "contour" is way too thick

 

(The biggest problem of course being the item bullets...)

 

 

Mantis : 946

I posted a DB that I created to organize meeting info. There are a few little scripts, auto-assign, equations and conditional formatting doing stuff in the background.

 

If you have suggestions, comments, please don't hesitate.

 

(Some of the structure might change as Pierre is going to change the way filters interact, etc. in IQ)

 

P.S. : And if you have some ideas of what kind of DB we could work on in the  next few months, please suggest. Mark Gregory suggested a GTD implementation a while ago. Other suggestions : CRM DB, Reference/Research DB... These could all be good projects.

E.g. :

1- I copy an item (Selected item --> XML format...) which has a few fields set to "Read-Only".

2- If I paste this item into the DB (or in another one), these fields will remain empty.

 

This seems pretty awkward to me.

- it's not a direct in-cell modification from the user,

- In Explorer If I copy a file that's read only, I can certainly paste it somewhere else without loosing parts of it...

- XML copy/paste shouldn't be considered the same as in-cell edition by the user, or pasting over a cell. XML pasting doesn't paste over anything, it adds an item to the DB.

 

 

Pierre, it seems like a pretty important bug.

And since I have many read only fields, I now understand why I always discover empty fields where there should be data !

 

Comments welcome...

I do not mean to be a pest about this but I really would like to be able to access my bibliographic database from within an outline. Think about it. Who more than a researcher gets more granular with ideas?

 So for example, user could right click & select pending or Foloup or whatever they have chosen as their choice of field(s)

 Per Need some opinions on the manual cross-references you mentioned IQbase to CHM export is planned. 

 

1)  Have you done any planning on this, and how much work it would entail?  I ask, because if it it's not a major effort, I'm thinking it would be a good thing to fairly soon have F1 call up a CHM made from the manual sndb, even if it's incomplete.

 

2) Should I put SNDB to CHM export in Mantis?

Hi group,

 

I've been away from this forum for a week or so. Sorry about that. I was busy doing some consulting work and doing some long due personal things.

 

Still a few more days to go and I'll be back to work

 

Thanks for your patience

 

Pierre_Admin

 

1- Select "Project" field

2- Enter something like "project somiro"

Enter or refresh...

The string will then appear as "project som"

 

Also : why is there an implied wild card at the end of the string and not at the beginning ?

 

(I underlined these a long long while ago, but I almost never use this toolbar, so... But as I'm trying to create a DB made for taking minutes -- see : http://www.donationcoder.com/Forums/bb/index.php?topic=22501  -- I discovered some limitations in a few different places + some bugs here and there. Again in the manage grids where I lost a few grids again... This time in a sample DB. But I'll come back to that.)