×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I don't know what I did wrong when I installed rdi 9.0 on this new
computer, but it does not work like it did on version 7.
(By the way, I was able get F1 help text working by renaming the
directories and restarting. Thanks.)
So first, the compile button is no longer on the toolbar. I am sure I
can eventually figure out how to add it and since there is a menu item
to compile, I can get the job done. Just not in 1 click.
Under v7, when I had compile errors, there was a nice box under the lpex
editor that listed the errors. Now the box is in the upper right
corner. If I click on enough things, it moves down to the bottom, but
it would be nice to have it always be on the bottom like it used to be.
But I said my problem was with debug.
I cannot get field values when I hover the mouse over the field. There
is a monitor window that seems to have the current values, but it sure
is not the same as seeing the values by positioning the cursor.
I went to preferences, debug and under debug editors, I have allow hover
evaluation checked and always use debug editor when debugging.
I also checked update production files. Hey, I never make any
mistakes on production data. At least not yet. Seriously, this is not
an issue for us.
But when I hover the mouse over the field, nothing happens. What am I
missing here?
One thing I did different during install was put my repository directly
off the C: drive, not program files or app data or wherever the default
windows location is.
---Dale
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.