Dear guest !

Welcome to Team Developer Community Forum. A place created by the community, for the community !

This is a resource for Q & A and discussion about everything related to OpenText Gupta Team Developer, SqlBase, TD Mobile and Report Builder.
It is the alternative for the OpenText customer forums which can only be accessed with an active support contract.

Please register your account now. It will make you part of the active community.
Also, this guest message will not be displayed for registered users.

As a bonus, registered users have access to the 'Newsgroups' subforum, holding 10 years worth of posts from the good old Gupta newsgroups.

Having an account gives you the opportunity to ask questions and get help from others.
We hope this free gathering will help you and the community getting forward!

Best regards,
The forum site admins.

RACON and cSplitter

General discussion forum about all things Team Developer 7.x
Post Reply
Posts: 1
Joined: 14 Jul 2017, 08:02
Location: Germany

RACON and cSplitter

Post by Marco » 17 Jul 2017, 15:08

Hello all,

we're currently migrating from 5.2 to 7.0.2. but we're running into some problems.

First problem:
We used the RACON.SQLWindows.UserInterface.dll from the wiki to paint dynamically created buttons in the "correct" color (same color as the standard buttons).
Unfortunately, RACON is not available for TD 7.0. (yet?). Is there another way to do the painting? (Button1.jpg is TD 5.2 with RACON, Button2 TD 7.0 without RACON and Button3 is how the normal buttons look.)

Second problem:
We still use "cSplitter". The splitter itself is painted correct, but the elements "attached" to the left or right side of the splitter act as if the splitter is not existent, e.g. the table that should only be shown on the left side of the splitter goes across the whole window. Moving the splitter has also no effect.
Is there a replacement for the cSplitter? Couldn't find anything via google or any forums.

Maybe a third problem:
Rich Text Controls - when above mentioned splitter is moved, we call SalSetWindowLoc ( hWnd, nX, nY ), hWnd beeing the rtc element. This results in a "The internal Memory has become invalid" message, which is not very helpful. The window handle is valid and functions like SalIsWindowEnabled work/return TRUE.

Also, if the rtc-ToolBar is not visible at design time and SalRTFShowToolBar is called during runtime --> "The internal Memory...". Same applies for SalRTFShowToolBarButton.

I'll attach a sample for problem 2 and 3 tomorrow, though I hope there's a replacement for the cSplitter control - never really liked that one..

Regards Marco
button3.jpg (2.17 KiB) Viewed 76 times
button2.jpg (4.66 KiB) Viewed 76 times
button1.jpg (4.55 KiB) Viewed 76 times

Post Reply

Return to “General Discussion”

Who is online

Users browsing this forum: No registered users and 1 guest