How to change the behavior of hyperlinks in generic inquiries - acumatica

In Generic Inquiries, I've noticed that certain fields automatically have hyperlink functionality to open specific screens. I'm not sure what determines what screens these open (I'd imagine its based on whether its a key field for a maintenance table/DAC, etc.) - but I've also noticed that the manner in which it opens a screen is different for different fields / field types. Some open a popup with no menu, others open in the same screen space as the Generic Inquiry, and in doing so replace it in the browser.
My question is this: Is there a way to modify, in the GI setup, the manner in which it opens the screen so that it always opens as a replacement instead of a popup window?

If I remember correctly, with Acumatica ERP ver. 6.0 on the Generic Inquiries' Navigation tab there was added Window Mode drop-down to configure how the screen is opened from hyperlinks in a given GI:

Related

Sublime Text 3: Hide tab bar in only one view

If I have multiple views open in a window in Sublime Text 3, is there a way for me to hide the tab bar in only one of the views, rather than View > Hide Tabs, which hides the tab bar in all views?
Except for Justin's workaround, there is not a way to do this in a single window. The toggle_tabs command is associated with the window, not an individual view, so it operates on all views within a particular window.
Hypothetically, you could write a Python plugin to execute toggle_tabs every time you switched to a particular view, but it would have to be file- or file type-specific.
If its just one view just drag it to make it a new window that way you will have two windows, one with the tabs you wish to see and other with ones you dont want to see

Keep taskbar icon, replace MFC dialog

I have a MFC dialog based application. User can change the language of the dialog, and I made this by closing existing dialog, and opening another with changed language. The problem is that the effect in the taskbar is that one icon is removed, and another identical is created in its place. If my application's icon is not the last icon in the task bar it will be perceived as it was moved to the end of taskbar icon set.
I want to retain icon's position in the taskbar, and rather to prevent icon flicker at all from happening. How do I do that?
The application must support OS'es from Windows XP to Windows 7.
EDIT: alternative question for which I would accept an answer is how to create an invisible window that is nevertheless shown in the taskbar, and how to forward relevant window messages from that window to my main window?
Make the dialog a child of another outer parent window. The parent can be a dialog or any other kind of window; all it will be providing is the title bar. If the user tries to resize it it will have to forward resizing commands to the dialog, but otherwise you shouldn't need to do much in the parent window.
Why not replace the dialog with a CFormView instead? That way there's a frame window that wraps around the dialog (which is embedded in a form view) and it's the frame window that owns the taskbar icon.
Create an SDI application that displays a CFormView. Display the dialog in the default language (or whatever langauge the user previously chose) on initialization. When the user chooses the 'change language' option, simply change the form view that's being displayed with a new one.
Bonus feature: with this design, the framework will take care of things like language-specific accelerators and menus for you with no effort on your part.
For more on how to do this, check out http://www.codeguru.com/cpp/w-d/doc_view/viewmanagement/article.php/c3341/Multiple-Views-Using-SDI.htm

System wide right click context hook

**Hello..
i am creating English To Gujarati Dictionary WinForm Application.
I need to set a system wide hook to the right click context menu on for text selection.
it means when this application is running,and if user selects word from any program and right click on it gujarati meaning of that word should be displayed as menu item.
How to do this?
or any other options like Registery Programming,shell extentions etc...?
i have to do this,even if you say its not possible.
so please help me.**
Hooking the mouse activity is the easy part. See SetWindowsHookEx, and lots of questions regarding hooking in SO. This way, you can tell when the mouse is right-clicked.
Getting the selected text is the harder part. See WindowFromPoint, for starters. You'd have to recognize the control, and if appropriate get the selected text from it. This will not always be possible using simple Win32 functions, if the control is complex.
Adding the translation to the right-click menu is probably the impossible part. Adding stuff to explorer context menu is not a problem, because explorer provides that possibility. But various applications will have various right-click menus, without a way to extend them. They might not even use Win32 for the menus, for whatever reason. A better option, IMO, would be one of the following:
Forget about changing the right-click menu. Open a window next to the point of selection with whatever content you want, and let the application show its own right-click menu.
If the user right-clicks while, say, pressing shift, show your own right-click menu, and don't pass the message to the application. So the user will see only one menu, which is yours. The user must of course be aware of this combination.

Custom Backstage View Tab like standard tab FileNew

I want to design own custom backstage view tab that has desing like standard tab FileNew.
How can I (and can I at all) use such tab elements like scrollable button set or large borderless button with text at bottom of one.
There are elements in the BackStage Tabs which are built-in and not available form the programming side. For example, all the individual controls on the Print Backstage Tab cannot be re-used by a developer. I'm afraid that we have the same problem with the File New Backstage. The previews are built-in. You can verify this if you look into the WordControls.xlsx file delivered with the Office 2010 Control-IDs download: There are no controls for the TabNew except for "GroupNewFormTemplates", "GroupNew2003Dialog" and "GroupNewFormPreview".
You can only re-use controls which are defined in the Ribbon Scheme, as Combobox, Edit Control, Button, and so on.
So to display your templates, you must use these default controls, or built something completely different.

SharePoint 2010 Publishing Page live preview... any thoughts?

I would like to collect your ideas on the following:
SharePoint 2010 (and 2007) does have a preview button... while you are editing a publishing page you can switch to the "Page" tab and hit the Preview button:
Clicking this button does some magic to save your data, and opens a new window where the preview page is displayed. Nice, but could be better. What I would like is live update on editing of field controls from the edit page on the preview page.
My thoughts on this is are as follows:
Field types have an ID. For rendering the field values on your preview page, subclass from the standard FieldValue control, and render a span with the same ID around the field value html. So if we have the text ABC in the content editable div of a RichTextFiled X, render the field value as ABC in the display output (for example using EditModePanels for Display and Edit)
Add key-stroke event handler on all fields for the edit mode page (using for example jQuery), on key press copy contents from edit browser window to preview browser window
Transfer can be done using http://www.sfpeter.com/2008/03/13/communication-between-browser-windows-with-jquery-my-new-plugin/.
Does this sound doable? Would be great to work dual monitor, edit on one monitor, preview page in its real rendering on the other monitor. Especially if the edit mode differs from the display mode.
Looking forward to your input!
I will answer my own question. It is not as easy as its sounds. Fields can use things like reusable content and render patterns. These features render at server side, and change the output. This would require postbacks, which renders the whole thing useless. Lets stay with the already available preview button.

Resources