_J release crashes on "Search"

jorge · 14 May 2005

thanks unkargherth, that's because I created new connector types for FloatArray and PointArray and forgot to make the search support them, it's easy to fix.

jorge · 15 May 2005

I've just uploaded a new version 0.9.3j with the search bug fixed, the link is the same as before: [old link]

lalo · 15 May 2005

jorge wrote: thanks unkargherth, that's because I created new connector types for FloatArray and PointArray and forgot to make the search support them, it's easy to fix.

woohh! i'm excited 🙂

lalo

jorge · 15 May 2005

Myself and Malc spent quite some time trying to come up with a symbol for array connectors, it was a challenge.

It was easy to design array connector symbols that looked good when zoomed in but not one that looks good at default zoom level.

lalo · 15 May 2005

jorge wrote: Myself and Malc spent quite some time trying to come up with a symbol for array connectors, it was a challenge.

It was easy to design array connector symbols that looked good when zoomed in but not one that looks good at default zoom level.

seems pretty nice... a touch of flowers 🙂

is it visible at normal zoom? if not...maybe just a square box would be nice...

array is in the semantic area of...archives wich are squarey 😀

lalo

Shifrin · 15 May 2005

lalo wrote: is it visible at normal zoom? if not...maybe just a square box would be nice...

My thoughts too 😉

Shif.

unkargherth · 15 May 2005

jorge wrote: I've just uploaded a new version 0.9.3j with the search bug fixed, the link is the same as before: [old link]

OK. Dont crash now, Anyway it continues giving the

"An attempt was made to access an unaamed file past his end"

erroe on the first search.

Shifrin · 15 May 2005

I get the same message box as unk upon the first search!

Shif.

jorge · 15 May 2005

I cant replicate it, does it happen when you type the first letter of the search and does it happen for any letter? The reason I cant replicate it might be because of modules you both might have in your toolbox that I dont.

Shifrin · 15 May 2005

I think it was throwing the message no matter what I typed. I seem to have fixed it, I moved out my custom module folder from '(1) Sound', deleted both the '(1) Sound' and '(2) Element' folders, reinstalled the latest version of SM (0.9.3j) and then moved my custom module folder back ino '(1) Sound'. No more message boxes.

I should have done some more tests first to try to narrow down what was causing it, *sorry* 🙁

Shif.

unkargherth · 15 May 2005

jorge wrote: I cant replicate it, does it happen when you type the first letter of the search and does it happen for any letter? The reason I cant replicate it might be because of modules you both might have in your toolbox that I dont.

It happens to me when I type the first letter of Firts seach since i started the SM application

For your infromation, my whole tool box has 8 pages, and i added my own folder to <SM Base dir>\Modules\(1) Sound\(10) xTools

Unforunately isn't easy to me do do as Shif because i have my own modules in standard directories , so deleting all and reinstalling makes me loose all of them?

Any solution, Jorge?

Should be a good idea to add a function to backup somewhere only non standard modules

Shifrin · 15 May 2005

unkargherth wrote: Should be a good idea to add a function to backup somewhere only non standard modules

That'd be useful! Like you said, I had all my custom modules in a folder that I had added, so it was easy to move them, remove everything else and reinstall.

Shif.