question about birdie

[honx]

does anyone know, where i have to copy the patters?
i don't want to specify the full path for each pattern i use,
because this line in Startup-sequence is getting really long!
tried to put them into SYS:Prefs/Presets/Patterns, but no use.
do they really have to be in the same drawer like birdie (C:)?

[volvo_0ne]

Not sure what "Birdie" is, but can't you put Birdie in it's own directory, then just Assign Birdie: SYS:Birdie/ and put the patterns there along with the Birdie program?

[honx]

birdie is a workbench hack which allows you to set patterns to window borders.
don't think that assign would make a difference, because it's started through Startup-sequence.
and after installing VisualPrefs i encounter another weird problem, see attachment.
how can i fix that issue?

//edit: found the solution for my second problem shown in attached image:
in visualprefs i had to check "Don't optimize border rendering". now this works.

[emufan]

this is Birdie.

volvo_0ne's way does not work this way.
so you may try the following:
1) put birdie and all the pattern files in one and the same folder.
for example: c:birdie2000
2) rename all the patterns to simple/short filenames,
for example: 1,2,3 .... 19,20
3) put the following commands in your s:startup-sequence or s:user-startup

;BEGIN birdie
cd c:birdie2000
run <>NIL: birdie 1 2 3 4 5 6 7
;END birdie

1-7 are the filenames of the patterns
this does load all the pattern and you have a very short command line.
I tested the above in s:user-startup.

this above should also work if you have birdie in c; folder and "cd" to your pattern folder before you call c:birdie.
give it a try.

[honx]

thx, i left birdie's patterns in SYS:Apps/birdie, where i have my birdie folder.
the birdie executable itself stays in C:, and so it works!
it looks like this:
;BEGIN birdie
cd Apps/birdie/Patterns
run <>NIL: birdie 1.jpg .... 7.jpg ACTIVEPATTERN
;END birdie

i left the block in Startup-sequence, right after VisualPrefs.

[emufan]

Originally Posted by honx

the birdie executable itself stays in C:, and so it works!

allright