Re: Easy Hide Ip Serial
Amabella Tevebaugh
First point is a pretty easy yes. To create another drill down level you enter the Platform Category sidebar filter (where you see the drill downs in the first place) then right click on any item and go to Add > New Category... To change where that category is placed go to the parent tab and select which item(s) you want. You can then place playlists and platforms under the new category. Your desired heirarchy would look like:
Root
- Consoles (Category)
- Nintendo (Category)
- Nintendo Entertainment System (Platform)
Second point is "kind of". The easiest way is to hide games that aren't hidden in Big Box is to set the hide flag to true on those games. In Big Box settings hide games mark hidden, then in LaunchBox DON'T hide games marked hidden. This will make it work kind of like you want.
If every game in the platform is hidden, it hides the platform as well. The hide flag can also be bulk edited. All you need to do is go to the platform in question inside of LaunchBox, then select an item in the grid/list and then press Ctrl+A, Ctrl+E then in bulk edit wizard that appears set the field you want to update to "Hide" and check the box.
You can use Launchbox to mark all games in a system hidden, this will then hide said system, then both Launchbox and Bigbox have there own settings for if hidden games are shown or not, so you can hide/unhide as needed in either UI.
Shortcoming - The main issue I can foresee is that dockers are customizable in Krita and user-modified dockers will affect what gets unhide and what not. Thus essential stuff should be added as a dedicated preset which can be enabled for cohesive usage.
with just these changes, the interface should be tablet ready and should be fairly able to compete with pro apps. This IMHO feels should be easy to implement but a developer can vouch for it. Layer selection is already considered in 5.2 release which works as intended.
Just as an example of what can currently be done in Canvas-Only with menus, toolbars, and dockers enabled, and scrollbars and status bar disabled, and with Multiple Document Mode as Subwindows:
canvasonly21536808 46.8 KB
Keep in mind there is already a way to toggle the visibility of all dockers: Settings->Show Dockers, which can be assigned a shortcut. If you switch to a Workspace with minimal dockers, that could also work.
Now this setup can give access to basic brush settings and in case layers need to be accessed or some tools need to be used, can come out of canvas mode at any time. Color and brush access can be done with a longer press finger gesture to get the Krita wheel
These are really good suggestions and i have even requested something like this before but without the mock up. I use krita on a large phone the s22 ultra and i need ultimate customization even more than tablet users if added i wouldnt even care about pretty UI for mobile users ! But sometimes its just fighting the UI and slow workflow that cause me to try other apps on android like infinite painter and concepts which are great apps in their own right but do not offer everything krita has. My two cents.
Hi @Michelist , I understand that. True I am not expecting anything out of this (at least not very soon) from the devs, My only humble submission is how to get this noticed enough so that it at least gets considered for implementation. But your message definitely is important for all people who have low knowledge of how open source works. Thanks
I've got another challenge for you all. I'm currently developing a form that'll allow the user to name a particular component in the displayed assembly model of an assembly drawing; the rules & macros behind the form will then search through all of the present views on the assembly drawing and hide (i.e. visibility turned off) all instances of the specified component. I've been successful in developing such a feature via a VB macro, which is awesome. I've even been able to extend the search function's reach so that it can search for components within a subassembly.
However, there are some cases where the user will want to specify a folder name within the assembly's model tree, and have all of the components contained within this folder be turned invisible. This would be much easier to do than naming all of the individual components whenever one of these folders happens to contain a large number of components.
Given what I've come to expect from Inventor's VBA Editor, I'm imagining that these folders are probably some kind of an object collection or an array that I'd probably be able to iterate through via a For-Each loop. I just need to know how to create a representation of the folder in my VB macro.
Does anyone know how to refer to a folder within an assembly model when creating a VB macro for an assembly drawing? I've been digging through the various help files in search for the keywords that I need to do this, but I haven't come across anything useful (at least, nothing that I've recognized as what I'm looking for, exactly). If anyone happens to know if & how this may be possible, I'd greatly appreciate some pointers on this matter.
Alrighty, I've figured out a bunch about hunting down and finding components based on whether or not they're nested inside of a folder. However, I've run into a bit of a brick wall in regard to trying to set the visibility of these nested components in the drawing itself.
My problem at this point is that there's no way to direct way to create a proxy for the components' occurrences so that I can hide them in the current view via something like the oView.SetVisibility() sub-routine. Ugh!!! So close, and yet so far away...
I'm trying to see if there's anything like regular expressions or such that I could use to extrapolate the names of the components via the BrowserNode.FullPath property. I would then just run my other macro with the extrapolated component name and have it hide the component.
If anyone has any suggestions on what could help me close the gap between these user interface objects and their actual component occurrences, I'm all ears. If I figure out some other way around it, I'll post it here for people to see. Wish me good luck! =P
So I've finally come up with a solution to my problem. It took a while to figure out a solution, but I did it, and it works beautifully (at least, for my purposes, anyway). And like I said I would do in my previous reply, here's the code that I came up with.
Disclaimer: I apologize in advance if my code is messy or inefficient - I'm just getting my feet wet in Inventor's VBA, so I'm learning a LOT of things every day on how to program efficiently.
Like the instructions in the screenshot below shows, this tool will scan through and turn off the visibility for individual component occurrences in DrawingViews 1 - 5 on the shop drawing. It can also turn off all components that share the same "part number", which is the name that shows up in the Inventor drawing's Browser Window. On top of that, you can enter multiple part numbers into the Find & Hide Components textbox; just separate each name with a comma, and the sub-routines will find & hide each of the components that you've listed. Lastly, the Find & Hide Folders textbox will find & hide all of the contents of a specified Browser Folder.
Why not just do this all by hand? Well, when you're working with a shop drawing template, there can be multiple DrawingViews used to illustrate an assembly model's details (my company uses 5 views to illustrate our packing crates). When you swap out some unit assemblies that are contained within each crate assembly model, sometimes a lot of small components that you'd prefer to remain invisible become visible on the drawing. I got sick and tired of having to go into each DrawingView and manually hiding the same components over and over again. So now I won't have to, and it's frakkin' AWESOME.
These sub-routines work in tandem with a couple simple User Parameters, iLogic rules & a simple form to perform their task. They're currently a part of a shop drawing template file that I've been refining, so everything is tied locally to a single .IDW file.
The .IDW file has two simple User Parameters: hide_this_component; and hide_this_folder. These text parameters simply hold the value of whatever the user types into the UI Form (see below). The iLogic rules that are tied to these User Parameters are simple, and look like the following:
There's a couple of interesting things that I've learned while figuring out this tool. First, Inventor gets angry and throws errors at you if you attempt to hide a component that doesn't contain any 3D models. The engineering team at my company sometimes create these empty placeholder components in their assembly models solely to make some additional unmodeled components appear on the assembly's B.O.M. I found that checking each sub-component's SurfaceBodies property helped to determine if it was something that's safe to hide.
Another interesting thing that I've learned was that the BrowserNodes in the Browser Window don't seem to have any direct connection to their counterparts within the assembly document. My need for a tool that could hide a specified folder in each DrawingView required that I dig through the BrowserNodes to find the components listed within a BrowserFolder. But since there's no BrowserNode property that directly links it to its component counterpart within the assembly model, I had to create a work-around method to solve my problem.
To solve my problem, I went about grabbing each BrowserNodes' FullPath property, Split()ing them up into a Variant array, and then extracting the part numbers & occurrence numbers of each component from the Variant array's last two elements. I then used my FindAndHideComponents() sub-routine to seek out & hide all applicable components whose Name property matched the extracted part numbers & occurrence numbers.
I can bet that this really long-winded post might be about a topic that a lot of you may have already figured out a loooooooong time ago. But with all of the google & forum-searching that I've done, none of them really had the solution to this problem that I was looking for. I'd be happy to let this post collect a lot of dust digitally in the back of a server hard drive somewhere for the rest of human existence for one single reason - that some other beginner like me may come along looking for this same exact answer, and will rejoice in finding all of this info in a single spot on the internet.
7fc3f7cf58