Author |
Topic: Cross Reference Module (Read 1192 times) |
|
Matt
Developer
member is offline
Gender: 
Posts: 210
|
 |
Cross Reference Module
« Thread started on: Jul 6th, 2013, 10:44am » |
|
Hi,
I've been using the Cross Reference module recently (thanks Richard, for pointing it out). When adjusting the program with reference to the utility's results, the referencing can become out of sync. Would it be possible to include a 'rerun' feature in the menu, so that it's not necessary to close it down and rerun it from the utility menu? When it's opened, I resize it to the side and use it alongside the BB4W PE. This has to be done each time it's opened. No problem with the way it works, but a 'rerun' would certainly cut out the resizing each time.
Also, what exactly does the list of 'Variables that violate naming guidelines' provide. There are variables in it that do not seem to violate any naming guidelines that I can find, e.g. imgdlg%, C%(), click%.
Matt
|
|
 Logged
|
|
|
|
admin
Administrator
member is offline
Posts: 1145
|
|
Re: Cross Reference Module
« Reply #1 on: Jul 6th, 2013, 2:10pm » |
|
on Jul 6th, 2013, 10:44am, Matt wrote:| Would it be possible to include a 'rerun' feature in the menu, so that it's not necessary to close it down and rerun it from the utility menu? |
|
I expect it would be possible. The menu bar was a last-minute addition, in response to somebody asking for an output-to-file feature. It wasn't adequately tested because the Tree View doesn't realise the window height is reduced, as you may have noticed. When that bug gets fixed there should be an opportunity to add a new menu item.
Quote:| There are variables in it that do not seem to violate any naming guidelines that I can find, e.g. imgdlg%, C%(), click%. |
|
Unless there's another bug in the utility, they do! Of course they are only conventions, not rules, and it's only a warning anyway, but the reporting should be accurate. The guidelines are here:
http://www.bbcbasic.co.uk/bbcwin/manual/bbcwin2.html#conventions
Richard.
|
|
Logged
|
|
|
|
Matt
Developer
member is offline
Gender:
Posts: 210
|
|
Re: Cross Reference Module
« Reply #2 on: Jul 7th, 2013, 05:39am » |
|
on Jul 6th, 2013, 2:10pm, Richard Russell wrote:Unless there's another bug in the utility, they do!
The guidelines are here: |
|
Having re-read this, two of the examples given do, in deed, contravene convention. However, the LOCAL 'click%' does follow it, although it's used in about half of the routines, if that makes a difference, and it's in the main program.
Matt
|
|
Logged
|
|
|
|
admin
Administrator
member is offline
Posts: 1145
|
|
Re: Cross Reference Module
« Reply #3 on: Jul 7th, 2013, 10:18pm » |
|
on Jul 7th, 2013, 05:39am, Matt wrote:| However, the LOCAL 'click%' does follow it |
|
If you believe the Cross Reference utility is incorrectly reporting that a variable name does not follow the conventions please list a short program here which illustrates the problem.
Richard.
|
|
Logged
|
|
|
|
Matt
Developer
member is offline
Gender:
Posts: 210
|
|
Re: Cross Reference Module
« Reply #4 on: Jul 8th, 2013, 07:20am » |
|
Stand down. I can't even find where I thought there was a problem. Almost certainly my error.
Matt
|
|
Logged
|
|
|
|
|
