Re: [mv] mv_range_lock doesn't work in MV4!

[Mike Heins <mikeh@minivend.com>]

******    message to minivend-users from Mike Heins <mikeh@minivend.com>     ******

Quoting jojo@buchonline.net (jojo@buchonline.net):
> 
> i´ve read my codes once and once more. But i get no success.
> This work:
> 
>  [page scan/ml=10/cs=yes/su=yes/se=Kind/sf=title/rl=erjahr/rm=2000/rx=2000]TEST[/page]
> 
> This doesn´t work (but works in MV 3.15 very fine):

I took out the ability to combine range look with coordinated search, and
I think I documented that in WHATSNEW. The reasons were performance, code
complexity, and correctness. If you are strong of stomach, try reading
the get_limit subroutine in Search.pm. 8-)

You can do instead:
 
 <FORM ACTION="[area search]" METHOD=POST><INPUT TYPE=hidden NAME="mv_search_map" VALUE="
                                mv_searchspec=search_min
                                mv_searchspec=search_max
                                mv_searchspec=search12
                                mv_searchspec=search14
                                mv_searchspec=search1
                                mv_searchspec=search11
">

                <INPUT TYPE=hidden NAME="mv_column_op" VALUE=">=">
                <INPUT TYPE=hidden NAME="mv_column_op" VALUE="<=">
                <INPUT TYPE=hidden NAME="mv_numeric" VALUE=1>
                <INPUT TYPE=hidden NAME="mv_numeric" VALUE=1>

                <INPUT TYPE=hidden NAME="mv_search_field" Value="author">
                <INPUT TYPE=hidden NAME="mv_search_field" Value="title">
                <INPUT TYPE=hidden NAME="mv_search_field" Value="0">
                <INPUT TYPE=hidden NAME="mv_search_field" Value="verlag">
                <INPUT TYPE=hidden NAME="mv_search_field" Value="erjahr">
                <INPUT TYPE=hidden NAME="mv_search_field" Value="erjahr">
                <INPUT TYPE=hidden NAME="mv_search_match_count" Value="0">
                <INPUT TYPE=hidden NAME="mv_coordinate" VALUE="yes">
                <INPUT TYPE="hidden" NAME="mv_matchlimit" VALUE="10">
                <INPUT TYPE="hidden" NAME="mv_min_string" VALUE="3">

 [L]Author[/L] :<INPUT NAME=search12 VALUE="">
 [L]Title[/L]-[L]Catchword[/L] :<INPUT NAME=search14 VALUE="Kind">
 [L]Code[/L] :<INPUT NAME=search1 VALUE="">
 [L]Publisher[/L] :<INPUT NAME=search11 VALUE="">
 
 <INPUT TYPE=hidden NAME=mv_range_look VALUE=erjahr>
 min. <INPUT TYPE=text NAME=search_min VALUE=2000>
 max. <INPUT TYPE=text NAME=search_max VALUE=2000>
 
 <INPUT TYPE="hidden" NAME="mv_first_match" VALUE=""></TD>
 <INPUT TYPE="hidden" NAME="mv_doit" VALUE="search">
 <INPUT TYPE=image SRC="icon/[L]Search[/L].gif" BORDER=0 NAME="[L]Search[/L]"></TD>
 <INPUT TYPE="hidden" NAME="mv_searchtype" VALUE="text">
 </FORM>

(I assume the type=hidden is an error on the min/max values.)

By the way, this isn't documented yet, but you can easily build coordinated
scan links. Perhaps I should make this available in the search form....

[page 	search.0='
		sf=foo
		se=bar
	'
	search.1='
		sf=buz
		se=baz
		op=ne
	'
	search.2='
		sf=zip
		se=[value zap]
		op=gt
		nu=1
	'
]Search for foo containing bar, buz!=baz, zip > value of zap[/page]

The advantage of this is that you don't have to coordinate your op=
and nu= and cs= things, it is done automagically. You can also use the
new search grouping feature of MV4, which allows the equivalent of (
foo =~ bar AND buz!=baz) OR zip>zap.  All this just awaits documentation
time.... 8-)

-- 
Internet Robotics, 131 Willow Lane, Floor 2, Oxford, OH  45056
phone +1.513.523.7621 fax 7501 <mikeh@minivend.com>

When the only tool you have is a hammer, all your problems tend to look
like nails.  -- Abraham Maslow
-
To unsubscribe from the list, DO NOT REPLY to this message.  Instead, send
email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
Archive of past messages: http://www.minivend.com/minivend/minivend-list