ok i see, the ui needs to protect better the inputs to the operator. the op
doesn't support that value (not that it couldn't).

@szabolcs, have you logged this?

On Tue, Jun 19, 2012 at 11:05 AM, Eric Cosky <[email protected]> wrote:

> Yeah it’s no big deal to me but technically it is a bug. I didn’t even
> know about it until Szabolcs asked someone to double check it.****
>
> ** **
>
> Dragging a slider to one spot, having the dialog not clamp the UI value as
> specified in SPDL, and not having the actual operator results match the
> SPDL slider or UI value are a little concerning since that seems like it
> would be a more general UI bug that goes beyond this one control. Do I now
> have to wonder if using the slider of any PPG will not be tracked
> correctly? I don’t know. Curious bug though. ****
>
>  ****
>
> ** **
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Steven Caron
> *Sent:* Tuesday, June 19, 2012 10:55 AM
> *To:* [email protected]
> *Subject:* Re: SI2013SP1****
>
> ** **
>
> i dont see that as an issue, they are blocking really low values which
> might result in the split to actually be right on top of the boundary edge.
> if you want a really really close edge use the "]" key (split edge tool)
> middle click and drag for a loop and left click and drag for a single point
> ****
>
> ** **
>
> s****
>
> On Tue, Jun 19, 2012 at 10:45 AM, Eric Cosky <[email protected]> wrote:****
>
> This is what I get, http://imgur.com/60YJx ****
>
> The point isn’t able to get to the corner and there is the unexpected
> error in the log.****
>
>  ****
>
>  ****
>
> CreatePrim "Cube", "MeshSurface"****
>
> ActivateEdgeSelTool****
>
> ActivateEdgeSelTool****
>
> SelectGeometryComponents "cube.edge[10]"****
>
> SplitEdge "cube.edge[10]", 50, False, True, siPersistentOperation****
>
> ' ERROR : 2006-EDIT-SetValue - Unexpected failure.****
>
> SetValue "cube.polymsh.splitedgeop.ratioedge", 0.001****
>
>  ****
>
>  ****
>
> Trying to execute the SetValue command manually gives an overflow error. *
> ***
>
> SetValue "cube.polymsh.splitedgeop.ratioedge", 0.001****
>
> ' ERROR : Overflow: 'SetValue' - [line 1]****
>
>  ****
>
> Setting to 0.0010000001 doesn’t cause the error though, so it’s not a
> parser error skipping the last digit.. odd. ****
>
>  ****
>
> I found that modifying C3DSplitEdgeOp.spdl so the ratioedgerange was
> clamped to 0.002 avoided the problem (0.0011 and smaller numbers didn’t
> work for me, didn’t try to converge on the smallest usable value – the ui
> only shows 3 digits so 0.002 might be the limit). ****
>
>  ****
>
>  ****
>
>                 Parameter "ratioedge"****
>
>                 {****
>
>                                 GUID =
> {CF8F1A90-46B9-11d4-8C28-009027BC3A0E};****
>
>                                 Name = "Ratio Edge ";****
>
>                                 Description = "Ratio on edge where to
> split the edge";****
>
>                                 Type = VT_R8;****
>
>                                 Caps = Persistable, Animatable;****
>
>                                 Class = E3DPROPERTY_CLASS_TOPO;****
>
>                                 Range = 0.002 to 99.999;****
>
>                                 UIRange = 0.002 to 99.999;****
>
>                 }****
>
>  ****
>
>  ****
>
> Oddly I found if moving the mouse quickly, it would still show 0.001 with
> the new clamping and the actual point location was nowhere near 0.001 – pic
> here: http://imgur.com/EGahh****
>
>  ****
>
> So, yeah, it’s a little buggy.****
>
>  ****
>
>  ****
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Szabolcs Matefy
> *Sent:* Tuesday, June 19, 2012 12:46 AM****
>
>
> *To:* [email protected]
> *Subject:* RE: SI2013SP1****
>
>  ****
>
> Unfortunately not repaired. Could you check please:****
>
>  ****
>
> 1.       Make a cube****
>
> 2.       Use the split edge with ratio control, and try to slide the
> slider to the left extreme, see the result on the viewport. I hope it’s
> just a local issue, and not worldwide…****
>
>  ****
>
> *From:* [email protected] [
> mailto:[email protected]<[email protected]>]
> *On Behalf Of *Szabolcs Matefy
> *Sent:* Tuesday, June 19, 2012 9:15 AM
> *To:* [email protected]
> *Subject:* RE: SI2013SP1****
>
>  ****
>
> Never mind I found it. I hope, that the split edge ratio PPG is repaired.*
> ***
>
>  ****
>
> *From:* [email protected]
> [mailto:[email protected]] *On Behalf Of *Szabolcs
> Matefy
> *Sent:* Tuesday, June 19, 2012 7:58 AM
> *To:* [email protected]
> *Subject:* RE: SI2013SP1****
>
>  ****
>
> Hey****
>
>  ****
>
> And where is this update? I can’t see on subscription…****
>
>  ****
>
> *From:* [email protected]
> [mailto:[email protected]] *On Behalf Of *Eric Cosky
> *Sent:* Tuesday, June 19, 2012 4:23 AM
> *To:* [email protected]
> *Subject:* SI2013SP1****
>
>  ****
>
> Just installed SP1, no problems so far and it’s nice to see a few pet bugs
> have been fixed. ****
>
>  ****
>
> Thanks for the update.****
>
>  ****
>
> -Eric Cosky****
>
>  ****
>
> ** **
>

Reply via email to