Submitted by jimspoon on 2016/07/21 16:39
I think it might be useful if we could configure the Title Bar to display the "date modified" of the database file.   Or, perhaps put this info in the lower right hand corner of the status bar.  Right now it seems that the time display is the current time, not the modified time stamp of the database file.

Comments

Could do, but as this is a database, the data/time is that of the last database action, which will be very close to the current time. I do keep a "LastEdit" date, which has more meaning. It is used for managing synced copies (see 1. Synchronization between computers using Dropbox)
 
Pierre_Admin
IQ Designer
 

jimspoon

2016/07/22 23:58

In reply to by Pierre_Admin

I guess it might not help too much anyway ... my goal was to have an idea of when it's "safe" to open a database that's stored in a Dropbox folder.  Right now I am using Voidtools Everything on two computers.  I shut down IQ on Computer 1, and watch the Modified Date of the sndb file change in Everything running on Computer 1.  Then on Computer 2, I watch for the Modified Date to change to the Modified Date I just saw on Computer 1.  That way I know that it's safe to load on Computer 2. 
 
I suppose there might be a utility out there to fulfill exactly this need.

Pierre_Admin

2016/07/23 11:39

In reply to by jimspoon

No need to worry. You can leave both open. IQ will warn you when a version has been edited, and offer you to switch to that one. See the doc on dropbox sync
 
 
Pierre_Admin
IQ Designer
 

jimspoon

2016/07/25 17:16

In reply to by Pierre_Admin

I've tried many times to get dropbox sync working reliably, but I've always had problems.  I spent awhile this afternoon trying to get it set up properly.  In the end, edits to items weren't be transmitted properly between computers.  For example, I made changes to a couple of items on my laptop.  I hit Ctrl+S to put the latest laptop version into the sync folder.  The new file appeared in the sync folder on the desktop.  Infoqube detected the new file in the sync folder, and prompted me to update the loaded database from that file.  I did so, but the reloaded database does not contain the changes I made on the laptop!   The items on the desktop appeared as they did before the update.  And then, a "conflicted" version of the laptop database appeared in the sync folder on the desktop (I think you've told me before that the appearance of the "conflicted" version is not a problem ..)
 
It just occurred to me that maybe the grid did not refresh on the desktop after the updated database was loaded?  (but that doesn't make sense).  I looked at Tools > Manage Grids > Options  and "Grid Auto-Updates" is checked.
 
I'll keep trying, but I've always lost changes when using Dropbox sync ... that's why I reverted to the more simple solution - on Laptop and Desktop I load the database from a Dropbox folder.  Before I load the databae I make sure it is closed on the other computer, and that the latest version has synced to the computer I am about to load it on.  . 
 
 

Armando

2016/07/27 16:03

In reply to by jimspoon

[quote=jimspoon]
It just occurred to me that maybe the grid did not refresh on the desktop after the updated database was loaded? 
[/quote]
 
quite possible. Did you retry with a manual grid refresh?
 
-
IQ geek
Windows 8.1
CPU: Intel i5 2.6ghz

jimspoon

2016/07/28 04:49

In reply to by Armando

I did do a manual refresh ... and the changes I made on the laptop still did not show up on the desktop.  Quite a mystery.
 
But it doesn't make much sense to me that a manual refresh would be required.  After all, IQ has just closed the database, copied the newer version (from the sync folder), and reopened it.  So the changes should show up, without a manual refresh.  The older database (without the changes) doesn't exist anymore (except as a backup, I guess).
 
Somehow, it seems, the desktop version isn't getting overwritten with the laptop version from the sync folder.
 
But I'm ok with just keeping the database (not just a sync folder) in Dropbox, and closing it on one computer before opening it in another.  It's less mind-boggling to me.