 | | | | | |
Subject:
|
BFC Tool?
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Wed, 3 Sep 2008 03:47:09 GMT
|
Viewed:
|
5505 times
|
| |
|
Just out of random, or perhaps not so random curiosity, is there a tool that can
take the red/ green of the BFC tools in Ldview/ L3Lab and highlight the
corresponding lines? I ask because I'm slowly trying to reverse lines between
MLcad/LDview/LDDP and it's taking a long time to figure which lines need to be
reversed and which lines don't. It's probably my own fault for writing the part
the way I did, but I think it would be helpful to have a tool like that
somewhere. There is a button in MLcad for BFC but mine doesn't do anything - is
there a way to change that?
Just wondering . . .
Ben
| | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Benjamin Lyttle wrote:
> Just out of random, or perhaps not so random curiosity, is there a tool that can
> take the red/ green of the BFC tools in Ldview/ L3Lab and highlight the
> corresponding lines? I ask because I'm slowly trying to reverse lines between
> MLcad/LDview/LDDP and it's taking a long time to figure which lines need to be
> reversed and which lines don't. It's probably my own fault for writing the part
> the way I did, but I think it would be helpful to have a tool like that
> somewhere. There is a button in MLcad for BFC but mine doesn't do anything - is
> there a way to change that?
>
> Just wondering . . .
I think the easiest thing to do is put LDDP into polling to cursor mode, then
move down the part one text line at a time. When you see a reversed polygon,
fix it. It's not perfect, but it's what I did when I decided to BFC an existing
part. (Note that I don't author parts, but I have cleaned a few up.)
There was a tool that somebody wrote that I don't think was ever released that
did this with clicks in the tool. Something like that could be added to LDView,
but it would be a fairly significant feature, and not really in keeping with
LDView being a viewer.
--Travis
| | | | | | | | | | | | | | | | | |
> somewhere. There is a button in MLcad for BFC but mine doesn't do anything - is
> there a way to change that?
This button allow to add BFC statements in LDraw code. To change winding of a
tri/quad in MLCad, double click on its line in code window (or select it in one
view and hit Ctrl-M), then push "swap" button.
Philo
| | | | | | | | | | | | | | | | | |
In lugnet.cad, Benjamin Lyttle wrote:
> Just out of random, or perhaps not so random curiosity,
> is there a tool that can take the red/ green of the BFC tools
> in Ldview/ L3Lab and highlight the corresponding lines?
If you have a Mac you can select a line in L3Lab's Tree View
and it will be highlighted in the main window.
I will release a new Windows version shortly
when I have finished L3P (currently writing update notes).
/Lars
| | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Benjamin Lyttle wrote:
> Just out of random, or perhaps not so random curiosity, is there a tool that can
> take the red/ green of the BFC tools in Ldview/ L3Lab and highlight the
> corresponding lines? I ask because I'm slowly trying to reverse lines between
> MLcad/LDview/LDDP and it's taking a long time to figure which lines need to be
> reversed and which lines don't. It's probably my own fault for writing the part
> the way I did, but I think it would be helpful to have a tool like that
> somewhere. There is a button in MLcad for BFC but mine doesn't do anything - is
> there a way to change that?
I'm currently knee-deep in LEGO database stuff;
which I've put on hold to try to get the color stuff for ldconfig ironed out;
all of which has this OTHER project on hold, but...
I have a buddy who's only peripherally interested in LEGO, but whom I got
involved in checking out the LDRAW spec as a side interest. He created a new
parser library from that spec, pretty much to letter (supporting things like
color redefinition that I later found out almost no one has bothered to support
because of lack of demand).
In order to test out his library as more than just a viewer, I started to design
with him a new series of tools for working with parts, and then putting those
parts together (new MLCAD, sorta, eventually; but we're not even close yet).
Demands at work have forced us to back-burner the project for the time being,
but I've used the tool I'm about to reference to great utility even in its
current state.
There's no warranty for this, so try at your own risk, but you can download his
technology preview build of "Foundry" at
http://alumni.cse.ucsc.edu/~dulcaoin/LEGO/Foundry.zip
This operates much as a simple viewer. Use File | Open to open a part in your
LDRAW/PARTS directory. Then notice the bottom pane of the display, showing a
tree view of the various sections of the part/model. You can navigate that tree
and see the appropriate parts of the model highlighted as you do.
Click on the part/model (I use this more for individual parts), and see the line
in the tree become active.
The line number of the line within the relevant file is shown, so you can
right-click and choose edit, and it will by default fire up notepad.exe on the
file, and then you can move to the line you want.
If you want to get REALLY tricky, download and install Florian Balmer's Notepad2
application, which can take a line on the command line to move to. (if you do
this, use something like 'c:\windows\system32\notepad2.exe /g %d %f' (without
the quotes, naturally) as your Editor Command in the Preferences box). That
would fire up notepad2 on the file and position the cursor on the relevant line
number. (%d is replaced by the line number, %f by the file name, when the editor
is executed).
Note the right-hand icon on the toolbar, the white and red chevron? This can be
clicked, or you can use Display | Backface Test Mode. That will show backfaces
in red.
See the OBI icon and menu item? Ignore those for now. Top secret new LDRAW
syntax I've been designing that's not quite ready for prime-time yet. Didn't
want to get that out too early, but this tool can useful enough that I wanted to
put it out since people are asking. You can harmlessly turn it on, but without
modified PARTS files, it won't do anything differently for you.
Last thing I can think of, holding down alt changes how your clicks on the part
are treated: typically clicking will select a pretty large object, such as an
entire sub-file. Alt-click selects down at the primitive level. "Play" with it
to see how that works.
This IS a Technology Preview, and has an expiration of January 1, 2009;
hopefully we'll have time to add to it and get new versions out before then.
It will save settings to your registry; if you need to reset those, check under
HCCU/Software/Wrightnow Developments/Foundry
That's about all I can think of for now; sorry this is sketchy and quick;
hopefully this will be useful for folks...
-- joshua
| | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Joshua Delahunty wrote:
> In lugnet.cad, Benjamin Lyttle wrote:
> > Just out of random, or perhaps not so random curiosity, is there a tool that can
> > take the red/ green of the BFC tools in Ldview/ L3Lab and highlight the
> > corresponding lines? I ask because I'm slowly trying to reverse lines between
> > MLcad/LDview/LDDP and it's taking a long time to figure which lines need to be
> > reversed and which lines don't. It's probably my own fault for writing the part
> > the way I did, but I think it would be helpful to have a tool like that
> > somewhere. There is a button in MLcad for BFC but mine doesn't do anything - is
> > there a way to change that?
>
> I'm currently knee-deep in LEGO database stuff;
> which I've put on hold to try to get the color stuff for ldconfig ironed out;
> all of which has this OTHER project on hold, but...
>
> I have a buddy who's only peripherally interested in LEGO, but whom I got
> involved in checking out the LDRAW spec as a side interest. He created a new
> parser library from that spec, pretty much to letter (supporting things like
> color redefinition that I later found out almost no one has bothered to support
> because of lack of demand).
>
> In order to test out his library as more than just a viewer, I started to design
> with him a new series of tools for working with parts, and then putting those
> parts together (new MLCAD, sorta, eventually; but we're not even close yet).
>
> Demands at work have forced us to back-burner the project for the time being,
> but I've used the tool I'm about to reference to great utility even in its
> current state.
>
> There's no warranty for this, so try at your own risk, but you can download his
> technology preview build of "Foundry" at
> http://alumni.cse.ucsc.edu/~dulcaoin/LEGO/Foundry.zip
Bad form, I know, replying to my own post (member number 3, you'd think I'd know
better :-P), but if you get display anamolies with this app, you might want to
try upgrading your OpenGL drivers (standard stuff). I have two machines, both
ATI, one runs this thing perfectly, the other displays lines that just go
haywire (yet it never seems to crash).
Again, no warranty, use at own risk, etc.; but hopefully it will do the job for
most who try it.
-- joshua
| | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Joshua Delahunty wrote:
> In lugnet.cad, Benjamin Lyttle wrote:
> > Just out of random, or perhaps not so random curiosity, is there a tool that can
> > take the red/ green of the BFC tools in Ldview/ L3Lab and highlight the
> > corresponding lines? I ask because I'm slowly trying to reverse lines between
> > MLcad/LDview/LDDP and it's taking a long time to figure which lines need to be
> > reversed and which lines don't. It's probably my own fault for writing the part
> > the way I did, but I think it would be helpful to have a tool like that
> > somewhere. There is a button in MLcad for BFC but mine doesn't do anything - is
> > there a way to change that?
>
> I'm currently knee-deep in LEGO database stuff;
> which I've put on hold to try to get the color stuff for ldconfig ironed out;
> all of which has this OTHER project on hold, but...
SNIP
>
> This IS a Technology Preview, and has an expiration of January 1, 2009;
> hopefully we'll have time to add to it and get new versions out before then.
>
> It will save settings to your registry; if you need to reset those, check under
> HCCU/Software/Wrightnow Developments/Foundry
>
> That's about all I can think of for now; sorry this is sketchy and quick;
> hopefully this will be useful for folks...
>
>
> -- joshua
It works for me just like you explained above.
Looks good.
cu
mikeheide
| | | | | | | | | | | | | | | | | |
> If you want to get REALLY tricky, download and install Florian Balmer's Notepad2
> application, which can take a line on the command line to move to. (if you do
> this, use something like 'c:\windows\system32\notepad2.exe /g %d %f' (without
> the quotes, naturally) as your Editor Command in the Preferences box). That
> would fire up notepad2 on the file and position the cursor on the relevant line
> number. (%d is replaced by the line number, %f by the file name, when the editor
> is executed).
Very nice!!! I love the possibility to select an element in 3D view (I miss that
A LOT in MLCad!).
But I seem to have some issue launching an editor, it doesn't seem to work when
there are spaces in editor path or LDraw file path.
>
> This IS a Technology Preview, and has an expiration of January 1, 2009;
> hopefully we'll have time to add to it and get new versions out before then.
A VERY promising preview !!!
Philo
| | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Philippe Hurbain wrote:
> > If you want to get REALLY tricky, download and install Florian Balmer's Notepad2
> > application, which can take a line on the command line to move to. (if you do
> > this, use something like 'c:\windows\system32\notepad2.exe /g %d %f' (without
> > the quotes, naturally) as your Editor Command in the Preferences box). That
> > would fire up notepad2 on the file and position the cursor on the relevant line
> > number. (%d is replaced by the line number, %f by the file name, when the editor
> > is executed).
>
> Very nice!!! I love the possibility to select an element in 3D view (I miss that
> A LOT in MLCad!).
Thanks, Philo; you're doing some of the cutting edge toolmaking for LDRAW these
days, so I appreciate the nice comments from you (as will the author).
> But I seem to have some issue launching an editor, it doesn't seem to work when
> there are spaces in editor path or LDraw file path.
I see that as a problem now too ["mumble, mumble, you tell them it's a Tech
Preview, and they ask for fixes anyway *cough* where was I?.." :-D]; though I
had problems with the editor on a space-path more than the parts.
I tried using quotes around the executable specification, as you'd expect to do
with the Windows Run... command; that launches the executable for me, but then
the supplied filename is pretty munged. I will have a look at fixing that
issue.
In the meantime, I suggest using the ugly MS "old-style" 8.3 names for your path
elements in the command-line you specify in the preferences to get around the
problem.
I had notepad2 in a C:\Notepad2 directory; as my test I renamed to "c:\notepad
dir". I was able to get the proper launch by specifying
c:\notepa~1\notepad2.exe as the executable in Foundry.
You can find the 8.3 version of a filename by using /X with the DIR command in a
command prompt.
As for the path, I tried placing a test .DAT in a "space dir" directory, and was
able to launch notepad2 against that file from Foundry (I loaded up the .dat in
the space dir directory, right-clicked at the "root" in the tree in Foundry, and
chose Edit; and notepad2 launched with the .DAT loaded).
I will keep an eye on this issue. We are old-time programmers here, and we
don't particularly subscribe to the filenaming issues that are MS's horse poo;
and will do our best to work around those issues.
> > This IS a Technology Preview, and has an expiration of January 1, 2009;
> > hopefully we'll have time to add to it and get new versions out before then.
>
> A VERY promising preview !!!
Thanks. I hope we get time to work on it more soon.
-- joshua
| | | | | | | | | | | | | | | | | |
Joshua Delahunty wrote:
> We are old-time programmers here, and we
> don't particularly subscribe to the filenaming issues that are MS's horse poo;
> and will do our best to work around those issues.
What, like the ones that have existed pretty much forever on Unix? :)
I will also point out (in case it catches anyone out) that it is
possible for something to NOT have a 8.3 filename, but on most systems,
this won't be a problem.
--
Dean Earley, Dee (dean@earlsoft.co.uk)
irc: irc://irc.blitzed.org/
web: http://personal.earlsoft.co.uk
phone: +44 (0)780 8369596
| | | | | | | | | | | | | | | | | |
> I see that as a problem now too ["mumble, mumble, you tell them it's a Tech
> Preview, and they ask for fixes anyway *cough* where was I?.." :-D];
Yeah... sorry for that ;o)
I hesitated before posting this comment, but...
> though I
> had problems with the editor on a space-path more than the parts.
I had problem with both. I'll try your DOS trick in the meantime!
Philo
| | | | | | | | | | | | | | | | | |
In lugnet.cad, Philippe Hurbain wrote:
> > I see that as a problem now too ["mumble, mumble, you tell them it's a Tech
> > Preview, and they ask for fixes anyway *cough* where was I?.." :-D];
>
> Yeah... sorry for that ;o)
> I hesitated before posting this comment, but...
>
> > though I
> > had problems with the editor on a space-path more than the parts.
>
> I had problem with both. I'll try your DOS trick in the meantime!
>
> Philo
I had to change the entry for the editor like this: C:\WINDOWS\notepad.exe "%f"
and it works on my machine.
cu
mikeheide
| | | | | | | | | | | | | | | | | | | | |
In lugnet.cad, Michael Heidemann wrote:
> In lugnet.cad, Philippe Hurbain wrote:
> > > I see that as a problem now too ["mumble, mumble, you tell them it's a Tech
> > > Preview, and they ask for fixes anyway *cough* where was I?.." :-D];
> >
> > Yeah... sorry for that ;o)
> > I hesitated before posting this comment, but...
> >
> > > though I
> > > had problems with the editor on a space-path more than the parts.
> >
> > I had problem with both. I'll try your DOS trick in the meantime!
> >
> > Philo
>
> I had to change the entry for the editor like this: C:\WINDOWS\notepad.exe "%f"
> and it works on my machine.
>
> cu
> mikeheide
I want to change to LDDP but the following line does not work:
"C:\Programme\LDraw Design Pad\LDDesignPad.exe" "%f".
But normally it should.
With the 8.3 names the following also works on my machine:
C:\PROGRA~1\LDRAWD~1\LDDESI~1.EXE "%f".
cu
mikeheide
| | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Philippe Hurbain wrote:
> > I see that as a problem now too ["mumble, mumble, you tell them it's a Tech
> > Preview, and they ask for fixes anyway *cough* where was I?.." :-D];
>
> Yeah... sorry for that ;o)
> I hesitated before posting this comment, but...
INTEREST is what keeps authors going. Apparently, the interest here has had its
effects... :-)
> > though I
> > had problems with the editor on a space-path more than the parts.
>
> I had problem with both. I'll try your DOS trick in the meantime!
Please try http://alumni.cse.ucsc.edu/~dulcaoin/LEGO/FoundryB.zip
The spaces issue should hopefully be resolved, and we've added a "reverse
winding" right-click menu item for triangles and quads (making all the save
functionality that was already there a bit more pointed :-P)
All the usual caveats and warnings; please work on COPIES of data for awhile
until you know you can trust things.
I asked that all comments properly survive a load/save operation, but we haven't
extensively tested that. We expect that a space may change here or there, and
any command that can work with or without '!' will gain it through a save
operation. But please put this app through the ringer on test data FIRST.
-- joshua
| | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Joshua Delahunty wrote:
> In lugnet.cad, Philippe Hurbain wrote:
> > > I see that as a problem now too ["mumble, mumble, you tell them it's a Tech
> > > Preview, and they ask for fixes anyway *cough* where was I?.." :-D];
> >
> > Yeah... sorry for that ;o)
> > I hesitated before posting this comment, but...
>
> INTEREST is what keeps authors going. Apparently, the interest here has had its
> effects... :-)
>
> > > though I
> > > had problems with the editor on a space-path more than the parts.
> >
> > I had problem with both. I'll try your DOS trick in the meantime!
>
> Please try http://alumni.cse.ucsc.edu/~dulcaoin/LEGO/FoundryB.zip
>
> The spaces issue should hopefully be resolved, and we've added a "reverse
> winding" right-click menu item for triangles and quads (making all the save
> functionality that was already there a bit more pointed :-P)
>
> All the usual caveats and warnings; please work on COPIES of data for awhile
> until you know you can trust things.
>
> I asked that all comments properly survive a load/save operation, but we haven't
> extensively tested that. We expect that a space may change here or there, and
> any command that can work with or without '!' will gain it through a save
> operation. But please put this app through the ringer on test data FIRST.
>
> -- joshua
This version does not work with the following line for the editor:
"C:\Programme\LDraw Design Pad\LDDesignPad.exe" "%f"
cu
mikeheide
| | | | | | | | | | | | | | | | |
Joshua wrote:
> > Please try http://alumni.cse.ucsc.edu/~dulcaoin/LEGO/FoundryB.zip
> >
> > The spaces issue should hopefully be resolved, and we've added a "reverse
> > winding" right-click menu item for triangles and quads (making all the save
> > functionality that was already there a bit more pointed :-P)
Mike replied:
> This version does not work with the following line for the editor:
> "C:\Programme\LDraw Design Pad\LDDesignPad.exe" "%f"
Agreed. Sorry I didn't test it better. We fixed one issue, but not both.
http://alumni.cse.ucsc.edu/~dulcaoin/LEGO/FoundryC.zip
SEEMS to have fixed the issue. No other new changes.
(FoundryB.zip is gone, there wasn't much of a point to keeping it around)
-- joshua
| | | | | | | | | | | | | | | | |
> Agreed. Sorry I didn't test it better. We fixed one issue, but not both.
>
> http://alumni.cse.ucsc.edu/~dulcaoin/LEGO/FoundryC.zip
>
> SEEMS to have fixed the issue. No other new changes.
Thanks, works great now!
Two new bug reports nonetheless ;o)
- Line number shown in status bar is off by one (eg it shows 234 when actual
line in the file is 235)
- Both display and tree expansion use Hi-res primitives (when they are
available) instead of regular ones, even when 48\ is not specified. While this
can be considered as a feature, this behaviour is annoying for parts authors.
Philo
| | | | | | | | | | | | | | | | | |
In lugnet.cad, Philippe Hurbain wrote:
> > Agreed. Sorry I didn't test it better. We fixed one issue, but not both.
> >
> > http://alumni.cse.ucsc.edu/~dulcaoin/LEGO/FoundryC.zip
> >
> > SEEMS to have fixed the issue. No other new changes.
>
> Thanks, works great now!
>
> Two new bug reports nonetheless ;o)
> - Line number shown in status bar is off by one (eg it shows 234 when actual
> line in the file is 235)
> - Both display and tree expansion use Hi-res primitives (when they are
> available) instead of regular ones, even when 48\ is not specified. While this
> can be considered as a feature, this behaviour is annoying for parts authors.
>
> Philo
Works fine here also (regarding spaces in filenames) with "C:\Programme\LDraw
Design Pad\LDDesignPad.exe" "%f" as entry for the editor.
cu
mikeheide
| | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Philippe Hurbain wrote:
> > Agreed. Sorry I didn't test it better. We fixed one issue, but not both.
> >
> > http://alumni.cse.ucsc.edu/~dulcaoin/LEGO/FoundryC.zip
> >
> > SEEMS to have fixed the issue. No other new changes.
>
> Thanks, works great now!
>
> Two new bug reports nonetheless ;o)
> - Line number shown in status bar is off by one (eg it shows 234 when actual
> line in the file is 235)
Hey! I told you we were old-school programmers.
Doesn't the whole WORLD count starting from zero now?
:grin:
I'm imagining that it's easy enough to fix.
Oddly, I find that it takes me to the right line in the file in notepad2 anyway.
It's possible a tweak was made to make sure notepad2 behaved as expected, and
the display code wasn't back-adjusted so everything made sense in the display as
well. That does seem faintly familiar (the app's been sitting dormant for some
months, unfortunately). I think that maybe %d versus %D was considered for a
base-0 versus base-1 count; it's a good idea either way going forward.
> - Both display and tree expansion use Hi-res primitives (when they are
> available) instead of regular ones, even when 48\ is not specified. While this
> can be considered as a feature, this behaviour is annoying for parts authors.
Will have to check on this one. It might be a "feature" of his parser, or some
actual unintended issue (either way, this will need some attention).
-- joshua
| | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, I had written:
> > Agreed. Sorry I didn't test it better. We fixed one issue, but not both.
> >
> > http://alumni.cse.ucsc.edu/~dulcaoin/LEGO/FoundryC.zip
Now
http://alumni.cse.ucsc.edu/~dulcaoin/LEGO/FoundryD.zip
is the version to use.
Philippe Hurbain wrote:
> Thanks, works great now!
>
> Two new bug reports nonetheless ;o)
> - Line number shown in status bar is off by one (eg it shows 234 when actual
> line in the file is 235)
This had been purposeful, base-0; I convinced that the status bar should start
at 1. %d should now represent base-1 line number in the command line issued,
and %D represents the base-0 line number.
> - Both display and tree expansion use Hi-res primitives (when they are
> available) instead of regular ones, even when 48\ is not specified. While this
> can be considered as a feature, this behaviour is annoying for parts authors.
Yes, this was done on purpose. But because PHILO WANTS IT (kidding), we added a
menu choice to determine whether to use high-res primitives or not. Your current
choice is cached in the registry so it will be remembered between runs of the
application.
-- joshua
| | | | | | | | | | | | | | | | | |
| |
|
> This had been purposeful, base-0; I convinced that the status bar should start
> at 1. %d should now represent base-1 line number in the command line issued,
> and %D represents the base-0 line number.
Thanks - text editors I know start numbering at 1.
> > - Both display and tree expansion use Hi-res primitives (when they are
> > available) instead of regular ones, even when 48\ is not specified. While this
> > can be considered as a feature, this behaviour is annoying for parts authors.
>
> Yes, this was done on purpose. But because PHILO WANTS IT (kidding), we added a
> menu choice to determine whether to use high-res primitives or not.
;o)
In a perfect world Hires would be a good choice, but since everything is not
hires substitution yields misfits and gaps I find especially ugly (same thing in
LDview).
I have another little complaint: I find it too easy to inadvertently edit and
modify LDraw primitives. Could it be possible to handle files placed in LDraw
folder differently and issue warning if the user tries to modify them?
Philo
| | | | | | | | | | | | | | | | | |
| |
|
> > This had been purposeful, base-0; I convinced that the status bar should start
> > at 1. %d should now represent base-1 line number in the command line issued,
> > and %D represents the base-0 line number.
>
> Thanks - text editors I know start numbering at 1.
That's why the easier one to use, lower-case, is 1; and the backup option is
there "just in case".
> > > - Both display and tree expansion use Hi-res primitives (when they are
> > > available) instead of regular ones, even when 48\ is not specified. While this
> > > can be considered as a feature, this behaviour is annoying for parts authors.
> >
> > Yes, this was done on purpose. But because PHILO WANTS IT (kidding), we added a
> > menu choice to determine whether to use high-res primitives or not.
>
> ;o)
>
> In a perfect world Hires would be a good choice, but since everything is not
> hires substitution yields misfits and gaps I find especially ugly (same thing in
> LDview).
Oh, we agree, and that's why it's now an option. The original intent was to get
the best looking viewer for developing the OBI syntax (shhh!), so we went for
what looked best.
There has been some test work done to show the 'Cool Silver Diffuse' parts
(black with a "spray-painted silver" overcoat look to them, from 2005 onward)
with the right speckles that's very promising, for instance. Well, promising,
anyway; not sure about "very" promising.
> I have another little complaint: I find it too easy to inadvertently edit and
> modify LDraw primitives. Could it be possible to handle files placed in LDraw
> folder differently and issue warning if the user tries to modify them?
OK, so I think we're now getting to user-feature requests, over things that need
serious attention. Which is fine, but for a technology preview, it's probably
best not to focus on the small details before there are major features
implemented that need attention first.
That said, let me understand better... do you want a warning issued whenever the
user tries to [Edit] or change the winding of any portion of a part file
appearing the in the p/ directory?
This sounds like an important consideration for long-range plans as Foundry
starts to truly allow editing of bricks.
For now I'd say that the target user of this Tech Preview should probably know
exactly what he's (or she's) doing, despite the nice trappings of a win32 file
dialog and so forth; and not fall victim to thinking that the app is in any way
feature complete or well tested yet.
Please go at this app carefully with test data and look for cracks in the armor.
If we can't find those, then hopefully we'll get some better features
implemented (adding lines is in development right now), and THEN start fixing
any user-features we forgot to design in.
Just the same, presuming I understood your intent, that design feature is
strongly noted.
-- joshua
| | | | | | | | | | | | | | | | | |
| |
|
> There has been some test work done to show the 'Cool Silver Diffuse' parts
> (black with a "spray-painted silver" overcoat look to them, from 2005 onward)
> with the right speckles that's very promising, for instance. Well, promising,
> anyway; not sure about "very" promising.
(drooling over the possibilities...)
> > I have another little complaint: I find it too easy to inadvertently edit and
> > modify LDraw primitives. Could it be possible to handle files placed in LDraw
> > folder differently and issue warning if the user tries to modify them?
>
> OK, so I think we're now getting to user-feature requests, over things that need
> serious attention. Which is fine, but for a technology preview, it's probably
> best not to focus on the small details before there are major features
> implemented that need attention first.
Sorry again... I totally agree that it is something that can wait for an
official release!
> That said, let me understand better... do you want a warning issued whenever the
> user tries to [Edit] or change the winding of any portion of a part file
> appearing the in the p/ directory?
Yes - parts/ too.
> Please go at this app carefully with test data and look for cracks in the armor.
> If we can't find those, then hopefully we'll get some better features
> implemented (adding lines is in development right now), and THEN start fixing
> any user-features we forgot to design in.
Sure. Keep us posted with new previews!
> Just the same, presuming I understood your intent, that design feature is
> strongly noted.
Thanks!
Philo
>
> -- joshua
| | | | | | |
