Hi Chris,
thank you for your suggestion, that approach might be useful for us. In most cases, the exact numeric type doesn't matter, but we have some type checking code that gave us issues.
Search found 6 matches
- Thu May 22, 2025 12:45 pm
- Forum: Product
- Topic: Strange typing behaviour in the X# macro compiler
- Replies: 2
- Views: 7090
- Wed May 21, 2025 2:55 pm
- Forum: Product
- Topic: Strange typing behaviour in the X# macro compiler
- Replies: 2
- Views: 7090
Strange typing behaviour in the X# macro compiler
Hi all,
We have an application ported from VO that heavily relies on macro execution, and we discovered the following behaviour in the macro engine when evaluating expressions:
local xMonth as usual
xMonth := MExec(MCompile("Month(Today())"))
// Result: xMonth contains Long (Int32)
xMonth ...
We have an application ported from VO that heavily relies on macro execution, and we discovered the following behaviour in the macro engine when evaluating expressions:
local xMonth as usual
xMonth := MExec(MCompile("Month(Today())"))
// Result: xMonth contains Long (Int32)
xMonth ...
- Wed May 21, 2025 1:55 pm
- Forum: 3rd party products
- Topic: Typo in cOleRichEdit:Destroy()?
- Replies: 1
- Views: 5207
Typo in cOleRichEdit:Destroy()?
In the Destroy method of the Classmate cOleRichEdit control, I found the following code:
IF ! SELF:oIRichEditOle==NULL_OBJECT
nObjects:=SELF:oIRichEditOle:GetObjectCount()-17
FOR nLp := 0 UPTO nObjects
...
NEXT
Surely, this has to be a typo? Subtracting 1 from the object count would make ...
IF ! SELF:oIRichEditOle==NULL_OBJECT
nObjects:=SELF:oIRichEditOle:GetObjectCount()-17
FOR nLp := 0 UPTO nObjects
...
NEXT
Surely, this has to be a typo? Subtracting 1 from the object count would make ...
- Mon Jun 03, 2024 3:43 pm
- Forum: 3rd party products
- Topic: ReportPro 3.60 for XSharp 2.60 memory exception
- Replies: 20
- Views: 24901
Re: ReportPro 3.60 for XSharp 2.60 memory exception
Well, we changed these variables to STATIC and it fixed the problem . Release builds with compiler optimization for the entire solution can now print documents without crashing. I've only done some preliminary testing, but it looks good so far. Beforehand, it basically couldn't print at all.
It's ...
It's ...
- Thu May 30, 2024 2:53 pm
- Forum: 3rd party products
- Topic: ReportPro 3.60 for XSharp 2.60 memory exception
- Replies: 20
- Views: 24901
Re: ReportPro 3.60 for XSharp 2.60 memory exception
Chris wrote: Thu Apr 25, 2024 9:18 am a set of slightly newer RP3 files, they might make a difference as we fixed another issue that could be related recently.
Hi Chris,
do these have changes within Classmate Gui? Maybe we should try that fix?
- Wed May 29, 2024 12:19 pm
- Forum: 3rd party products
- Topic: ReportPro 3.60 for XSharp 2.60 memory exception
- Replies: 20
- Views: 24901
Re: ReportPro 3.60 for XSharp 2.60 memory exception
Greetings,
We observe the exact same problem. It turns out that printing through the cPrinter class crashes with memory errors whenever we compile Classmate with the "Build/Optimize" flag. It only happens when using the printer DC, print preview is not affected. Disabling Optimize in Release builds ...
We observe the exact same problem. It turns out that printing through the cPrinter class crashes with memory errors whenever we compile Classmate with the "Build/Optimize" flag. It only happens when using the printer DC, print preview is not affected. Disabling Optimize in Release builds ...

