bb.donnay-software.com

How many fields does the table have? Does it happen with all kinds of tables or only with a special one?

Hi, Stu. Xbase++ programs are not able to run on multiple CPUs at the same time. By default, they select CPU #1 to run on. You can switch the core for each instance of your application by using "_sysSetCPU" from the XppRt1-lib of your Alaska installation (..\Source\Samples\Solution\smp). This works ...

Hi, Nolberto. CLEAREVENTS works good. I have several huge dialogs which used to flicker, but they stopped this behaviour with "clearevents". You make look for unneeded DC_Getrefreshs, oDialog:InvalidateRect and stuff like this in your code. Maybe you do something inside the EVAL clause of DCREAD GUI...

The VALID clause is evaluated before something happens to the second get and it's HIDE clause. This should work: Procedure Main() LOCAL GetList[0], GetOptions, cWorkOrderType, cValidType, nAmountA, nAmountB DCGETOPTIONS AUTORESIZE cWorkOrderType := cValidType := SPACE(1) nAmountA := nAmountB := 0 @ ...

Hi, Fred. Take a look at the samples in ..\Samples\Soap. You may try the SOAPTEST.PRG to get an idea. If you want to know more about SOAP communication, I recommend to install the freeware "SOAPUI": http://www.eviware.com/Download-SoapUI/download-latest-release.html This software shows and retrieves...

This does the job. The modal window can't be moved outside the parent dialog: #include "dcdialog.ch" #pragma library("dclipx.lib") PROCEDURE appsys() ; RETURN PROCEDURE MAIN() LOCAL GetList := {}, GetOptions := {}, oDialog @ 1,1 DCSAY 'Blabla' SIZE 100,28 @ 29,1 DCPUSHBUTTON CAPTION 'New Window' SIZ...

Hi, Roger.

Below is my current code. Commented out. Are you saying that Alaska still traps the errors?

Oops. I just looked for "ErrorBlock" in the new code you sent me (fonts with DC_AutoRestoreBrowse) and missed that it was already commented out. So forget # 1.

Hi, Chris. Indeed, these are CJPUSHBUTTONS. They work good, but the captions are bitmaps (CJLoadBitmap) with a background color set with DC_BitmapTransparentColor. There is only one cosmetic thing: All other items on this dialog react properly on changes effecting their WHEN-/HIDE-clauses, but somet...

Hi, Roger. This is a short list of things which were already mentioned, but seem to be forgotten: 1. DC_XbpBrowse:ForceStable(): This method still replaces the errorblock during the force-stable-process, so there is no access to the error system if there are errors inside color codeblocks of the bro...

Hi, Bruce.

The "Windows Management Instrumentation" (WMI) should lead to a result. Look at the samples (active x) here:

http://www.activexperts.com/activmonito ... mi/samples