Gagliem
09-20-2007, 09:37 AM
Hi Andrei,
there's a list of strange behaviours and some request, remembering that the important thing for me is hoping you'll fix the last MultiVolume bug (see topic 'The Last MultiVolume BUG (Credits section)'), the following items are only suggestions.
(1) START PAGE BUG
------------------
In START PAGE there seems to be a bug, or I'm missing something:
in a JavaScript function, inside a loop as below, if I try to display the album title I get an error, if I use all the other fields related instead of it, they are ok, why that happens?
function CustomStatistics(isHOME, StatsTitle, StatsType) {
.....
document.write('<dax:group(artist)>')
document.write(' <dax:album(all,artist,title)>')
.....
document.write (' <dax:artistlink><dax:artist/></dax:artistlink>') <!-- OK -->
document.write(' <dax:albumpagelink><dax:title/></dax:albumpagelink>') <!-- I got an ERROR!!! -->
document.write(' <br>')
....
document.write(' </dax:album>')
document.write('</dax:group>')
....
}
another curious thing is that I use a thing like this
document.write('<dax:albumpagelink>BlaBla</dax:albumpagelink>')
instead of
document.write('<dax:albumpagelink><dax:title/></dax:albumpagelink>')
I get no error and if I click on 'BlaBla' the link to the album's page works perfectly (?!)
(2) TEXTBOXES PER-TRACK BUGS
----------------------------
In beta 3, TextBoxes 6 to 8 if checked per-track setting, they didn't work, as their values will not be saved: in the official v6 it seems that only textbox 8 still doesn't work per track.
(3) CTRL+F BUG IN DAXEDIT
-------------------------
In DAXEDIT, if I use CTRL+F it select a word plus the next character.
Also if I use CTRL+F on a word shorter than the previous selected, the textbox will be filled with a mix of the shorter word, then the rest of the previous, or something like that, but the result is always that I have to copy and paste or digit the word to search in the textbox.
... and the request for (far?) future releases
(A) CD MATRIX FIELD
-------------------
There's a thing missing in the item's Properties Window:
inside the frame 'Release information' it's missing, for a complete cd archiving, the field 'CD Matrix', lts behaviour should be like the Barcode field.
The CD Matrix is an id code printed in the inner circle of the cd and identifies it apart from the CD Number printed on it, I know that now you released a beta with a lot of custom fields, but it should be nice to have it as an OCD field, because if I use a textbox, when I input the ID, OCD retrieves all the ID available in the database, and this is unnecessary as it is often unique.
(B) "ISBAND" FLAG
-----------------
It seems that the flag 'isband' works only in the Artist Page and not in the Album Page, so if I use <dax:if(isband)> in the Album Page, it returns always false, but it could be useful also in this page.
(C) CUSTOMIZABLE ICONS
----------------------
For a real audio collector, this product could be perfect if user could add his own custom media icons like audio tapes, etc. (or simply to replace OCD standards icons) and link them to the specified format field like 'TAPE', 'E-CD' for enhanced cd, 'BSET' for Box set etc... like you did for the vinyl icon.
(D) CUSTOM STATISTICS IN STATISTICS PAGE
----------------------------------------
Reading other topics, I discovered you will restyle the Statistic Page, so it would be nice if, in DAXEDIT, the STATISTICS page should allow to use all the sections, tags, etc. like START PAGE does, so everyone could add his own statistics in JavaScript (while at the moment the only way I found is to use the START PAGE with a subsection at the bottom of it, with a dynamic custom statitstic table changing contents related to different types of selections; that's why I found the (1) bug).
It came out pretty well, but when I'll move my entire collection I think it'll slow down the loading of the start page, moving all this in the statistic page would be better (I know it would be heavy... but who knows..).
... that's all!!!!
Huh! I forgot to tell that OCD v6.1.7 is great, and if I'm writing to you lots of things and topics is because I'm liking very much your OCD engine customizable with JavaScript.
Thanks Andrei... and cheers!
Emanuele
there's a list of strange behaviours and some request, remembering that the important thing for me is hoping you'll fix the last MultiVolume bug (see topic 'The Last MultiVolume BUG (Credits section)'), the following items are only suggestions.
(1) START PAGE BUG
------------------
In START PAGE there seems to be a bug, or I'm missing something:
in a JavaScript function, inside a loop as below, if I try to display the album title I get an error, if I use all the other fields related instead of it, they are ok, why that happens?
function CustomStatistics(isHOME, StatsTitle, StatsType) {
.....
document.write('<dax:group(artist)>')
document.write(' <dax:album(all,artist,title)>')
.....
document.write (' <dax:artistlink><dax:artist/></dax:artistlink>') <!-- OK -->
document.write(' <dax:albumpagelink><dax:title/></dax:albumpagelink>') <!-- I got an ERROR!!! -->
document.write(' <br>')
....
document.write(' </dax:album>')
document.write('</dax:group>')
....
}
another curious thing is that I use a thing like this
document.write('<dax:albumpagelink>BlaBla</dax:albumpagelink>')
instead of
document.write('<dax:albumpagelink><dax:title/></dax:albumpagelink>')
I get no error and if I click on 'BlaBla' the link to the album's page works perfectly (?!)
(2) TEXTBOXES PER-TRACK BUGS
----------------------------
In beta 3, TextBoxes 6 to 8 if checked per-track setting, they didn't work, as their values will not be saved: in the official v6 it seems that only textbox 8 still doesn't work per track.
(3) CTRL+F BUG IN DAXEDIT
-------------------------
In DAXEDIT, if I use CTRL+F it select a word plus the next character.
Also if I use CTRL+F on a word shorter than the previous selected, the textbox will be filled with a mix of the shorter word, then the rest of the previous, or something like that, but the result is always that I have to copy and paste or digit the word to search in the textbox.
... and the request for (far?) future releases
(A) CD MATRIX FIELD
-------------------
There's a thing missing in the item's Properties Window:
inside the frame 'Release information' it's missing, for a complete cd archiving, the field 'CD Matrix', lts behaviour should be like the Barcode field.
The CD Matrix is an id code printed in the inner circle of the cd and identifies it apart from the CD Number printed on it, I know that now you released a beta with a lot of custom fields, but it should be nice to have it as an OCD field, because if I use a textbox, when I input the ID, OCD retrieves all the ID available in the database, and this is unnecessary as it is often unique.
(B) "ISBAND" FLAG
-----------------
It seems that the flag 'isband' works only in the Artist Page and not in the Album Page, so if I use <dax:if(isband)> in the Album Page, it returns always false, but it could be useful also in this page.
(C) CUSTOMIZABLE ICONS
----------------------
For a real audio collector, this product could be perfect if user could add his own custom media icons like audio tapes, etc. (or simply to replace OCD standards icons) and link them to the specified format field like 'TAPE', 'E-CD' for enhanced cd, 'BSET' for Box set etc... like you did for the vinyl icon.
(D) CUSTOM STATISTICS IN STATISTICS PAGE
----------------------------------------
Reading other topics, I discovered you will restyle the Statistic Page, so it would be nice if, in DAXEDIT, the STATISTICS page should allow to use all the sections, tags, etc. like START PAGE does, so everyone could add his own statistics in JavaScript (while at the moment the only way I found is to use the START PAGE with a subsection at the bottom of it, with a dynamic custom statitstic table changing contents related to different types of selections; that's why I found the (1) bug).
It came out pretty well, but when I'll move my entire collection I think it'll slow down the loading of the start page, moving all this in the statistic page would be better (I know it would be heavy... but who knows..).
... that's all!!!!
Huh! I forgot to tell that OCD v6.1.7 is great, and if I'm writing to you lots of things and topics is because I'm liking very much your OCD engine customizable with JavaScript.
Thanks Andrei... and cheers!
Emanuele