OK, I was just reviewing the code in the custom Method within this sub-classed Grid - and I noticed the Comments on the following 3 lines of code: #DEFINE VK_lSHIFT 0x10 && Relocate to a header file #DEFINE VK_lCONTROL 0x11 && Relocate to a header file DECLARE INTEGER GetKeyState IN WIN32API INTEGER && Relocate to where WinAPI calls are declared
Although the Author of the code did Not specifically mention this on Foxite - it looks like I must change the code according to his comments above.
Is it possible that because the Define & Declare commands are happening MULTIPLE times - that this may be what is causing VFP to crash?
I haven't had much hands on experience with usage of the #Define command - although I have modified code here that HAS the commands in them - I just haven't added them much into the code myself...
-K-
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Kurt Wendt Sent: Tuesday, February 02, 2016 12:17 PM To: profoxtech@leafe.com Subject: RE: Multi-Select Grid & Foxite Code Issue (Was...RE: A Question of ListBoxes)
Ouch - I wish I knew about that earlier! Maybe it would have been a better solution. Does it have a Multi-Select feature in this SuperGrid?
So - an additional follow-up to my last comments.
I've been doing testing & dev. using Two sessions of VFP. I Mod a screen in the one instance, but I Always run a test within the Other session. And, in the session where I test, I rebuild the APP using the BUILD command line option & then run the APP.
And, since I am constantly running the App in that session - I'm wondering if THAT has something to do with it - that I keep re-running the APP. So, just now as a Test - I compiled an EXE. And, I ran that EXE multiple times. I even went into that particular Form - which is accessed by a button on the main form, and ran that form that has the Grid - multiple times - each time going back to the primary form and selecting a different main data record. But, still - it did NOT Crash once.
So - maybe the crashing problem DOES have to do with re-running of the APP. Maybe something is being left behind, not cleaned up, after the App is run each time. Of course, I am just taking a WAG here as to the problem.
-K-
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Tuesday, February 02, 2016 12:09 PM To: profoxtech@leafe.com Subject: RE: Multi-Select Grid & Foxite Code Issue (Was...RE: A Question of ListBoxes)
Not to confuse the issue more but Craig Boyd has a brilliant VFP class called gridextras that gives you all kinds of functionality like column sorting, filtering, exporting, etc. You basically drop the class on your form, set a few properties and voila! Supergrid!
--
rk
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Kurt Wendt Sent: Tuesday, February 02, 2016 12:06 PM To: profoxtech@leafe.com Subject: RE: Multi-Select Grid & Foxite Code Issue (Was...RE: A Question of ListBoxes)
Well - the current version of the system has 2 listboxes. However, there are several changes that were requested - which can NOT be done with the Listbox: 1 - Easily resize the columns 2 - Click on a column header to allow user to sort data by that column
Both of these features are typically implemented in Grids. That's why I'm trying to implement the request using the Multi-Select Grid coding that was displayed on Foxite.
-K-
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of AndyHC Sent: Tuesday, February 02, 2016 12:01 PM To: profoxtech@leafe.com Subject: Re: Multi-Select Grid & Foxite Code Issue (Was...RE: A Question of ListBoxes)
out of interest, take a look at the datapicker (?) class in xsource - does exactly that with two listboxes
On 02/02/2016 21:18, Kurt Wendt wrote:
... was previously implemented w/2 ListBoxes - the users selects records on 1 listbox - then hits a button to have those records pushed over to the other listbox.
[excessive quoting removed by server]