Ted, I ran into something similar to this. I don't have the code immediately available, but I think the solution was in the pageframe.Init was to run through all the pages (set the .ActivePage) then finally set the page you want to be displayed.
If that doesn't work, I'll try to hunt up the code when I get home tonight. Fred On Tue, Jul 21, 2009 at 10:51 AM, Ted Roche <tedro...@gmail.com> wrote: > We have a large legacy app ported from Foxbase through DOS into VFP > which we're moving from 7 to 9 in order to get some better behavior in > Vista. We're running into a bunch of issues. Luckily, the "What's New > in 8" and 9 books have addressed a bunch of the issues -- thanks, > guys! -- but there's still a few outstanding problems. > > Google and searching the ProFox archives haven't brought immediate > answers, so I thought I'd toss it out here with insufficient details > in case anyone had seen something similar and knew a specific fix. > > This is VFP9 SP2 running in WinXP Pro. There's a VFP form with a > pageframe. On the pageframe page 1 there's a mover control consisting > of the usual lists and buttons (long ago, this was a Mere Mortals > framework-based app, but it's somewhat branched off on its own). In a > textbox lostfocus on page1 there's a routine that actually calls a > click on page2 (yeah, it should be a method, not an event call, that's > bad, but it had been working in VFP7). When we moved the page into > VFP9, we'd see a refresh that brought some of the controls from page2 > bleeding through page1. A fix to this was found with a windows API > call that does the WinAPI WindowRefresh for the entire application, > but not the other symptom. Here's the weirdness: the focus is on the > left listbox of the mover, and keystrokes to manipulate the mover work > correctly (arrow keys to navigate, space to highlight, Enter to select > and move) but clicks on the listbox display no result: focus does not > move, items don't get selected or moved. It's like the keyboard knows > what the activecontrol is, but the mouse has gone off somewhere else. > > Has anyone seen similar behavior when moving to VFP9 and know of a > solution / work-around? I'll be doing some more debugging to try to > see if I can get the problem narrowed down a little better. > > -- > Ted Roche > Ted Roche & Associates, LLC > http://www.tedroche.com > > [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/3392e7100907211137y4e381b9chc19d3d9d2952b...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
