Anim8or Community

Please login or register.

Login with username, password and session length
Advanced search  

News:

An update to Anim8or, v1.00b, is available with a few bug fixes. Get your copy HERE. See the "ReadMe" file for details.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - chuft-captain

Pages: 1 [2] 3
16
This has been implemented and is looking good. Thanks Steve for slipping this into the release at the last moment.

17
Anim8or Challenges / Re: Challenge #34: Anim8or 1.0 splash screen
« on: May 31, 2017, 09:47:05 am »
The only possible change I can think of that would make it better is if a little Robin got in through one of those windows and was seen flying through the scene (or perhaps sitting on the number eight) and leaving a small "deposit" for good luck! ;-)
something to bear in mind for v1.1, maybe :)
I was thinking somthing along the lines of this....  8)  .. Just a quick mock-up!
The "deposit" would probably look more effective if it was mainly dripping from the top edge(s) of one or more letters down the face, and maybe even pooling on the floor below, however I've just quickly grabbed what I could from imagery on the web, so it's not very effective, but is just to give some idea of what I was thinking.... :)

18
I was referring to my using group for layer TWICE :)
Birds of a feather, flock together! :)

No need to be embarrassed about a couple of typos, but the fact that you were thinking about groups and layers interchangedly (is that a word?) .. suggests a possible elegant simplification...
Maybe groups and layers are conceptually one and the same. This might open a whole can of worms though. (EDIT: Don't tell the birds about the worms!)

19
Why so :-[ ?

I hope you don't think that you have to cater for all those scenarios. I was just thinking out loud about the possible scenarios.
I think your strategy to put the group in the same layer when all objects are already in that layer, and in the default layer otherwise, would go a long way to improving this functionality.
I mean ... what else can you do? ... and it's probably better to just have a couple of simple rules that everyone can understand, than to have a very complicated strategy.

Regards
CC

20
Do you mean ... "What group layer should the group be in if the objects are in different layers? The default group layer?"

I'm not sure what the best approach would be.
One approach might be to just put the group in the lowest layer of the selected objects.

But what if there are other un-selected objects already in that layer? Maybe you should scan the layers of the selected objects with a preference for placing the group in a layer which is otherwise empty --- this would nicely separate it from the other objects.

But what if none of those layers are empty of extra objects? Do you put it in the nearest empty layer, or create a completely new layer for the group? ... This would appear to require that there is no limit on the number of layers which can be created, whereas at present there's a limit of 8 layers.

Regardless of the layer selection strategy for grouping, once grouped, on a future un-grouping action, I think that the un-grouped objects should probably remain in the current layer rather than returning to their original layers.

21
Anim8or Challenges / Re: Challenge #34: Anim8or 1.0 splash screen
« on: May 30, 2017, 03:47:00 am »
I only joined this forum very recently, so I didn't vote in this poll, however I agree with the decision to go with thecolclough's entry as I think it best achieves the requirements for a Splash Screen.

The only possible change I can think of that would make it better is if a little Robin got in through one of those windows and was seen flying through the scene (or perhaps sitting on the number eight) and leaving a small "deposit" for good luck! ;-)

22
      Maybe Ctrl LMB Click-Drag. I'm lefthanded. That would work for me better  :) :) :)
Sorry to jump into this thread as I haven't been following it, however I noticed this comment and thought it worth mentioning that allowances for left-handedness are better handled in the mouse-configuration options of the OS where you should be able to reverse the meaning of LMB and RMB on your computer. (This shouldn't be a consideration in the design of the application.)
I guess you almost certainly already know about this and were just joking about designing for left-handedness.  :)

Regards
CC

23
(Build 1269)

So it's a bit hard to work out exactly what's going on with this one, but I think the crux of it is that when grouping objects it seems that the group is always sent to layer 0 (even when the grouped objects are initially all in the same layer).
If Layer 0 is hidden then the newly grouped object disappears from view ... in which case I can re-enable Layer 0 and re-assign the grouped object back to the original Layer, however if Layer 0 is visible, then it's not immediately apparent that the Layer has changed.
I understand that when the objects being grouped are individually in different layers before grouping, then the only logical decision I guess is to put the group in Layer 0, however when they're all already in the same Layer, then perhaps it is more appropriate for the group to remain in that Layer.

This opinion is based upon the way that I work --- I tend to use Layers to group multiple objects which are used to compose an assembly or assemblies, but I often need to temporarily un-group assemblies to make changes to individual elements, and then re-group the assembly or assemblies, at which point the assembly and it's components gets re-assigned to Layer 0 (and this fact often goes un-noticed by me if Layer 0 is also visible.)
I imagine that if I was to make changes in all Layers and forget to re-assign the Layer on every occasion after re-grouping, then eventually everything would just end in Layer 0 ...  so I think you can see the problem.

As I can have multiple assemblies which I may want to view and work upon independently, I tend to organize each assembly and it's components into it's own Layer. I then want it to remain in this Layer unless I choose to move it elsewhere. The constant re-assignment to Layer 0 causes a bit of chaos which affects my workflow.

Other people may have a different opinion about this if they perhaps use Layers in a different way to me, but this is how it affects my workflow.

CC

This post referenced in: Version 1.0 Bugs and Suggestions

24
Thanks for the replies guys,

Although I had become accustomed to the alt-RMB combination, as long as there's some way to do it I'm happy, so clicking on the MMB will suffice for now, until a better solution can be found for the future... Perhaps nemyax's suggestion of ctrl-RMB might be a good long term solution.
From a UI perspective it would seem like some combination involving SHIFT, CTRL, or ALT keys is a more natural and intuitive approach than MMB.

Thanks again
CC

25
In my very best David Attenborough voice....

"This is a rare treat indeed. It's very unusual for the lesser spotted software developer to venture this far from the cave entrance (except to top up on his staple diet of coffee and energy drinks). It's an even more rare event for him to engage in actual conversation with humans, let alone about strategy ... unless it's the Strategy Pattern of course."


26
Thanks Steve!

... but don't do it if there's any chance of breaking something else as this is a very trivial issue after all.
(It would be a great shame to break v1 for the sake of a tick mark!  :'( )

27
Will do.

One thing I do recall is that at the time that this occurred, I had just discovered the alt-RMB function no longer worked and I was trying to find out (by trial and error) what key combination would de-select faces. So it may be possible that some random combination of CTRL / SHIFT / ALT and RMB caused this issue, as well as the issue with the diacritic characters on the keyboard (as both issues occurred around the same time).

I do think it more likely that whatever I did put the OS into some strange state, rather than Anim8or, but this might just give you an avenue to replicate it.

CC

28
One extra comment:
The ability to re-locate multiple objects at once would be of most help when re-organizing existing 0.98 / 0.95 projects, however for new v.1 projects most of the overhead associated with organizing object folders would be mitigated if new and imported objects were to be initially located by default in the same folder as the current object ... which in most cases would probably be the appropriate location for it to stay (in the way that I work anyway --- YMMV).

Currently, new and imported objects are created at the root level (which means they almost always have to be re-located at some point).

29
I was adjusting texture alignment on selected faces at the time, so point edit mode.
(ie. the yellow UV tool was visible, however once maximized I couldn't get rid of it because none of the controls were clickable due to whatever the iossue was.)
OS=WIN7 SP1 64bit
Graphics= Intel HD4000 (integrated)

I can't replicate the problem now either, so I wouldn't worry too much about it Steve. Probably not a bug, but due to whatever was going on with my machine at the time (remember I also had those keyboard issues around the same time -- which have also not re-occurred).

I think it's safe to assume this is not a bug, but if it happens again I'll try to get a handle on the exact cause / circumstances, and I'll let you know.

CC

30
Completely understand and agree, and I have no expectations regarding timeframe in any case. (Sorry I haven't posted earlier).
Probably the one with the least risk of regression is #2, but NONE of these is worth the risk when you're so close to release.

That said, you might just want to make sure that you can't replicate #6 (just posted) before release. (Although it did come right eventually, so probably not a show-stopper even if you do manage to replicate it.)

Cheers
CC

Pages: 1 [2] 3