[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [amibroker] A second DLL challenge? --Half done



PureBytes Links

Trading Reference Links

Tomasz,

I have succeeded in doing #1 on the list below.   I can have unique  
parameter names that "appear" to be the same name, even though I only  
have one _Section_Begin() for my whole parameter window now.  So as  
far as AB is concerned, the entire Flexible Parameters system is one  
section.  I did not need to use a DLL for this, just AFL (Just because  
one way is "not feasible" does not stop me from trying to find another  
way).

So for #2 on the list, changing the ParamToggle button (or name)  
background color.  Can you see the possibility of me being able to use  
one of the following approaches to succeed with this?

A.  Continue to rack my brains for a new AFL command that will add  
color to the Parameters Window that you like and will implement?  
(#1448 is my latest attempt)

B.  Somehow change the color of entries in the Parameters Window after  
the fact through a DLL.

C.  Expose some variable that a DLL could modify to effect the color  
change.

If none of these looks likely, could you suggest another approach that  
is feasible?

I am a believer in using on-chart buttons for normal real time  
interactions while trading AND using the Parameter Window for the  
hundreds of "system" parameters that are primarily used for system  
creation and testing.  I believe both are needed long term and I am  
proceeding in the direction of trying to get the most additional  
functionality out of both in my systems.  I appreciate your support in  
helping me extend my AmiBroker systems.

Best regards,
Dennis

On May 12, 2008, at 12:05 AM, Dennis Brown wrote:

> Tomasz,
>
> I was very happy to succeed in making my first DLL that gave me the
> functionality I needed without your adding anything new to AFL.  I
> updated the article I am writing for the UKB to reflect the simpler
> setup now because of this.  Thank you for all your help with this.
>
> There are now just two things that stand in the way of what I consider
> a near perfect implementation of Flexible Parameters.  I have put in
> requests in the suggestions for them #1440 and #1441.
>
> However, if it is possible for me to implement these things from an
> external plugin, I am willing to put in the work to make it happen so
> that I can feel good about what I give away to the UKB.
>
> My problem is that the _Section_Begin("Name") command combines several
> different functions.   While this makes the modular Drag Drop work
> simply, it makes it difficult for my large monolithic systems to have
> the same functionality and visual appeal of your vision for the
> Parameters Window.
>
> I need to do two things to give this work the final polish.
>
> 1.  The most important of the two.  I need to make a command that will
> set the internal SectionName to to the "Name" I specify:
> SectionNameSet("Name");  I want to do this without doing all the rest
> of the stuff that the _Section_Begin("Name") command does like set up
> a Parameters Window top level menu button.  I just want to change the
> internal "Hash" number/string to a new value so that the parameter
> statements (which use the same names) following it will have unique
> internal names and will not interfere with each other.  This provides
> just the critical functionality to stop using the _Section_Begin()
> command in funny ways by my AFL.  Perhaps there is just some way that
> I can add some non-displaying characters to the parameter name to make
> this unique naming happen.
>
> 2.  I would like a way to get a particular paramTrigger() name/label
> to have a color all the way across the the Parameters Window item that
> matches the way the Section buttons look.  This could be done before
> or after the fact, as I can tell which line in the window I would like
> to change the color of with a bit of work in my AFL.  This brings back
> the basic look to the pseudo-sections that I provide in my AFL.  Being
> able to extend the active button area across the whole line like a
> section menu button would be adding gravy.  Of course without #1, #2
> is pointless.
>
> In summary, If I could do both of these things, I could get rid of my
> _Section_Begin() commands (except the first one) so that I am no
> longer using them in ways that were not intended.  That way I will not
> have to worry as much about future changes to the way the Parameter
> Window might function --like saving the open state of the menus.  At
> the same time, I can bring the basic look and feel in line with what
> you normally provide in the Parameters Window.
>
> I appreciate your comments on the possibility of my being to do this
> externally.
>
> Best regards,
> Dennis

------------------------------------

Please note that this group is for discussion between users only.

To get support from AmiBroker please send an e-mail directly to 
SUPPORT {at} amibroker.com

For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG:
http://www.amibroker.com/devlog/

For other support material please check also:
http://www.amibroker.com/support.html
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/amibroker/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/amibroker/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:amibroker-digest@xxxxxxxxxxxxxxx 
    mailto:amibroker-fullfeatured@xxxxxxxxxxxxxxx

<*> To unsubscribe from this group, send an email to:
    amibroker-unsubscribe@xxxxxxxxxxxxxxx

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/