gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] Re: [Gnumed-bugs] xDT import problems


From: Jim Busser
Subject: Re: [Gnumed-devel] Re: [Gnumed-bugs] xDT import problems
Date: Thu, 18 Nov 2010 14:14:05 -0800

On 2010-11-17, at 2:34 PM, Karsten Hilbert wrote:

>> --> whereas maybe the *filenames* in the .conf file ARE relevant to "Load 
>> external"?
> 
> They are, indeed. But they are not relevant to the
> xDT-format file browser plugin.

Are the .conf *paths* at least relevant, or does the xDT plugin not even care 
about the *paths*, such that the file picker opens simply to wherever it was 
last opened?

> That's just a difference in coding:
> 
> With PATIENTS.IN files GNUmed searches all available drive
> letters for DRIVE:\MDW2\PATIENTS.IN *automatically* which is
> bound to provide a lot of False Negatives. Hence they aren't
> prompted to the user but rather logged only.

The wiki says GNUmed will parse (at most only) two source files, one on the 
server and one locally ... so in the case of multiple drive letters would 
GNUmed ignore more than two positives?


> With MSVA sources OTOH, all of them are manually configured
> so GNUmed pops up a message informing of the
> misconfiguration.


Might it be meaningfully useful (performance-wise) and also (in the case where 
a praxis would not use MSVA) to comment-out all of the inapplicable sources?






reply via email to

[Prev in Thread] Current Thread [Next in Thread]