BUSYBOX() 2

[Richard Kreiss]

Did some more testing.  Found that busybox() does not clear cleanly.  It will erase an color or graphics on the screen when it clears.  

I did use it with a browse that displayed only 12 records and a very small file so the busybox had little opportunity to be read.  However when I set it to busybox("9","47") to display in a blank area on the screen, it clipped off the right side of the browse window and when the browse was cleared, part of the text message was visible. I think this is a bug as the busybox was located to the right of the browse. I programmed busybox("1",49") and it clipped off the upper right corner of the browse and removed the white color background from the screen.  Again it left remnants of itself on the screen when the browse was cleared.

This needs to be corrected and I will send this to FP Support as a bug, although when used as suggested, there doesn't appear to be an issue.


Richard 


  

> -----Original Message-----
> From: Filepro-list [mailto:filepro-list-
> bounces+rkreiss=verizon.net at lists.celestial.com] On Behalf Of Richard Kreiss via
> Filepro-list
> Sent: Monday, February 11, 2019 4:31 PM
> To: 'filepro-list at lists.celestial.com' <filepro-list at lists.celestial.com>
> Subject: RE:BUSYBOX()
> 
> Server - Windows Server 2012
> Work Station- Widow 10 Enterprise
> Network - Gigabit
> 
> 
> 
> I have been experimenting with this function and have noted the following
> results with a browse lookup.
> 
> 
> 1.      Suggest that one does not place busybox in prc sub routine as it executes
> each time the prc runs.  Also after the browse is displayed and one scrolls, the
> busybox reappears.
> 
> 2.      Better place to place busybox is just prior to the browse executing.  It will
> display a message or your message where you want the box to appear. Once the
> records have been selected, the busybox will disappear.  Scrolling will not make
> the busybox reappear as above.
> 
> 3.      You can use color within busybox busybox() "\b5 Your Message \a-". I
> would suggest using a color to bring the users eye to the message.
> 
> 4.      On very fast systems, one might not see the busybox().  I test this against a
> file with just over 27 million records and selected it on those records with a
> specific item number and having the invoice # field ne to empty.  This operation
> took 2.66 seconds before the browse appeared selecting 2408 records.
> 
> I have not tested this directly on my server. On a *nix system I would expected
> this would even be faster.
> 
> As for using busybox elsewhere, I can't say as I have to experimented with it yet.
> It is working as detailed by filePro, however, it would have been nice to show
> some programming examples which would have saved a lot of back and forth.  I
> still would like to see some program examples for busybox not used with a
> browse lookup.  i.e. with sortarray and reading in records to an array.  When I
> program these types of actions, it can appear the program has stopped.  In
> effect it has stopped as it is doing something behind the scenes, sauch as loading
> an array with 300 or so names or sorting an array with 300 or more elements
> with a sort size of 40 characters.
> 
> 
> Richard Kreiss
> GCC Consulting
> 
> 
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: winmail.dat
> Type: application/ms-tnef
> Size: 18613 bytes
> Desc: not available
> URL: <http://mailman.celestial.com/pipermail/filepro-
> list/attachments/20190211/f5fa7ee4/attachment.bin>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 14596 bytes
Desc: not available
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20190211/7cecfcca/attachment.bin>