 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I have noticed that when 3.7 posts Parse Warnings, they appear with the file
name and line number in the bottom bar briefly, however, when reported to the
message window, onl;y the parse warning appears with the file and line number
location. Is this intended this way? I find knowing the parse warining
locations useful so I can fix if I want (their appearance on the bottom bar is
only brief, so not much use to keep track). or is this something that I have
turned ioff and can turn back on adn haven't noticed?
-tgq
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Trevor G Quayle" <Tin### [at] hotmail com> wrote:
> I have noticed that when 3.7 posts Parse Warnings, they appear with the file
> name and line number in the bottom bar briefly, however, when reported to the
> message window, onl;y the parse warning appears with the file and line number
> location. Is this intended this way? I find knowing the parse warining
> locations useful so I can fix if I want (their appearance on the bottom bar is
> only brief, so not much use to keep track). or is this something that I have
> turned ioff and can turn back on adn haven't noticed?
>
> -tgq
Highly agreed. Some of the messages are of rare use (number of finite objects,
etc.) It would be far more important and useful to add line numbers (and file
names in the case of parsed inc files) to the Parse warning and Possible parse
error messages.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 26/02/2011 7:31 PM, Trevor G Quayle wrote:
> I have noticed that when 3.7 posts Parse Warnings, they appear with the file
> name and line number in the bottom bar briefly, however, when reported to the
> message window, onl;y the parse warning appears with the file and line number
> location. Is this intended this way? I find knowing the parse warining
> locations useful so I can fix if I want (their appearance on the bottom bar is
> only brief, so not much use to keep track). or is this something that I have
> turned ioff and can turn back on adn haven't noticed?
>
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 06/04/2011 08:39 AM, Stephen wrote:
> On 26/02/2011 7:31 PM, Trevor G Quayle wrote:
>> I have noticed that when 3.7 posts Parse Warnings, they appear with
>> the file
>> name and line number in the bottom bar briefly, however, when reported
>> to the
>> message window, onl;y the parse warning appears with the file and line
>> number
>> location. Is this intended this way? I find knowing the parse warining
>> locations useful so I can fix if I want (their appearance on the
>> bottom bar is
>> only brief, so not much use to keep track). or is this something that
>> I have
>> turned ioff and can turn back on adn haven't noticed?
>>
>
>
I think those are coming from notations like this: scale z*1 (yours
perhaps diff axis) ... there were a couple of them is the ndi bench include
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 04/06/2011 1:15 PM, Jim Holsenback wrote:
>>
> I think those are coming from notations like this: scale z*1 (yours
> perhaps diff axis) ... there were a couple of them is the ndi bench include
LOL you picked the one axis that didn't have it.
What do you mean by "notations"? Comments?
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 06/04/2011 09:34 AM, Stephen wrote:
> On 04/06/2011 1:15 PM, Jim Holsenback wrote:
>>>
>> I think those are coming from notations like this: scale z*1 (yours
>> perhaps diff axis) ... there were a couple of them is the ndi bench
>> include
>
> LOL you picked the one axis that didn't have it.
>
> What do you mean by "notations"? Comments?
>
>
code ... lol poor choice of words i guess
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 04/06/2011 1:39 PM, Jim Holsenback wrote:
> On 06/04/2011 09:34 AM, Stephen wrote:
>> On 04/06/2011 1:15 PM, Jim Holsenback wrote:
>>>>
>>> I think those are coming from notations like this: scale z*1 (yours
>>> perhaps diff axis) ... there were a couple of them is the ndi bench
>>> include
>>
>> LOL you picked the one axis that didn't have it.
>>
>> What do you mean by "notations"? Comments?
>>
>>
> code ... lol poor choice of words i guess
I'll check when this render finishes but I doubt it as it is not hand
coded.
I'm just cleaning up an old scene.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 04/06/2011 1:15 PM, Jim Holsenback wrote:
> I think those are coming from notations like this: scale z*1 (yours
> perhaps diff axis) ... there were a couple of them is the ndi bench include
Give that man a coconut! You were dead right.
was butchered by me.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Stephen <mcavoys_at@aoldotcom> wrote:
> On 04/06/2011 1:15 PM, Jim Holsenback wrote:
> > I think those are coming from notations like this: scale z*1 (yours
> > perhaps diff axis) ... there were a couple of them is the ndi bench include
>
> Give that man a coconut! You were dead right.
>
> was butchered by me.
>
>
> --
> Regards
> Stephen
But this leaves the original question unanswered -- why isn't the file and line
number associated with the warning in the message screen? Didn't it used to do
this in 3.6?
Tom A.
who is looking for a pretty printer to help debug a missing END from a very
messy scene file.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
