Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Progress bar doesn't want to disappear from the screen
Message
 
 
To
20/08/2001 17:33:29
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Miscellaneous
Thread ID:
00546304
Message ID:
00546520
Views:
15
Nancy,

I don't have paint() in the code (I put it temporary, then commented out, then deleted at all). I'll retest this code tomorrow trying to comment out piece by piece. I can not debug it, because as I said, Grid.MyForeColor method fires automatically in an endless loop. I may try to prevent it from firing, but it may be not a clean test, since I have to have it anyway.

I agree, that I have to determine the cause and correct solution. I guess, I just was tired, that this "thing" polluted my form and when finally I got it disappeared, I stopped my testings. In addition, I had lots of other applications to work on.

Anyway, I'm going to check it tomorrow again closely.

Thanks again.

>>>>The solution was posted in my reply to Sergey. Here it is:
>>>>
>>>>if m.lnCount=m.lnReccount
>>>>         oProgBar.SetPos(m.lnReccount)
>>>>    endif
>>>>    .lockscreen=.f.
>>>>    oProgBar.Hide()
>>>>	oProgBar.Release()
>>>>	release oProgBar
>>>>	doevents()
>>>>	mouse at mrow(), mcol()
>>>>	.lockscreen=.t.
>>>>
>>>
>>>Okay. That's the code, but which bit is the actual solution?
>>
>>Setting lockscreen to false in conjunction with doevents.
>
>Really? If you comment out DOEVENTS and Paint(), for example, the problem is still there? And you've suspended the program after the release to confirm that thisform.lockscreen is .f.?
>
>> I think, I tried without doevents() before, and it didn't work, but I tried soo many things, that I'm really not 100% sure. At least, this particular piece works :)
>
>Okay. You get what I'm trying to get you to do, right? You post a lot indicating that you've had a problem then written some code that somehow seems to fix the problem but you're not sure what the problem was, and you're not sure what code fixed it. I'm not sure you get what I meant by "mysteriously fixed code tends to just as mysteriously reoccur." Then you'll be inclined to post this solution to someone with a similar sounding problem but it may or may not be appropriate.
>
>I use a progress bar control on a form subclass a lot and haven't had to use either paint() or doevents for it. Not to say you don't need it, but you haven't convinced me. For whatever that is worth, which ain't a lot.
If it's not broken, fix it until it is.


My Blog
Previous
Reply
Map
View

Click here to load this message in the networking platform