| A couple of iTools queries [message #47081] |
Fri, 20 January 2006 11:55 |
James Everton
Messages: 19
Registered: November 2005
|
Junior Member |
|
|
Hi everybody,
Here I am, yet again, asking for a little bit of help from you smart
experts out there. I'm sure some of you may have read my previous
posts, but if you haven't, I'm currently making a specialized
iImage/iSurface tool that has UI Panels created that contain thumbnail
images. When you click on one of the thumbnails, the associated larger
image is brought into the main view. Here's are some of the problems
I'm dealing with now:
#1:
I'm having some problems with the iTools data manager when I make my
tool. Every time I make an instance of my tool, where I create my
parameter set and send it to the iTools registry, the parameter set
gets loaded in, but each consecutive call creates a new parameter set
with _1, _2, _3, etc. at the end of it. In my panel event handler, I
get a hold of the parameter set by using
FindIdentifiers('*My_Parameters*', /DATA_MANAGER)
but how will I know which parameter set to use if there are multiple
parameter sets that have 'My_Parameters' in it?
As a temporary fix, I run ITRESET with the /NO_PROMPT keyword to clear
the data manager, but I would like to find a nice way to run multiple
instances that contain different parameters.
#2:
The most recent tweak that I've been asked to implement is to utilize
iTool's window-layout function and optionally have 4 graphics views
with different data contained in each. What they ultimately want to
happen is to be able to click on an image in panel_a and have one large
image open up in a single view, then if they click on an image in
panel_b, have 4 large images open up in 4 separate views, in the same
iTool window.
There is a VIEW_GRID keyword to the iImage procedure that can be set to
a 2-element vector of the form [column, vector] and this can create the
proper number of graphics views, but it opens up in an entirely new
iImage tool. One idea someone came up with was to always have four
views created, but to minimize three of them in some way so that you
can only see a single view when you need it. I have yet to find out a
way to implement this idea either, but I'm sure you all have a few
tricks up your sleeves that I would love to hear about. :o)
#3:
Panel-diff-itools
The last big problem I'm having also has to do with opening up
different instances of iTools. As you know, I use ITREGISTER to
register my panels with the iTools system, then create my iTool from
the procedure, then go about my business. However, if someone wanted to
close that, go back to the command, then open up iImage, they would
still have all my panels in their new iTool. I need to figure out a way
so that after my iTool is created, I delete the panels from the iTools
registry so new instances of iTools don't have my panels in them.
I thank you very much for having at least read through this post. If
you can provide any help whatsoever on any or all of these problems, I
will very much appreciate it.
Thanks,
- James
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
