Chris,
I just tested this and had no problems with Exceed 7.1. Open your
log file for Exceed and make sure that it is loading your xrdb file
correctly. I put the line
DX*vpeCanvas.allowOverlap: True
in C:\Documents and Settings\All Users\Application
Data\Hummingbird\Connectivity\7.10\Xrdb.txt. Told it to reload the
xrdb and viola overlapping modules with no problems.
David
[For anyone joining this thread late, the tips below relate to openDX
on Windows XP.]
Argh. Of course, today it works: my only excuse is that since I
wasn't sure if the actual string had changed (DX*? openDX*?), it
doubled the number of tests and since the exact order matters in
starting Exceed, loading XRDB, and starting DX, I didn't manage to
find the correct permutation.
One minor correction to the above: the path is:
C:\Documents and Settings\All Users\Application
Data\Hummingbird\Connectivity\7.10\Exceed\Xrdb.txt (can also be
xrdb.txt)
Following your instructions, I managed once to hand-load XRDB and get
DX to overlap, but it was not working every time. So then I
discovered the Exceed config for Screen Definition contains an
Autoload XRDB button that I engaged. This is what seemed to make the
difference in making this work reliably, esp. from a cold start.
So thanks for the details!
More info on our other conversation:
After setting the Environment Variable "DXMEMORY" to "1000", when I
start openDX by clicking the openDX application icon or shortcut, the
server will autostart as expected. However, double-clicking .net
icons still causes the "Connection to server localhost has been
queued" message (and no running server until I hand-start it). Still
mystified by that, but this is just FYI, as I know you said you
aren't having this problem. The error dialog appears on top of the
openDX logo window after the UI has opened up. I tried setting the
ENV VAR first as a user ENV VAR, then today, redid it as a system ENV
VAR, rebooted, and tried again. Nope, same (mis)behavior. As before,
the solution is to open the Connection:Start Server:Options dialog,
set memory to 1000 then the server launches and runs. This only seems
to be a problem when launching by double-clicking a .net icon as with
the ENV VAR in place, launching openDX by clicking the icon starts
the server with the designated amount of memory (checked via the
Message Window's startup message).
The obvious big advantage to clicking .net icons, is that DX then
"homes" to that startup directory instead of to the Program
Files/OpenDX directory as when launching from the openDX icon. The
latter necessitates navigating/changing filters to get to the data
directories for the current project.
--
Chris Pelkie
Managing Partner
Practical Video LLC
30 West Meadow Drive, Ithaca, NY 14850
