Bugs item #1528731, was opened at 2006-07-26 03:18 Message generated for change (Comment added) made by zmoelnig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1528731...
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update.
Category: externals
Group: v0.39.2 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: IOhannes m zmölnig (zmoelnig)
Summary: hex loader doesn't work with namespace prefixes
Initial Comment:
When using a hex loader name like 0x3c0x7e.pd for [<~], you can't use namespace prefixes since the / is only interpreted as a hex value 0x2f.
For example, [zexy/<~] tries to load only zexy0x2f0x3c0x7e.pd, and therefore fails.
An additional search path should be added after this one where the / is used literally without being translated into a hex code, then it would look for zexy/0x3c0x7e.pd
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2007-10-16 11:48
Message: Logged In: YES user_id=564396 Originator: NO
how exactly do you think this should happen? e.g. how should [path//] be resolved? "path0x2f0x2f.pd", "path/0x2f.pd", "path0x2f/.pd" or "path//.pd"?
once there is a precise idea on how the problem should be solved, i can go and implement it.
btw, i changed the category to "externals" since the hexloader is no longer part of pd itself
----------------------------------------------------------------------
You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1528731...