On 11/23/2009 6:47 AM, Ulrich wrote:
> Links to specific topics inside the GExperts help, e.g.
> http://www.gexperts.org/tour/index.html?ide_menu_shortcuts.html
> don't work - they lead to the help overview page.

Alexander Halser has donated Help and Manual 5 for our use with GExperts.
I'll to do some testing to see if this fixes things, but it looks like it
will, so far.


If anyone is interested in taking over the maintenance of the help file,
please let me know.  It isn't the type of thing that will take lots of time
to maintain - probably just an hour or two per month - but I'd want someone
who can plan on committing to it longer term (a year or two ideally).   I can
get you the required license for Help and Manual 5.  You would need basic
English writing skills, be able to occasionally update the screenshots, and
occasionally upload the exported help files to the web site.

Erik

On 11/23/2009 6:47 AM, Ulrich wrote:
> Links to specific topics inside the GExperts help, e.g.
> http://www.gexperts.org/tour/index.html?ide_menu_shortcuts.html don't work
> - they lead to the help overview page. This is annoying if one wants to
> show certain GExperts features in web forums or usenet. Is this something
> that could be fixed without too much effort?

If someone can figure out the correct JavaScript to get this working but
still show the table of contents, I could probably fix it.  Right now, each
content frame does something like this, which doesn't quite work:

<script language="JavaScript">
       <!--
           if (top.frames.length==0)
             top.location.href='index.html?ide_menu_shortcuts.html'
       //-->
</script>

If anyone has a copy of Help and Manual 5 they are not using and wants to
transfer the license to us, that is another way to fix this.  The older
vesion 3 we use is fairly limited.  Or, if someone knows of a free but usable
help tool that supports both CHM and html export, and imports some format
that H&M 3 generates, we could also look into that.

Erik

Links to specific topics inside the GExperts help, e.g.
http://www.gexperts.org/tour/index.html?ide_menu_shortcuts.html
don't work - they lead to the help overview page. This is annoying if one wants
to show certain GExperts features in web forums or usenet. Is this something
that could be fixed without too much effort?

Uli.

On 11/19/2009 9:12 AM, alexbeka4600 wrote:
> i am using Gexperts for the first time and i am using it in Delphi 2010
> and have the following problem: i have to replace all TTnTLabel components
> with TcxLabel components but i would like to set the subproperty
> "Style.StyleController" from TcxLabel to a certain value, so i have
> defined in the "Replace-Components-Settings" a mapping; but i get the
> following error: "Error occured: Assigning const failed - wrong
> destination class: TcxLabelEditStyle.StyleController"
> arenīt subproperties allowed?

Subproperties are not supported right now.  It might be possible to add that
if someone wants to try using RTTI.  See: GX_OtaUtils:
GxOtaSetComponentPropertyAsString, GxOtaGetComponentPropertyAsString,
TPropList.AssignPropsToCompByMapping, etc.

Erik

Hi,
i am using Gexperts for the first time and i am using it in Delphi 2010 and have
the following problem:
i have to replace all TTnTLabel components with TcxLabel components but i would
like to set the subproperty "Style.StyleController" from TcxLabel to a certain
value, so i have defined in the "Replace-Components-Settings" a mapping;
but i get the following error: "Error occured: Assigning const failed - wrong
destination class: TcxLabelEditStyle.StyleController"

arenīt subproperties allowed?

thanks in advance for help;
regards,
Alex

On 11/12/2009 5:41 PM, Daniel Maltarollo wrote:
> Nice job, Erik. You certainly proved your point about automatic
> assignment of FocusControl properties. Now I've wrote a simpler and more
> efficient version of that commited code. Instead of aproximating a
> intersection rectangle by brute force, pixel by pixel, it now simply
> traverse all available labels and finds the nearest one.

Your changes look good and your search algorithm is faster.  I did try and
improve things slightly.  The old code would not assign a FocusControl if the
label is both completely above and completely to the left of the control, for
example.  I made sure the label intersects a rectangle to the left or above
the control before it is considered.  I also re-added the distance limit,
such that labels 100 pixels above, for example, are never considered matches.

Checking if the control has TabStop=True was a good idea and should handle
most of the false positive control classes I was manually screening, except
for possibly TButtonControl descendants, so I added that exclusion.

There are more checks we could add like not allowing controls to search over
the top of other controls to locate labels, etc., and I'm sure I will get
requests to auto-select an appropriate accelerator key on the labels, but it
is usable as-is, so I'll stop here.

I appreciate your collaboration with this tool - things generally turn out
better when there are multiple people reviewing the code.

I was a little sad to see the one goto in the GExperts source disappear... :)
   It lived a very short life.

Erik

I went ahead and put this in Subversion.  Your code looked good.  I did
remove most of the code from the action update method, since we've had
problems with anything non-trivial going on there.

I also added the ability to automatically "guess" the FocusControl for each
selected component.  I found it easier to hit Ctrl+A to select all components
and then execute the expert to handle them all at once.  It is fairly smart
and works for labels both above and to the left of the control.  The code did
get much more complex compared to the simple case of selecting a label and
control, though.  I also added an icon, updated all of the projects, added
documentation, etc.

See:
http://gexperts.svn.sourceforge.net/viewvc/gexperts/trunk/Source/Experts/GX_SetF\
ocusControl.pas?view=log

Erik

On 11/7/2009 10:00 AM, Daniel Maltarollo wrote:
> You can download the code from http://drop.io/gx_assignfocuscontrol It
> is just a single unit file currently.
>
> I made it as simple as possible to address a specific need. I always set
> label shortcuts (&) and assign its FocusControl property as a
> convenience to the user and to conform to common UI guidelines. It is
> very hard and boring to manually select the correct control from the
> FocusControl property list, specially on a form with many controls.
>
> I also thought about automatic assignment by proximity. That would be
> great - if it works. I'm concerned about the many different layout
> styles programmers adopt. Some use labels above the control, others use
> to the left, and sometimes even both styles. Sometimes a label may be
> next to a control, even aligned to it, but it is not intended to be the
> control's label. I don't think there is a method that can work /all/ the
> times, but maybe we may came up with a "fair enough" approach.
>
> Another idea I had was to select multiple pairs in sequence, just like
> the Tab Order expert, that respects my selection order as a suggestion
> to tab ordering. This way one could set all the labels at once, exactly
> the way he/she wants.
>
> I just want to comment a few details of my initial code:
>
>     * The "Assign &Focus Control" option is enabled only when two
>       controls, a TLabel and a TWinControl descendant, are selected on
>       the form designer.
>     * The default shortcut (Ctrl+Shift+A) allows you easily select a
>       pair of controls with the mouse and with the left hand stroke the
>       shortcut to execute the expert.
>     * After assigning the FocusControl property, the label is selected,
>       giving a clear visual feedback to the user that it was executed
>       and the FocusControl property is visible at the Object Inspector
>       window.

--- In GExpertsDiscuss@yahoogroups.com, Daniel Maltarollo <daniel@...> wrote:
> "Assign Focus Control" allows you to simply connect a TLabel to any
> TWinControl component visually on the form designer by just selecting
> them both and hitting a key stroke. It's very simple, really. Yet very
> useful, at least for me. :)
Sounds good to me.