My 1st Grid Component on the Desktop

[Tim Kiebert]

Re: My 1st Grid Component on the Desktop

From the error message it seems to be tripping over the 'tablename' variable. May be it needs to be changed as well. But if it works on first opening I would have thought that it was ok. Can you post us the whole function?

[MoGrace]

Re: My 1st Grid Component on the Desktop

Hi Tim,
Here is the script - but without my table. Hope you can see what I can't!

[Tim Kiebert]

Re: My 1st Grid Component on the Desktop

I am having a look. I changed the xml definition to use your previous sample table and am seeing the behavior you described. it is a weird one. Even rerunning the function I get the same result. Hmmmm

[MoGrace]

Re: My 1st Grid Component on the Desktop

It definitely has something to do with the card statement. I used the rollup code from another function that displays a list view control - no problems there. Since this is actually two dialogs in one (a minor example is in the Learning Xdialog app); it seems like you could make two functions and call one from the other to achieve the desired result.

At one point, I actually had it calling the browse as modal and the rollup as modeless - which I will do if I can get the rolldown part to work correctly.

I also tried closing the main modeless xd in the rollup code using different dlg_titles - but that just caused the whole thing to vanish... ;)

Perhaps it is the scope of the variables that needs changing?

[Tim Kiebert]

Re: My 1st Grid Component on the Desktop

Hi Robin,

I played around with the scope of the variable without any luck. In the debugger I can see the proper values for the elements of the a5_XdialogDefaultBrowse() function the second time around but that function still seems to fail. Can only make wild guesses on what is going on there. I was thinking something might be being left in memory. The strange thing is that if you repeatedly run xd_Brw_PO() the dialog gets refreshed without a problem. This may be a candidate for a bug report.

As a work around I a created a solution by running the rollup dialog with its own title and then hiding and showing either one. Code is below.

First the new rollup title

dim rollup_title as C = "Search Orders rollup"

then change the main event code to

if a_dlg_button = "close" then 
	If ui_modeless_dlg_exist(rollup_title)  
		ui_modeless_dlg_close(rollup_title)
	end if
	ui_modeless_dlg_close(dlg_title)
end if 

if a_dlg_button = "ROLLUP"   
	if ui_modeless_dlg_exist(rollup_title)
		ui_dlg_show(rollup_title)
	else
		ui_modeless_dlg_box(rollup_title,rollup_body,rollup_code)	  
	end if
	ui_dlg_hide(dlg_title)  
end if

and the rollup code

if a_dlg_button = "CLOSEB"
   go_rec = ""
   ui_modeless_dlg_close(rollup_title)   
   If ui_modeless_dlg_exist(dlg_title)  
		ui_modeless_dlg_close(dlg_title)
	end if
end if

if a_dlg_button = "ROLLDOWN"
	If ui_modeless_dlg_exist(dlg_title)  
		ui_dlg_show(dlg_title)
	else
	ui_modeless_dlg_box(dlg_title,dlg_body,dlg_event)   
	end if 
	ui_dlg_hide(rollup_title)
end if

Also change the position=remember statement in the rollup_body to a unique value.


Using the show\hide method has the added benefit of returning the user to the dialog in the state that they left it.

[MoGrace]

Re: My 1st Grid Component on the Desktop

Thanks Tim - I'll try it out on Friday.

[MoGrace]

Re: My 1st Grid Component on the Desktop

Got a chance to try it out today - works great! And both dlgs remember their positions. Thanks Tim. And

[Ray in Capetown]

Re: My 1st Grid Component on the Desktop

I am having a look. I changed the xml definition to use your previous sample table and am seeing the behavior you described. it is a weird one. Even rerunning the function I get the same result. Hmmmm

Where would one find the previous sample table in order to study this problem and the resolution?

[Tim Kiebert]

Re: My 1st Grid Component on the Desktop

Apologies Ray, I must have used one of Robin's examples from another thread. I will make a sample adb and table. But all you need to do is point the browse to any table you have and then adjust the xml definition. I got rid of all but three columns and also removed the filter in the first line.

[Ray in Capetown]

Re: My 1st Grid Component on the Desktop

No worries Tim
I'll get to the XML code and make adjustments.
So the problem is not specific to any particular fields or data content?

[MoGrace]

Re: My 1st Grid Component on the Desktop

I have been trying out different features in order to find one that would be suitable for a dynamic search whereby i could change the underlying table, and make it work like a dock panel. And since i can't seem to make an actual dock panel, I thought a modeless global toolbar would be the next best thing since it is not form dependent - and you can roll them up.

The next leg of this project is to create some files to hold the xml definitions of the various tables I want to use, and let the script call whichever one the user wants to use. Since now I know how to change the size dynamically, displaying different tables seems feasible.

Sounds fun doesn't it?

[MoGrace]

Re: My 1st Grid Component on the Desktop

I have this browse working correctly and have a OnRowDblClick event that opens a related form, so I made a template out of it so all I need to do is copy the XML to the new function for a new browse.
xdbrwpo.jpg

Here is the event that works in the UDF above:

XDbrwPO_browse_definition = <<%xml%
<browse drop_down_menu="Main Menu" toolbar="My Browse Toolbar" restrict_enter="yes" restrict_change="yes" restrict_delete="yes" gridline_horizontal="yes" gridline_vertical="yes" restrict_split="yes" data_entry_style="default" row_height="17" order="cdate(podate)+dir_id+pono">
<code>
	<OnRowDblClick>
dim go_rec as c
go_rec = custpo->ko_no
Go_frm("Knit Order","KO_NO",go_rec)
</OnRowDblClick>
</code>

But in my new browse function, this code will not work unless the browse I am working from is open:

brw1_browse_definition = <<%xml%
<browse width="867" data_entry_style="default" drop_down_menu="Main Menu" toolbar="My Browse Toolbar" restrict_enter="yes" restrict_change="yes" restrict_delete="yes" gridline_horizontal="yes" gridline_vertical="yes" row_height="17" filter="txtype=&quot;R&quot;">
<code>
	<OnRowDblClick>[COLOR="#FF0000"]<![CDATA[[/COLOR]
dim global get_dir_id as c = brw1:dir_id.value
dim global get_refno as c = brw1:txref.value
dim global get_yarnid as c = brw1:yarnid.value
dim choice as c = ""
dim lst as c
lst = <<%a%
Search All Transactions
Dir Set Up
Yarn Receipt
Yarn Tx
Yarn Item
%a%
choice = ui_get_list2("Action: View Form","Yarn Receipt",lst) 
select	
	case choice = ""
		'user cancelled
		goto ENDIT
	case choice = "Search All Transactions"
		vw_frm_1st("Yarn Trans")
	case choice = "Dir Set Up"
		Go_frm("Dir Set Up","DIR_ID",get_dir_id)
	case choice = "Yarn Tx"
		Go_frm("Yarn Tx Zoom","TXREF",get_refno)
	case choice = "Yarn Receipt"
		Go_frm("Yarn Rec","YR_NO",get_refno)
	case choice = "Yarn Item"	
		Go_frm("Yarn Item","YARN_ID",get_yarnid)
end select
ENDIT: 
end[COLOR="#FF0000"]]]>[/COLOR]
</OnRowDblClick>
</code>

Notice the section I highlighted? Why is that needed for this code and not for the first? And what is it doing? I tried removing it but that messed up the browse format. I should mention that I also removed all the status_area code from both scripts and that seems to work alright in both functions.

[MoGrace]

Re: My 1st Grid Component on the Desktop

This place must be magic - I have been working on this for 2 days and now it is clear that my variable definitions are wrong for this context - here is what they need to be:

dim global get_dir_id as c = YarnTx->dir_id
dim global get_refno as c = YarnTx->txref
dim global get_yarnid as c = YarnTx->yarnid

I am working with a set, but that is not the problem, rather it was the syntax. Which is why when the temporary browse was open the global variables were set and the script worked, but not when the browse was closed because the XD needed a table pointer not an object pointer.

Sometimes I think I have forgotten more than I have learned!

I would still like to know what the CDATA business is about...

[MoGrace]

Re: My 1st Grid Component on the Desktop

I would like my function to dynamically filter the underlying table for the browse before it displays but am having trouble passing a filter to the xml browse definition. Has anyone tried this and had success?

In a test browse I added a filter using a global variable and in the xml it rendered it as:

filter="TxType=var->txt_str"

and that worked when the value of txt_str was "R", but I would like the entire string to contain the filter but can't figure out how to format it so

filter=var->txt_str where txt_str = "TxType = 'R' "

If the table could be queried before the browse is displayed I'm thinking that might be a good way to do it too.

[Ray in Capetown]

Re: My 1st Grid Component on the Desktop

I would like my function to dynamically filter the underlying table for the browse before it displays but am having trouble passing a filter to the xml browse definition. Has anyone tried this and had success?

In a test browse I added a filter using a global variable and in the xml it rendered it as:

filter="TxType=var->txt_str"

and that worked when the value of txt_str was "R", but I would like the entire string to contain the filter but can't figure out how to format it so

filter=var->txt_str where txt_str = "TxType = 'R' "

If the table could be queried before the browse is displayed I'm thinking that might be a good way to do it too.

..use ...

filter="*remembered()"