Search found 283 matches
- 5 Feb 2019 15:53
- Forum: Visual Prolog
- Topic: Dialog vs Form interactions
- Replies: 6
- Views: 114
Re: Dialog vs Form interactions
"I suspect you think the Rectangle in a printResponder is something different than what it is. This is what it is: The part of the client rectangle that needs to be repainted. " Ahhh ... thank you very much! You are right, I erroneously assumed that the Rectangle in the paintResponder was the client...
- 5 Feb 2019 14:33
- Forum: Visual Prolog
- Topic: Dialog vs Form interactions
- Replies: 6
- Views: 114
Re: Dialog vs Form interactions
OK, here it is as a VP 8.02 project. The problem is how I am handling GDIP in the onPaint/3 event in graphDisplayForm.pro (Line 44). Other "empty" forms behave normally. My idea is that the rugPainter object stores the graphics information on creation and Rug:paint() uses that information to draw th...
- 4 Feb 2019 20:21
- Forum: Visual Prolog
- Topic: Dialog vs Form interactions
- Replies: 6
- Views: 114
Re: Dialog vs Form interactions
VIP Version 7.502
I've tested it several different ways, using vipCommonDialogs type dialogs and my own small dialogs and forms.
I've tested it several different ways, using vipCommonDialogs type dialogs and my own small dialogs and forms.
- 4 Feb 2019 18:23
- Forum: Visual Prolog
- Topic: Dialog vs Form interactions
- Replies: 6
- Views: 114
Dialog vs Form interactions
How do I make form windows repaint themselves when another form window passes over them? Consider two scenarios: 1. Open form FormF then open dialog DlgD. If I move DlgD around on top of FormF then FormF repaints as expected. 2. Open two forms, FormA and FormB. If I move FormA around on top of FormB...
- 7 Jan 2019 13:54
- Forum: Visual Prolog
- Topic: Send to Background-Bring to Top
- Replies: 17
- Views: 434
Re: Send to Background-Bring to Top
Here's a suggestion from someone who knows nothing about the complexity of your project: Create an internal fact database in dialogA and populate it with information to control what the user needs to see or wants to revisit. Put human-readable strings in the database that can be used to populate a l...
- 6 Jan 2019 15:07
- Forum: Visual Prolog
- Topic: Send to Background-Bring to Top
- Replies: 17
- Views: 434
Re: Send to Background-Bring to Top
"so many instances of B, maximizing and comparing the dialogs becomes tedious." Yes ... but you could put the B-dialog identifiers into a database (or a list in a mutable variable) in the A-dialog as you create them. This might not correspond to what you are trying to achieve, but have you consider...
- 6 Jan 2019 4:34
- Forum: Visual Prolog
- Topic: Send to Background-Bring to Top
- Replies: 17
- Views: 434
Re: Send to Background-Bring to Top
This might have an effect you desire -- just make dialogB invisible (or minimized) when you press Cancel. Put this in dialogB: predicates onCancelClick : button::clickResponder. clauses onCancelClick(_Source) = button::noAction :- This:setState([vpiDomains::wsf_Invisible]). You will need to keep tra...
- 5 Jan 2019 0:26
- Forum: Visual Prolog
- Topic: Send to Background-Bring to Top
- Replies: 17
- Views: 434
Re: Send to Background-Bring to Top
Take a look at this in the IDE help: vpi::winBringToTop/1 winBringToTop : (vpiDomains::windowHandle WindowHandle) language c. Brings the window WindowHandle to the front of the screen. Description Use the winBringToTop predicate to uncover any window that is partially or completely obscured by other...
- 7 Dec 2018 14:52
- Forum: Visual Prolog
- Topic: Wheel Scrolling in Grid Example
- Replies: 4
- Views: 269
Re: Wheel Scrolling in Grid Example
Dave, Should vpiGridgrid_vmove_cells_area be vpiGrid::grid_vmove_cells_area ? Add listener " addVScrollListener(onVScroll)" confuses me. Do you mean add a VScroll listener (onVScroll) ? Also, where is activeGrid defined? I can't find it. Thanks for digging into this. I hope your tweaks get added int...
- 19 Nov 2018 17:02
- Forum: Visual Prolog
- Topic: Find in Files, a little quirk
- Replies: 7
- Views: 1071
Re: Find in Files, a little quirk
The vipprj files in the two projects do not have replicate entries. I backed up both projects and tried deleting the TaskWindow package using the IDE. I got a message "It isn't allowed to delete the task window resource from the project." Despite the message, it deleted all the resources in the Task...
- 17 Nov 2018 16:19
- Forum: Visual Prolog
- Topic: Find in Files, a little quirk
- Replies: 7
- Views: 1071
Re: Find in Files, a little quirk
The quirky projects are two that I created using VP 7 and later copied to my VP 8 development tree and continued development there. How does Find in Files populate the search list?
This quirk, of course, is at the most trivial level of all quirks.
This quirk, of course, is at the most trivial level of all quirks.

- 16 Nov 2018 13:31
- Forum: Visual Prolog
- Topic: Find in Files, a little quirk
- Replies: 7
- Views: 1071
Re: Find in Files, a little quirk
Thanks for checking. I'll keep an eye on it.
- 14 Nov 2018 14:45
- Forum: Visual Prolog
- Topic: Find in Files, a little quirk
- Replies: 7
- Views: 1071
Re: Find in Files, a little quirk
I'm using VP Build 802. The behavior seems somewhat inconsistent, but this is what I know for sure so far: * It doesn't happen with all projects, but happens with more than one. * I don't think it's related to 32 vs 64 bit projects. * It happens when searching from the top of the project tree (the f...
- 12 Nov 2018 15:03
- Forum: Visual Prolog
- Topic: Find in Files, a little quirk
- Replies: 7
- Views: 1071
Find in Files, a little quirk
"Find in Files" (Ctrl-Shift-F) displays "found" lines in Task Window twice, but other files search results are OK.
- 9 Nov 2018 20:38
- Forum: Visual Prolog Tips & Samples
- Topic: xyChartDemo - GDIPLUS XY graphing demonstration
- Replies: 2
- Views: 1726
Re: xyChartDemo - GDIPLUS XY graphing demonstration
UPGRADE FOR Vip8: The original version of xyChartDemo was developed with Vip7 and is not plug-and-play compatible with Vip8 due to some minor changes in the version 8 PFC Graphics class. I have made the necessary changes (mostly in Chart.pro), added a few trivial features (e.g., save and recall nam...